Author Topic: WCS (Read 59697 times)

Bearded Blunder · « **Reply #280 on:** June 26, 2007, 02:47:53 am »

just set their textformat to something without $TEXT$
then have a bot echo what it sees them say in /opmsg
3.31 clients (& those in bot mode) will still see what they type

Micromecca · « **Reply #281 on:** June 26, 2007, 02:59:47 am »

thanks il give that a try

~~James420~~ · « **Reply #282 on:** June 26, 2007, 07:44:22 pm »

I believe KM would add this a different way. He plans on adding some sort of system for message reporting like that and other stuff, just not sure when that will be.

Bearded Blunder · « **Reply #283 on:** June 27, 2007, 02:57:19 am »

i was merely suggesting a workaround for the current version

Micromecca · « **Reply #284 on:** July 08, 2007, 11:57:56 pm »

Just installed the latest rc4 of WCS to test and i get the following message...

08/07/2007 19:55:21 [C0] Illegal Name Attempted 'Î¥Îî¢rôÎ¥Îê¢¢â 666_57634' join 'room_6444D04A682A'

be very grateful if you could shed some light on this KM, cheers

*^*Åü§§ïëgïrl*^* · « **Reply #285 on:** July 09, 2007, 01:59:30 am »

I have also received the illegal character message

09/07/2007 12:41:00 [C0] Illegal Name Attempted 'AFK_Åü§§ïëgïrl770_28198'

However once I removed the ascii from my nic..

09/07/2007 12:41:23 [C0] AFK_Aussiegirl770_28198 Joined

Can we please have Ascii allowed ? Apart from a lot of roomies having Ascii in their nics, 3 of the 4 hosts also have ascii. If the server is auto-updated we're in a little bit of trouble for hosting.

SamSeeSam · « **Reply #286 on:** July 09, 2007, 04:21:44 am »

I don't know remove each ascii letter and see the cause. Ascii worked ok for ema dn many other in the wmw room too... which is b11

Cheers

GriZz · « **Reply #287 on:** July 09, 2007, 04:23:57 am »

I'm having the same problem with the Ascii hope this is fixed soon but for now will stay with WCS rc3...

*^*Åü§§ïëgïrl*^* · « **Reply #288 on:** July 09, 2007, 04:45:44 am »

.

Quote from: SamSeeSam on July 09, 2007, 04:21:44 am

I don't know remove each ascii letter and see the cause. Ascii worked ok for ema dn many other in the wmw room too... which is b11

Cheers

Thanks for the suggestion Sam but trying the characters one by one to find the problem one is far too time consuming. We have a lot of wide and varied fonts used in our room to test that theory.

Quote from: Rëpö/V\äñ on July 09, 2007, 04:23:57 am

I'm having the same problem with the Ascii hope this is fixed soon but for now will stay with WCS rc3...

Ditto.

Bearded Blunder · « **Reply #289 on:** July 09, 2007, 04:48:49 am »

have a look in your config to see if there's anty clues in the blocked names section

*^*Åü§§ïëgïrl*^* · « **Reply #290 on:** July 09, 2007, 05:18:25 am »

erm... blocked names ? There isn't one in a standard wcs config which I'm using. I'm using an identical config from rc3 to rc4.

Different port tried : result=no entry for ASCII nic
Blocked word list=disabled : result= No ASCII entry
Fancy Entry disabled/enabled: result=No ASCII entry
JoinFlood disabled/enabled: result=No ASCII entry
NameTrim full/partial/none: result=No ASCII entry

Nic change in WinMX from ASCII character to non-ASCII: result=Room entry permitted.

Bearded Blunder · « **Reply #291 on:** July 09, 2007, 04:10:26 pm »

indeed, tried rc4 *just* long enough to determine my bot won't enter (name isn't plain alpha-numeric) returned to rc3

PenMax · « **Reply #292 on:** July 09, 2007, 05:23:48 pm »

Yep ... plain 'Network Identity' characters get u into ur own room using d new WCSv1.8rc4, tho it handles odd characters alright in ur ChannelName. Strange how the upgrade goes forward yet backward as well.

PenMax · « **Reply #293 on:** July 09, 2007, 06:29:22 pm »

Oops ... all ur propective Users have to use plain 'Network Identity' characters to get into ur room as well using d new WCSv1.8rc4!!! Remarkable upgrade!!!

Micromecca · « **Reply #294 on:** July 09, 2007, 07:00:55 pm »

RC5 has been released guys which has fixed the bug

http://www.kingmacro.net/

reef · « **Reply #295 on:** July 09, 2007, 07:06:57 pm »

I'm sure it will be resolved soon enuf penmax...have u ever made
a mistake in yer life? it's those kinda ungrateful comments in the
first place that helped chase km away from other areas of winmx...would
ya be happy if there were no more wcs updates to look forward too?

reef · « **Reply #296 on:** July 09, 2007, 07:08:39 pm »

Oh its been fixed as i was making my previous post.... imagine that

PenMax · « **Reply #297 on:** July 12, 2007, 02:27:45 pm »

I downloaded WCS 1.8rc5-Win32 into the WCS-Version-of-my-ChatRoom Folder and left-clicked [Yes] to 'Replace' the offender, and all is well with the World again!

A quote from KM ...

Quote

I blame the same fairy that blew up one of the hard drives in my home server last night... (causing a few hours outage, and causing me to get up for work late because I use the server as my alarm clock - and I still insist it has nothing to do with my rewiring the power supply whilst it was turned on)

LOL, soundz like me!!

Take it easy man, we all still love ya deep down!!

Real Red · « **Reply #298 on:** August 05, 2007, 08:49:33 am »

do we use the old config from 1.7.4 for the new wcs 1.8.6.???

Bearded Blunder · « **Reply #299 on:** August 05, 2007, 09:00:06 am »

you can.. it works, but it won't take advantage of new features without some editing

Author Topic: WCS (Read 59697 times)

Micromecca

Micromecca

Micromecca