Author Topic: WCS (Read 57881 times)

SamSeeSam · « **Reply #240 on:** May 15, 2007, 04:23:31 am »

well then you can copy paste a script from someone or ask ," Please give me a working metis script for blocking caps " and be done with it...

In many cases, people use caps by mistake as it hapens with all of us...

Cheers

Bearded Blunder · « **Reply #241 on:** May 15, 2007, 05:15:49 am »

* Bearded Blunder is everlasting hitting capslock instead of left shift..

please no comments about going blind or one handed typing...

~~James420~~ · « **Reply #242 on:** May 17, 2007, 12:18:39 am »

Going to go ahead and comment on the b12 that will be released some time soon, and I must say. I'm loving the new version, can't wait till it's out to download. Tons of nice new features, some nice important changes, and some bug fixes. All I can really say is that all the current WCS users out there will love the new server once it's released, plus I believe the new release may drag over some users from FXS. Guess we'll just have to wait and see, but till it comes out. I'm going to stop messing with my bot, since the new server will make me rewrite some of my old stuff for the new server. And no, that's not a bad thing. Rewriting it all because I can now make the scripts far easier to make with one of the key changes in b12.

nylly444 · « **Reply #243 on:** May 17, 2007, 04:24:25 pm »

WCS 1.8b12 has been released!

Details on www.kingmacro.net and for archiving here

~~Josh~~ · « **Reply #244 on:** May 17, 2007, 11:46:05 pm »

DNS stuff isn't working

KM · « **Reply #245 on:** May 18, 2007, 01:00:41 am »

well as you said to me you didn't want to figure out why it wasn't working and don't want it fixed... i guess you'll have to hope that someone else has the same problem and does want it fixed

anyway, b13 has been released, mostly just a workaround for a robomx issue

KM · « **Reply #246 on:** May 18, 2007, 02:38:22 am »

anyone wondering, snippy did change his mind and decided to give me some useful information to find out what the problem was... the reason it wasn't going online and looking up hostnames? it was on offline mode...

KM · « **Reply #247 on:** May 18, 2007, 03:31:05 am »

also probably worth putting a link in this thread, a small bug in b12/13 with #c10#, it will be fixed in the next update but i don't consider it urgent enough to need an update (mainly because #c10# is grey, there are over a hundred other ones that can be used for grey...)

https://forum.winmxworld.com/index.php?topic=4776.0.html

Victim · « **Reply #248 on:** May 18, 2007, 05:12:38 am »

Hey is the Wcs 1.8 B12 & B13 Gunna be added to WinmxWorld Archive Soon?

Thanks

Micromecca · « **Reply #249 on:** May 18, 2007, 09:54:04 pm »

K Thank you !

The problem I had with a bot not being able to view logins was easily solved by using the new CustomCommand function, really impressed with that !

I'd still really love to see #NEWLINE# availble in notice if you could possibly cram it into your next release

Many Thanks

KM · « **Reply #250 on:** May 19, 2007, 03:13:14 am »

the bot should see the login announcements in b12/13 anyway, that was also changed so it should see them as normal messages from the servers username (unless you used /notice or something at the start, which isn't required and just makes announcements harder to pick up by bots)

Bearded Blunder · « **Reply #251 on:** May 19, 2007, 08:31:26 am »

turns out the only way i could get the bot reading them *was* by using /notice & then only after i started modifying the *correct* bot config..

KM · « **Reply #252 on:** May 19, 2007, 11:58:41 am »

yes, it helps to edit the right bot config... lol

btw, it has been pointed out that using MOTDLine= on its own without MOTD= causes the MOTD to duplicate when doing a /reload, this had been mentioned before but I believe I misunderstood the first time and misunderstood what was being said (it is after all meant to add a line to the end of the MOTD... lol)

If you consider it a bug or not is a matter of perspective, the intended purpose of that entry in a config file is to add a line to the end of the MOTD, so in that case it works fine and isn't a bug to do that - however someone would probably expect it to reset the MOTD if you only used MOTDLine= so might think of it as a bug

My opinion on if it's a bug or not? it's more of an undocumented behaviour which some may find undesireable

[edit]just noticed this mentioned in the "WCS Glitch" thread... should probably have answered there, oh well...[/edit]

Micromecca · « **Reply #253 on:** May 19, 2007, 03:52:42 pm »

This may be a little bug I've spotted...

If I perform: /forcelogin Bot 000_43143 BotPassword

The server shows this on my WinMX screen whilst logged in as *+ (although it doesnt change my access)

Bot 000_43143 Access set to: *b+
Î¥Îî¢rôÎ¥Îê¢¢â 666_34614 Has changed your Access to: *b+

maybe its supposed to mirror this to my screen, I'm not sure so thought I'd mention this.
It only appears to do this with a bot password with 'b' in access

KM · « **Reply #254 on:** May 19, 2007, 04:38:22 pm »

I forgot to mention on the original announcement that I also changed duplicate name detection so if a duplicate user joins from the same IP Address, the old one is kicked, instead of the new one being blocked from joining. This should solve issues with ghost users.

as for that forcelogin thing... it doesn't seem to do it here :-S come find me in the winmxworld room...

nylly444 · « **Reply #255 on:** May 20, 2007, 03:45:38 pm »

Too bad it doesn't work when the IP address changes...

* nylly444 is still ghosting...

KM · « **Reply #256 on:** May 20, 2007, 04:05:59 pm »

indeed, not much can be done if your connection drops and IP changes, it won't get any sort of connection error, and you can't be timed out in under 6 minutes (because winmx may go up to 5 minutes without sending anything)... but it will at least help when the IP Address doesn't change

nylly444 · « **Reply #257 on:** May 28, 2007, 05:55:19 pm »

Seems I encountered that bug KM mentioned at some point - my WCS crashed twice after the same user entered.
Guess DNS resolution IS still buggy.

* nylly444 blames KM

Bearded Blunder · « **Reply #258 on:** June 03, 2007, 09:39:01 pm »

Can WCS 1.8 have a /listhidden command? or the output from /who to bots actually indicate the status?
(for obvious reasons.. the colour coding used in normal /who output doesn't show....)

Victim · « **Reply #259 on:** June 05, 2007, 07:10:09 am »

WCS 1.8rc 3 Was Released Not Long Ago

Thanks For That KM

Author Topic: WCS (Read 57881 times)

KM

KM

KM

Micromecca

KM

KM

Micromecca

KM

KM