Author Topic: WSC & Metis Bot and other quick questions (Read 2399 times)

Tish · « **on:** March 19, 2006, 11:42:26 pm »

I am trying to set up a WSC room.... I am using a Metis Bot that has been patched however when I try to enter the room I get the following error message - "An invalid Argument was encountered". I get this message as each line of the welcome message loads.

Does not happen on a non-patched metis bot. This happens if I enter any room that is running WSC.

Also, is there any way of turning the color Off... sometimes you have people changing their colors in your room to try different ones...is a bit of a pain... Yes color is nice but not a necessity.

The reason I'm trying this is because you can host and use less bandwidth and if the host's winmx crashes the room survives.

If all the hosts use the same port settings will the room name and number stay the same?

Is there a link for setting up Shareguard or help with it please?

I appologize if you have already answered these question somewhere in the forum. Took a quick look but didn't see them.

thank you

Me Here · « **Reply #1 on:** March 21, 2006, 02:58:39 am »

Hi Tish,

Ok, to start with its not uncommon for the Metis to encounter that invalid error on entry.. Mine does it often, I am not aware of the cause or the fix, but you can just click ok, ok, ok .. and all is fine.

Now metis along with lots of MX Control programs dont like the WCS default port of '3'.. make sure in your WCS config.ini file you change this and use a number higher then 1024 to ensure that the bots and such will like the room ok. Keeping the same port number for all hosts is ok and I recommend it however, the room number is also made up of the hosts IP number so its impossible to swith hosts and not change names.

When running a bot in a color server its very important to use what is called bot mode. This can be achieved by typing /bot into the Metis screen. When looking at the Chat channel you should see number codes, not colors. You can also admin your bot, giving it a 'b' access in WCS to ensure its not going to get confused reading color codes and not function correctly.

Funny you should ask about the shareguard, Ghost is been working on that and should have it done shortly for you.

I hope this helps you some. Let me know if you have any other questions regarding the wcs or bots..

Tish · « **Reply #2 on:** March 22, 2006, 05:19:13 am »

Thank you Me Here

Glad to know I'm not the only one with that problem with the Metis Bot. Thank you for the tips in running it in Bot mode. I will set up a bot only password which it will auto admin to. A non patched bot does work and will kick etc.

I do have the port in the config file changed from "3" and a higher number then "1024". I will mess with it more on the weekend.

My shareguard just doesn't seem to want to work. It enters the room fine...but when you type !find it doesn't find. So I'm not sure what I'm doing wrong or how to set it up properly. I do let it scan 100% before I test it.

The only other question I have is is it possible to disable color in the room?

Thanks again

Me Here · « **Reply #3 on:** March 22, 2006, 06:44:46 am »

If you dont want color in the server its prolly only possible to get rid of it completely by using WinMx to host your channel with. Ouka has a function to disable color but the other servers do not.

~~GnarlySnarly~~ · « **Reply #4 on:** March 22, 2006, 10:04:23 am »

I don't use metis.. but i *think* you can kill the colors

afaik, setting FancyEntry=0 and not giving anyone 'C' access should do it.
which means setting the defailt access to something like 'Aam' or maybe Aamb'

~~Røçkåfë££ë® §kåñK~~ · « **Reply #5 on:** March 22, 2006, 11:48:56 am »

To kill colours for bot to work make sure the bot has small b in its access for WCS and this disables colours for the bot or type /bot

Should fix any problems shareguard will be the same problem the colours in WCS are stopping it reading u type !find so make sure it has the same thing