WinMX World :: Forum

Metis Scripts and Help => Metis Script Help => Topic started by: birdman on July 02, 2009, 04:10:06 pm

Title: Client on enter
Post by: birdman on July 02, 2009, 04:10:06 pm
A friend asked me if there was a script for mettis that could identify a users chat client on enter with the option to kick  and to send a message  as he does not like chat clients only winmx users sharing files in his room, i know theres a transfer and client script on here but that shows every client that enters as winmx 3.53 lol
Title: Re: Client on enter
Post by: Forested665 on July 03, 2009, 04:16:44 pm
The clients can be made to report whatever version they wish provided the source code is available.(includes majority of the chat clients) This is especially easy in robo/metis without the sourcecode as its stored in a setting file.
Title: Re: Client on enter
Post by: Pri on July 03, 2009, 05:38:11 pm
If you are running WCS, RSWCS and maybe Eagles server (I've not used it) you can /stats a user as they enter the room and it will display what client the user is using and then you can setup a trigger that responds to 'Client: XXXXX' and XXXXX = the clients you don't want and have the Bot kick/ban. Of course as Forested says clients can change what they report. I know WPCC will let the user put whatever they want in there I don't think most users change it by default.
Title: Re: Client on enter
Post by: birdman on July 03, 2009, 06:18:56 pm
My friend is using wcs, can mettis see the /stats of a user on enter and then check the client and kick and message if required is there a script ?
Title: Re: Client on enter
Post by: Forested665 on July 03, 2009, 06:54:30 pm
You can make one. im not sure exactly how it would work unless it waits so many seconds and if it doesnt see Winmx version XXX it kicks that user.
But then all the person has to do is say it once they figure it out.
What room is this thats not wanting people to have chat clients?
Title: Re: Client on enter
Post by: wonderer on July 04, 2009, 12:07:51 am
There are many rooms having objections against bots and chat clients and for different reasons.
In my opinion is WinMx a chatclient with a big community having the nice option to share files but sharing should not be a must.
As stated above, any client can report whatever client it wants to be just like it can report any connection type from unknown to t3 or faster and number of shared files. In some cases it might be possible to detect the real client type but that is beyond the possibilities of Metis.
Why should a host running a chatserver be against chatclients, is it not the goal of a chatroom to chat in the first place?
It is just as ridiculous to ban zero file share on enter, it happens more than once that WinMx wrongly reports zero files. And even when the zero is real, did we not all start at zero? A bit hostile and not very smart to reject possible newbies if we want our community to grow.
But this is only my opinion and also the reason why I will not put any effort in making such a script.
Title: Re: Client on enter
Post by: Guest on July 18, 2009, 12:59:58 pm
Something alo the lines of:

Code: [Select]
<OnJoinRoom type="script">
<out type="push" extdata="ClientCheck">0</out>
</OnJoinRoom>

<OnEnter type="script">
<out type="push" extdata="ClientCheck">1</out>
<out type="push" extdata="ClientName">%NAME%</out>
<out>/hidecmd /stats %USERVAR[ClientName]%</out>
</OnEnter>

<command type="script" condition="==" lvalue="%USERVAR[ClientCheck]%" rvalue="1">
<in>Client: %PARAM%</in>

<out condition="_?" lvalue="%PARAM%" rvalue="RoboMX">/kick %USERVAR[ClientName]%</out>

<out type="push" extdata="ClientCheck">0</out>
</command>

Should work on RSWCS may need adapting for other servers.
Title: Re: Client on enter
Post by: Pri on July 18, 2009, 11:12:40 pm
Something alo the lines of:

Code: [Select]
<OnJoinRoom type="script">
<out type="push" extdata="ClientCheck">0</out>
</OnJoinRoom>

<OnEnter type="script">
<out type="push" extdata="ClientCheck">1</out>
<out type="push" extdata="ClientName">%NAME%</out>
<out>/hidecmd /stats %USERVAR[ClientName]%</out>
</OnEnter>

<command type="script" condition="==" lvalue="%USERVAR[ClientCheck]%" rvalue="1">
<in>Client: %PARAM%</in>

<out condition="_?" lvalue="%PARAM%" rvalue="RoboMX">/kick %USERVAR[ClientName]%</out>

<out type="push" extdata="ClientCheck">0</out>
</command>

Should work on RSWCS may need adapting for other servers.


This is exactly what I described in my above post and that is how I would write it. Although I probably wouldn't include the the ClientCheck 0/1 as it seems redundant.
Title: Re: Client on enter
Post by: ñòóKýçrÕôK on July 20, 2009, 03:03:54 pm
As we do not support Richy or his hacked up version of KM's wcs I will respectfully ask that it not be named again in this thread or any other. I will personally lock the topic myself and further steps may be taken to ensure that we do not refference it in this thread or any other except for the threads warning of its backdoor capabilities. I personally thank you for posting but I again ask that you do not refference it again.
Title: Re: Client on enter
Post by: Pri on July 20, 2009, 11:42:17 pm
As we do not support Richy or his hacked up version of KM's wcs I will respectfully ask that it not be named again in this thread or any other. I will personally lock the topic myself and further steps may be taken to ensure that we do not refference it in this thread or any other except for the threads warning of its backdoor capabilities. I personally thank you for posting but I again ask that you do not refference it again.

Don't you think this stance is a bit heavy handed. I personally wouldn't use it but I think banning the naming of it is a step to far. Also I just wanted to note that the script posted above will work fine on the vanilla WCS.
Title: Re: Client on enter
Post by: ñòóKýçrÕôK on July 21, 2009, 05:58:52 am
Don't you think this stance is a bit heavy handed. I personally wouldn't use it but I think banning the naming of it is a step to far. Also I just wanted to note that the script posted above will work fine on the vanilla WCS.

Richy purposely wrote malicious backdoor commands into his program and it is not supported by anyone on this site or in the WMW helproom and to be perfectly honest, although I could be wrong on the matter, I don't believe you'll find another supervisor on this site that will support it or offer help with it either. I don't believe this stand requires anymore explanation nor is it up for discussion. Heavy handed or not, I ask again that you do not refference it again please.
Title: Re: Client on enter
Post by: Pri on July 21, 2009, 09:06:39 am
My point is telling people never to say the name of it is not the right thing to do. If government told you not to talk about something they consider depraved you'd be up in arms so why should you feel it is your right to institutionalise the same rules here?

I'm fully aware of the malicious commands that he placed in RSWCS and I do not support RSWCS and I'll never run it or tell anyone else it's a good idea to do so but to simply say we can't even say the name of it is ridiculous.

I'm not here to cause trouble but this 'Rule' or 'Stance' is in poor taste. If this is a Forum we should be able to talk about anything WinMX Related in my opinion. Lets just remind ourselves that we are talking about a Chat Server and not Neo-Nazism I don't see the harm in saying the servers title even though we know its untrustworthy.

I understand that you guys are maintaining the Forum and you guys make the Rules but this is just silly.
Title: Re: Client on enter
Post by: ñòóKýçrÕôK on July 21, 2009, 01:20:01 pm
You bring it up today. Someone else brings up tomorrow. Others bring it up here n there and randomly down the road. Next thing you know a user comes on the forum looking for a chat server. "Hmmmm, seen that server all over the forum, reckon I'll try it out". User posts "I can't find the link to that server, anyone know it?" . Next thing you know some scatterbrained moron posts a link to the site where it can be located. Following me here? Bam, we've just told people where to find it. I say again, you may not like it but that's how it is. This is a public forum but we take our responcibility to this network extremely serious. We would appreciate no future refference to Richy's hacked up version of KM's software. And you can't say this wouldn't happen because you know it would. So let's move on. If you wouldn't support it then you understand why we wouldn't support it or want refference to it on this site.
Title: Re: Client on enter
Post by: Stevi on July 21, 2009, 02:36:36 pm
This is starting to get off topic. Please stick to the topic, or I will lock this thread.
Title: Re: Client on enter
Post by: wonderer on July 22, 2009, 08:36:40 pm
Metis is able to read most if not, all messages issued in a room. Some may need some special treatment.
Metis can't however identify a users chat client on it's own yet.

So, lets say the joinmessage of the room is "Name has entered with" Client, issued by the server.
you may use as a trigger Name has entered with %PARAM%

You will have to find the messagetype   of the onjoin message and use an metiscommand  to get the %PARAM%

Code: [Select]
<command>
<in>Name has entered with %PARAM%</in>
<out>client %PARAM%</out>
</command>
<in>
Title: Re: Client on enter
Post by: birdman on July 22, 2009, 09:16:02 pm
Ok say for example someone wanted to stop wpcc client from entering their room for what ever reason what script could they use i know fx server displays peoples client on enter but wcs does not infact if you do a /stats on a user in a wcs room with wpcc it shows as winmx 3.53 lol
Title: Re: Client on enter
Post by: Pri on July 23, 2009, 06:33:00 am
It depends birdman. If you /stats someone as they enter WCS is likely to say it is WinMX 3.53 however if you wait a little while for WCS to determine which client it is the information on the /stats will change. However the WPCC user themselves can put in any information they want in to the box to make WPCC appear to be any client.

It's an annoying client that I personally dislike although we don't ban its usage or anything like that.
Title: Re: Client on enter
Post by: reef on July 23, 2009, 10:08:07 am
WPCC does have an option to not report client name and version, but i believe transfer status always reports as
Transfer Status: WPCC v0.1 beta 8.5 of Emulator available (or whatever version number). Correct me if i'm wrong.

The below script is a modified version of Guru's Transfer Status for WCS... it should do the trick in eliminating WPCC users from your room.

Code: [Select]
<config>

<OnEnter type="script">
<out type="sleep" extdata="10000"/>
<out type="push" extdata="CLIENTCHECK">1</out>
<out type="push" extdata="USERNAME">%NAME%</out>
<out type="push" extdata="USERIP">%IP%</out>
<out>/hidecmd /stats %USERVAR[USERNAME]%</out>
</OnEnter>

<command mode="thread" type="script" condition="==" lvalue="%USERVAR[CLIENTCHECK]%" rvalue="1">
<in>Transfer Status: %PARAM%</in>
<out type="push" extdata="TRANSTATUS">%PARAM%</out>
</command>

<command mode="thread" type="script" condition="==" lvalue="%USERVAR[CLIENTCHECK]%" rvalue="1">
<in>Client: %PARAM%</in>
<out type="push" extdata="USERCLIENT">%PARAM%</out>
<out>/hidecmd /gnotice @ #c7#User Name: #c3#$USERNAME$ #c7#Client: #c3#$USERCLIENT$</out>
<out delay="100" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC">/hidecmd /gnotice @ #c9#Illegal Client Detected: #c3#$USERCLIENT$</out>
<out delay="100" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC">/hidecmd /gnotice @ #c8#$USERNAME$ #c1#Banned For Illegal Client</out>
<out delay="100" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC">/hidecmd /kickban $USERNAME$</out>
<out type="goto" extdata="6" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC"></out>

<out>/hidecmd /gnotice @ #c7#User Name: #c3#$USERNAME$ #c7#Transfer Status: #c3#$TRANSTATUS$</out>
<out delay="100" condition="?" lvalue="$TRANSTATUS$" rvalue="WPCC">/hidecmd /gnotice @ #c9#Illegal Client Detected: #c3#WPCC #c1#(#c8#Manipulated To Report as #c3#$USERCLIENT$#c1#)</out>
<out delay="100" condition="?" lvalue="$TRANSTATUS$" rvalue="WPCC">/hidecmd /gnotice @ #c8#$USERNAME$ #c1#Banned For Illegal Client</out>
<out delay="100" condition="?" lvalue="$TRANSTATUS$" rvalue="WPCC">/hidecmd /kickban $USERNAME$</out>

<out type="pop" extdata="USERIP"/>
<out type="pop" extdata="USERCLIENT"/>
<out type="pop" extdata="CLIENTCHECK"/>
<out type="pop" extdata="USERNAME"/>
<out type="pop" extdata="TRANSTATUS"/>
</command>

</config>

Not sure why you'd want to keep WPCC users out though  :S
Title: Re: Client on enter
Post by: birdman on July 23, 2009, 10:58:54 am
I used wpcc as an example but basicaly what i was askin was for the ability to block any type of chat client other than winmx from a room if the host desired for what ever reason, the script looks good would it be possible to add other clients and also before removal of the person to send them a message stating why they are being removed ?
Title: Re: Client on enter
Post by: ']['affy on July 23, 2009, 02:32:47 pm
what worries me more about this is that if every host added these sort of scripts.  We wouldnt have anyone left on mx, as not many ppl download on mx these days they only upload, they get there files from other sources most use bots or chat clients for just chatting.
Title: Re: Client on enter
Post by: Forested665 on July 23, 2009, 10:11:45 pm
the whole point in making people park in your room to download a file is to bring users into your room who wouldnt normally be there. by disregarding anyone who wishes to be there JUST to talk you are bypassing the point of having them in the room as all your files and theres can be found via search.
Title: Re: Client on enter
Post by: birdman on July 23, 2009, 10:38:55 pm
I agree that loads of people use chat clients on winmx now mainly wpcc, i personaly see no point in its use as to me i want winmx running and sharing files a chat client offers nothing to the network, granted some people have no alternative but to use a chat client due to whatever circumstances but right now i would say theres more people using bots and chat clients than using winmx, its crazy !
Title: Re: Client on enter
Post by: Forested665 on July 24, 2009, 12:07:26 am
people use winmx to chat. But if your not sharing anything and your running secondary there isnt much point in using winmx itself over a lighter chatclient.
Title: Re: Client on enter
Post by: Guest on August 08, 2009, 08:05:12 pm
The "ClientCheck" mentioned earlier in the thread is used to separate different commands.

Most people run many scripts in metis, and this will avoid cross over of triggered commands from one script to another.  If the ClientCheck is 0 then the command will not be triggered by a /stats, unless its triggered as part of the actual script the command is included in.  Clearly by not including blocks like this you in effect allow metis to eat up pc resources for no reason at all and possibly even output totally inaccurate information!
Title: Re: Client on enter
Post by: Pri on August 09, 2009, 01:37:47 am
Except that the bot is the one doing the /stats so only it will be receiving the information. When other users in the room do a /stats it isn't displayed publicly thus the bot wont see it and run that part of the script. The only occasion for it to run when it sees a /stats is when someone enters making the check redundant. If you wanted to lock it down so others in your room couldn't cheat the system to get someone kicked when they aren't using WPCC (which is possible even with the above script and running a bot in your room for quickness) you could lock it down to a username (server000_00000) to make sure only input from the rooms Server is accepted for that /stats command.

Title: Re: Client on enter
Post by: Guest on August 10, 2009, 08:38:50 am
What i mean is, if you have several scripts with parts of the stats triggers, such as say an access lookup on one script, and a staytime lookup and post, then by doing a /stats it will trigger these.

By having a ClientCheck variable switch (on/off) it will only trigger if someone enters rather than if the bot does /stats at a later stage.
Title: Re: Client on enter
Post by: Pri on August 10, 2009, 10:36:16 am
That does make sense.
Title: Re: Client on enter
Post by: Forested665 on August 10, 2009, 05:46:39 pm
what about other clients that meet these requirements. doesnt winzo or moonmx have file transfer? they can just as easily meet your weird little demands.
I beleive all your going to acheive with this is hindering 3rd party developement should you convince a bunch of people to use it. and even still robo can report as winmx and share a fake list of files.
Title: Re: Client on enter
Post by: wonderer on August 10, 2009, 10:42:42 pm
This seems a bit off topic to me, you must have been intending to post in another thread
Title: Re: Client on enter
Post by: Stevi on August 11, 2009, 05:37:35 am
I dont see how this is off topic. I pertains to the original post at hand.

Using a script like this could hinder third party development when enforced by a large number of rooms. This is a great debate that, from what i have seen, has not gotten out of hand.
Title: Re: Client on enter
Post by: wonderer on August 11, 2009, 09:01:25 am
I fail to see the relation between "client on enter" and "filetransfer"
The thread is about detecting client type and not about client abilities in my humble opinion
Title: Re: Client on enter
Post by: Pri on August 11, 2009, 03:44:49 pm
I don't see a lot of rooms using this. And I think that to many people abuse WPCC as a parking tool than a chat client. I doubt Emulator or anyone else is doing to stop developing their clients because of misuse and hosters should be allowed to deny whichever clients they want after-all it is they who are giving up their resources to allow a client to enter.

For many years we have seen rooms that deny based on files shared (0 = Kick is common in Topic Titles) this is no different except now the Chat only users are using WPCC and to a much lesser extent RoboMX to skirt around these blocks requiring more imaginative ways to stop what you don't want in your room.

Now I personally don't block WPCC clients in my room for a couple of reasons these are just personal to me and my room obviously.

1. Some of my users don't ever share files but they do chat and they prefer the way WPCC works
2. Some of my users access the room from Work and use WPCC for that as they are not going to be sharing files.

But last year WPCC was a problem with some users parking 3-4 separate WPCC's in my room at once. Which is something I do not want. And at that time we decided to block WPCC we have since lifted that as its no longer a problem but when I visit other rooms I often see room counts in the channel list of 50-60-70 and enter to find 45-50 are WPCC parkers. Which means the room is devoid of files and of chat. A waste on resources for the hoster and the network keeping these clients connected in my opinion.

You cannot run multiple WinMX's at once without using a 3rd party tool and I think WPCC should work the same way because spawning multiple instances has done more harm than good not just to the network in the increased redundant load but also to the reputation of WinMX, all to often I hear people saying 'WinMX is just full of parkers these days anyway' and when you ask them what they mean WPCC is always mentioned. You've all seen it. This client is like some kinda cancer.
Title: Re: Client on enter
Post by: birdman on August 11, 2009, 05:01:02 pm
I have tried the script posted in this thread by Reef to test if it could stop a wpcc client but it didnt work as the wpcc showed up as a winmx 353 client, i use wcs which is what the script reef wrote was for but for me it didnt work, i also think a host has the right to say what he wants in his room and have the ability to block what he or she does not want in their room for what ever reason which is why i started this topic but as yet no script for mettis has worked for me maybe it needs a chat server level programe.
Title: Re: Client on enter
Post by: Pri on August 11, 2009, 05:57:16 pm
It works Birdman you just need to enter a delay. When you first stats a WPCC user as they enter WCS says it is WinMX 3.53 but after a few seconds it refreshes the client information to correctly report WPCC. Add in a little delay after the user has entered before the /stats executes and your be fine.
Title: Re: Client on enter
Post by: birdman on August 11, 2009, 06:04:55 pm
Yes my apologies reefs script does work i dont know why it didnt for me before i guess i did something wrong lol anyway what would the line be to send the user a message  before they are removed from the room so they know why, a line added into reefs script ?
Title: Re: Client on enter
Post by: reef on August 11, 2009, 08:51:14 pm
This will send them a PM message informing them they were banned for WPCC
Also added a 5 second delay before executing the stats command, like Pri mentioned

Code: [Select]
<config>

<OnEnter type="script">
<out type="sleep" extdata="10000"/>
<out type="push" extdata="CLIENTCHECK">1</out>
<out type="push" extdata="USERNAME">%NAME%</out>
<out type="push" extdata="USERRAWNAME">%RAWNAME%</out>
<out type="push" extdata="USERIP">%IP%</out>
<out delay="5000">/hidecmd /stats %USERVAR[USERNAME]%</out>
</OnEnter>

<command mode="thread" type="script" condition="==" lvalue="%USERVAR[CLIENTCHECK]%" rvalue="1">
<in>Transfer Status: %PARAM%</in>
<out type="push" extdata="TRANSTATUS">%PARAM%</out>
</command>

<command mode="thread" type="script" condition="==" lvalue="%USERVAR[CLIENTCHECK]%" rvalue="1">
<in>Client: %PARAM%</in>
<out type="push" extdata="USERCLIENT">%PARAM%</out>
<out>/hidecmd /gnotice @ #c7#User Name: #c3#$USERNAME$ #c7#Client: #c3#$USERCLIENT$</out>
<out delay="100" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC">/hidecmd /gnotice @ #c9#Illegal Client Detected: #c3#$USERCLIENT$</out>
<out delay="100" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC">/hidecmd /gnotice @ #c8#$USERNAME$ #c1#Banned For Illegal Client</out>
<out delay="100" type="pm" extdata="$USERRAWNAME$" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC">$USERNAME$ Your Banned For An Illegal Client: WPCC</out>
<out delay="5000" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC">/hidecmd /kickban $USERNAME$</out>
<out type="goto" extdata="7" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC"></out>

<out>/hidecmd /gnotice @ #c7#User Name: #c3#$USERNAME$ #c7#Transfer Status: #c3#$TRANSTATUS$</out>
<out delay="100" type="pm" extdata="$USERRAWNAME$" condition="?" lvalue="$TRANSTATUS$" rvalue="WPCC">$USERNAME$ Your Banned For An Illegal Client: WPCC</out>
<out delay="100" condition="?" lvalue="$TRANSTATUS$" rvalue="WPCC">/hidecmd /gnotice @ #c9#Illegal Client Detected: #c3#WPCC #c1#(#c8#Manipulated To Report as #c3#$USERCLIENT$#c1#)</out>
<out delay="100" condition="?" lvalue="$TRANSTATUS$" rvalue="WPCC">/hidecmd /gnotice @ #c8#$USERNAME$ #c1#Banned For Illegal Client</out>
<out delay="5000" condition="?" lvalue="$TRANSTATUS$" rvalue="WPCC">/hidecmd /kickban $USERNAME$</out>

<out type="pop" extdata="USERIP"/>
<out type="pop" extdata="USERCLIENT"/>
<out type="pop" extdata="CLIENTCHECK"/>
<out type="pop" extdata="USERNAME"/>
<out type="pop" extdata="USERRAWNAME"/>
<out type="pop" extdata="TRANSTATUS"/>
</command>

</config>
Title: Re: Client on enter
Post by: birdman on August 11, 2009, 09:37:30 pm
nice one Reef that works a treat!   is it possible to add other clients to it like for example robomx and so on ?
Title: Re: Client on enter
Post by: reef on August 12, 2009, 07:05:56 am
Added RoboMX & Rabbit... not sure what else could be added other than 3.31 (which nushi normally reports as).Ouka chat client cant get into wcs rooms anyways, unless fancy entry message is turned off.
Increased the delay to 10 seconds
Added a privnotice message to the user (in case pm fails)
Added a tooltip popup that will alert you when an unwanted client enters
Changed it so that it bans and kicks the IP rather than name (in case they change names after entering)
Ban Time 48 hrs rather than permanent

I'm sure this all could be done a better way. But it works.

Code: [Select]
<config>

<OnEnter type="script">
<out type="sleep" extdata="10000"/>
<out type="push" extdata="CLIENTCHECK">1</out>
<out type="push" extdata="USERNAME">%NAME%</out>
<out type="push" extdata="USERRAWNAME">%RAWNAME%</out>
<out type="push" extdata="USERIP">%IP%</out>
<out type="push" extdata="USERHOSTNAME">%HOSTNAME%</out>
<out delay="10000">/hidecmd /stats %USERVAR[USERNAME]%</out>
</OnEnter>

<command mode="thread" type="script" condition="==" lvalue="%USERVAR[CLIENTCHECK]%" rvalue="1">
<in>Transfer Status: %PARAM%</in>
<out type="push" extdata="TRANSTATUS">%PARAM%</out>
</command>

<command mode="thread" type="script" condition="==" lvalue="%USERVAR[CLIENTCHECK]%" rvalue="1">
<in>Client: %PARAM%</in>
<out type="push" extdata="USERCLIENT">%PARAM%</out>

// RoboMX
<out condition="?" lvalue="$USERCLIENT$" rvalue="Robo">/hidecmd /gnotice @ #c9#User Name: #c10#$USERNAME$ #c9#Client: #c10#$USERCLIENT$</out>
<out delay="100" condition="?" lvalue="$USERCLIENT$" rvalue="Robo">/hidecmd /gnotice @ #c9#Illegal Client Detected: #c10#$USERCLIENT$</out>
<out delay="100" condition="?" lvalue="$USERCLIENT$" rvalue="Robo">/hidecmd /gnotice @ #c9#$USERNAME$ #c1#Banned For Illegal Client</out>
<out delay="100" condition="?" lvalue="$USERCLIENT$" rvalue="Robo">/hidecmd /banip $USERIP$ 2880</out>
<out delay="100" type="pm" extdata="$USERRAWNAME$" condition="?" lvalue="$USERCLIENT$" rvalue="Robo">$USERNAME$ Your Banned For An Illegal Client: $USERCLIENT$</out>
<out delay="5000" condition="?" lvalue="$USERCLIENT$" rvalue="Robo">/hidecmd /privnotice $USERNAME$ #c1#You've Been Banned For An Illegal Client</out>
<out delay="5000" condition="?" lvalue="$USERCLIENT$" rvalue="Robo">/hidecmd /kick $USERIP$</out>
<out delay="500" type="tooltip" condition="?" lvalue="$USERCLIENT$" rvalue="Robo">ILLEGAL CLIENT DETECTED\n\n$USERNAME$ - $USERHOSTNAME$ - $USERIP$\n\n$TRANSTATUS$\n\n$USERCLIENT$</out>
<out type="goto" extdata="32" condition="?" lvalue="$USERCLIENT$" rvalue="Robo"></out>

// Rabbit
<out condition="?" lvalue="$USERCLIENT$" rvalue="Rabbit">/hidecmd /gnotice @ #c9#User Name: #c10#$USERNAME$ #c9#Client: #c10#$USERCLIENT$</out>
<out delay="100" condition="?" lvalue="$USERCLIENT$" rvalue="Rabbit">/hidecmd /gnotice @ #c9#Illegal Client Detected: #c10#$USERCLIENT$</out>
<out delay="100" condition="?" lvalue="$USERCLIENT$" rvalue="Rabbit">/hidecmd /gnotice @ #c9#$USERNAME$ #c1#Banned For Illegal Client</out>
<out delay="100" condition="?" lvalue="$USERCLIENT$" rvalue="Rabbit">/hidecmd /banip $USERIP$ 2880</out>
<out delay="100" type="pm" extdata="$USERRAWNAME$" condition="?" lvalue="$USERCLIENT$" rvalue="Rabbit">$USERNAME$ Your Banned For An Illegal Client: $USERCLIENT$</out>
<out delay="5000" condition="?" lvalue="$USERCLIENT$" rvalue="Rabbit">/hidecmd /privnotice $USERNAME$ #c1#You've Been Banned For An Illegal Client</out>
<out delay="5000" condition="?" lvalue="$USERCLIENT$" rvalue="Rabbit">/hidecmd /kick $USERIP$</out>
<out delay="500" type="tooltip" condition="?" lvalue="$USERCLIENT$" rvalue="Rabbit">ILLEGAL CLIENT DETECTED\n\n$USERNAME$ - $USERHOSTNAME$ - $USERIP$\n\n$TRANSTATUS$\n\n$USERCLIENT$</out>
<out type="goto" extdata="21" condition="?" lvalue="$USERCLIENT$" rvalue="Rabbit"></out>

// WPCC Client Check
<out condition="?" lvalue="$USERCLIENT$" rvalue="WPCC">/hidecmd /gnotice @ #c9#User Name: #c10#$USERNAME$ #c9#Client: #c10#$USERCLIENT$</out>
<out delay="100" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC">/hidecmd /gnotice @ #c9#Illegal Client Detected: #c10#$USERCLIENT$</out>
<out delay="100" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC">/hidecmd /gnotice @ #c9#$USERNAME$ #c1#Banned For Illegal Client</out>
<out delay="100" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC">/hidecmd /banip $USERIP$ 2880</out>
<out delay="100" type="pm" extdata="$USERRAWNAME$" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC">$USERNAME$ Your Banned For An Illegal Client: $USERCLIENT$</out>
<out delay="5000" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC">/hidecmd /privnotice $USERNAME$ #c1#You've Been Banned For An Illegal Client</out>
<out delay="5000" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC">/hidecmd /kick $USERIP$</out>
<out delay="500" type="tooltip" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC">ILLEGAL CLIENT DETECTED\n\n$USERNAME$ - $USERHOSTNAME$ - $USERIP$\n\n$TRANSTATUS$\n\n$USERCLIENT$</out>
<out type="goto" extdata="10" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC"></out>

// WPCC Transfer Status Check
<out>/hidecmd /gnotice @ #c9#User Name: #c4#$USERNAME$ #c9#Transfer Status: #c4#$TRANSTATUS$</out>
<out delay="100" condition="?" lvalue="$TRANSTATUS$" rvalue="WPCC">/hidecmd /banip $USERIP$ 2880</out>
<out delay="100" type="pm" extdata="$USERRAWNAME$" condition="?" lvalue="$TRANSTATUS$" rvalue="WPCC">$USERNAME$ Your Banned For An Illegal Client: WPCC</out>
<out delay="100" condition="?" lvalue="$TRANSTATUS$" rvalue="WPCC">/hidecmd /gnotice @ #c9#Illegal Client Detected: #c8#WPCC #c1#(#c1#Manipulated To Report as #c4#$USERCLIENT$#c1#)</out>
<out delay="100" condition="?" lvalue="$TRANSTATUS$" rvalue="WPCC">/hidecmd /gnotice @ #c8#$USERNAME$ #c1#Banned For Illegal Client</out>
<out delay="5000" condition="?" lvalue="$TRANSTATUS$" rvalue="WPCC">/hidecmd /kick $USERIP$</out>
<out delay="500" type="tooltip" condition="?" lvalue="$TRANSTATUS$" rvalue="WPCC">ILLEGAL CLIENT DETECTED\n\n$USERNAME$ - $USERHOSTNAME$ - $USERIP$\n\n$TRANSTATUS$\n\n$USERCLIENT$</out>

<out type="pop" extdata="USERIP"/>
<out type="pop" extdata="USERCLIENT"/>
<out type="pop" extdata="CLIENTCHECK"/>
<out type="pop" extdata="USERNAME"/>
<out type="pop" extdata="USERRAWNAME"/>
<out type="pop" extdata="USERHOSTNAME"/>
<out type="pop" extdata="TRANSTATUS"/>
</command>

</config>
Title: Re: Client on enter
Post by: birdman on August 12, 2009, 08:21:05 am
Again this works sweet Reef nice one :)  although ive decreased the ban time and changed the pm message to explain why they have been removed and to come back later using winmx , for anyone trying this script its written for wcs so may need altering to work with other chat servers.
Title: Re: Client on enter
Post by: ]2aven (R.I.P.) on August 12, 2009, 05:29:38 pm
Nice script Reef. I won't need this but I wanted to say I liked how incorporated /gnotice into it. It's a WCS command that's rarely used. Very cool.   8)
Title: Re: Client on enter
Post by: Pri on August 12, 2009, 06:04:26 pm
If you want something a bit smaller and easier to edit in future try this instead. I hope you don't mind me editing your script as it was a good script but I think this would be easier for end users to edit to add/remove clients to block as-well as smaller code.

Code: [Select]
<config>

<OnEnter type="script">
<out type="sleep" extdata="10000"/>
<out type="push" extdata="CLIENTCHECK">1</out>
<out type="push" extdata="USERNAME">%NAME%</out>
<out type="push" extdata="USERRAWNAME">%RAWNAME%</out>
<out type="push" extdata="USERIP">%IP%</out>
<out type="push" extdata="USERHOSTNAME">%HOSTNAME%</out>
<out delay="10000">/hidecmd /stats %USERVAR[USERNAME]%</out>
</OnEnter>

<command mode="thread" type="script" condition="==" lvalue="%USERVAR[CLIENTCHECK]%" rvalue="1">
<in>Transfer Status: %PARAM%</in>
<out type="push" extdata="TRANSTATUS">%PARAM%</out>
</command>

<command mode="thread" type="script" condition="==" lvalue="%USERVAR[CLIENTCHECK]%" rvalue="1">
<in>Client: %PARAM%</in>
<out type="push" extdata="USERCLIENT">%PARAM%</out>
// Push 'TRANSTATUS' to 'USERCLIENT' if WPCC is detected inside 'TRANSTATUS' variable
<out type="push" extdata="USERCLIENT" condition="?" lvalue="$TRANSTATUS$" rvalue="WPCC">WPCC</out>
// Push 1 to CLIENT_CHECK if an Illegal Client is detected
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="Robo">1</out>
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="Rabbit">1</out>
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC">1</out>
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="RESERVED FOR MORE CLIENTS">1</out>
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="RESERVED FOR MORE CLIENTS">1</out>
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="RESERVED FOR MORE CLIENTS">1</out>
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="RESERVED FOR MORE CLIENTS">1</out>
// Illegal Client Check, Kick/ban and PM/announce if a 1 is present in CLIENT_CHECK, ignore else
<out condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">/hidecmd /gnotice @ #c9#User Name: #c10#$USERNAME$ #c9#Client: #c10#$USERCLIENT$</out>
<out delay="100" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">/hidecmd /gnotice @ #c9#Illegal Client Detected: #c10#$USERCLIENT$</out>
<out delay="100" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">/hidecmd /gnotice @ #c9#$USERNAME$ #c1#Banned For Illegal Client</out>
<out delay="100" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">/hidecmd /banip $USERIP$ 2880</out>
<out delay="100" type="pm" extdata="$USERRAWNAME$" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">$USERNAME$ Your Banned For An Illegal Client: $USERCLIENT$</out>
<out delay="5000" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">/hidecmd /privnotice $USERNAME$ #c1#You've Been Banned For An Illegal Client</out>
<out delay="5000" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">/hidecmd /kick $USERIP$</out>
<out delay="500" type="tooltip" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">ILLEGAL CLIENT DETECTED\n\n$USERNAME$ - $USERHOSTNAME$ - $USERIP$\n\n$TRANSTATUS$\n\n$USERCLIENT$</out>
<out type="goto" extdata="32" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1"></out>
// Pop user variables for clean run next time
<out type="pop" extdata="USERIP"/>
<out type="pop" extdata="USERCLIENT"/>
<out type="pop" extdata="CLIENTCHECK"/>
<out type="pop" extdata="USERNAME"/>
<out type="pop" extdata="USERRAWNAME"/>
<out type="pop" extdata="USERHOSTNAME"/>
<out type="pop" extdata="TRANSTATUS"/>
<out type="pop" extdata="CLIENT_CHECK"/>
</command>

</config>
Title: Re: Client on enter
Post by: F£¥è® on August 12, 2009, 09:57:34 pm
Excellent edit Pri,
Nice clean and precise.
Not sure why the "goto extdata = 32" line is included though,to me it seems unnecessary and makes no sense,unless I'm missing something.
Title: Re: Client on enter
Post by: birdman on August 12, 2009, 10:07:29 pm
Two nice scripts there from reef anf Pri :-) i wonder what other security type mettis scripts may be knocking around i know theres one for number of files shared. I like the popup from mettis on reefs script i never knew mettis could do that lol
Title: Re: Client on enter
Post by: reef on August 13, 2009, 06:32:57 am
@ birdman
As i mentioned earlier on in this thread... this script was originally a transfer status script
by Guru aka James. I just mod'd it up to do what u were lookin for.

@ Raven
Personally i use gnotice quite a bit... certain messages get sent to admins and others get sent
to agents and so on.

@ Pri
I dont mind at all, nice mod, and as u mentioned... easier for hosts to edit in the future.
An improvement i would say.
Title: Re: Client on enter
Post by: Pri on August 13, 2009, 08:17:50 am
Sorry I completely missed the Goto statement there Apprentice. It was in the original and I never noticed it. Totally erase that before using the script.

Here is one with that removed:

Code: [Select]
<config>

<OnEnter type="script">
<out type="sleep" extdata="10000"/>
<out type="push" extdata="CLIENTCHECK">1</out>
<out type="push" extdata="USERNAME">%NAME%</out>
<out type="push" extdata="USERRAWNAME">%RAWNAME%</out>
<out type="push" extdata="USERIP">%IP%</out>
<out type="push" extdata="USERHOSTNAME">%HOSTNAME%</out>
<out delay="10000">/hidecmd /stats %USERVAR[USERNAME]%</out>
</OnEnter>

<command mode="thread" type="script" condition="==" lvalue="%USERVAR[CLIENTCHECK]%" rvalue="1">
<in>Transfer Status: %PARAM%</in>
<out type="push" extdata="TRANSTATUS">%PARAM%</out>
</command>

<command mode="thread" type="script" condition="==" lvalue="%USERVAR[CLIENTCHECK]%" rvalue="1">
<in>Client: %PARAM%</in>
<out type="push" extdata="USERCLIENT">%PARAM%</out>
// Push 'TRANSTATUS' to 'USERCLIENT' if WPCC is detected inside 'TRANSTATUS' variable
<out type="push" extdata="USERCLIENT" condition="?" lvalue="$TRANSTATUS$" rvalue="WPCC">WPCC</out>
// Push 1 to CLIENT_CHECK if an Illegal Client is detected
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="Robo">1</out>
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="Rabbit">1</out>
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC">1</out>
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="RESERVED FOR MORE CLIENTS">1</out>
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="RESERVED FOR MORE CLIENTS">1</out>
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="RESERVED FOR MORE CLIENTS">1</out>
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="RESERVED FOR MORE CLIENTS">1</out>
// Illegal Client Check, Kick/ban and PM/announce if a 1 is present in CLIENT_CHECK, ignore else
<out condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">/hidecmd /gnotice @ #c9#User Name: #c10#$USERNAME$ #c9#Client: #c10#$USERCLIENT$</out>
<out delay="100" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">/hidecmd /gnotice @ #c9#Illegal Client Detected: #c10#$USERCLIENT$</out>
<out delay="100" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">/hidecmd /gnotice @ #c9#$USERNAME$ #c1#Banned For Illegal Client</out>
<out delay="100" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">/hidecmd /banip $USERIP$ 2880</out>
<out delay="100" type="pm" extdata="$USERRAWNAME$" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">$USERNAME$ Your Banned For An Illegal Client: $USERCLIENT$</out>
<out delay="5000" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">/hidecmd /privnotice $USERNAME$ #c1#You've Been Banned For An Illegal Client</out>
<out delay="5000" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">/hidecmd /kick $USERIP$</out>
<out delay="500" type="tooltip" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">ILLEGAL CLIENT DETECTED\n\n$USERNAME$ - $USERHOSTNAME$ - $USERIP$\n\n$TRANSTATUS$\n\n$USERCLIENT$</out>
// Pop user variables for clean run next time
<out type="pop" extdata="USERIP"/>
<out type="pop" extdata="USERCLIENT"/>
<out type="pop" extdata="CLIENTCHECK"/>
<out type="pop" extdata="USERNAME"/>
<out type="pop" extdata="USERRAWNAME"/>
<out type="pop" extdata="USERHOSTNAME"/>
<out type="pop" extdata="TRANSTATUS"/>
<out type="pop" extdata="CLIENT_CHECK"/>
</command>

</config>
Title: Re: Client on enter
Post by: F£¥è® on August 13, 2009, 11:08:06 am
Quote
birdman wrote,
 I like the popup from mettis on reefs script i never knew mettis could do that lol

 The tooltip is documented in the Metis.chm file, although it's not fully comprehensive if you have never used it then it's a good reference point to start.
Title: Re: Client on enter
Post by: birdman on August 13, 2009, 01:00:41 pm
That script works sweet to pri ;) what would a host change in the script if they was using FXS  as the scripts are for WCS ?
Title: Re: Client on enter
Post by: Pri on August 13, 2009, 03:24:20 pm
It has been a long long time since I used FXServ (last time I even looked at it was 2007) but if I remember correctly it does not have any type of /gnotice system (??) so I would suppose changing /gnotice @ to /opmsg and also removing all the /hidecmd's as FXServ does not support those. And I cannot remember the command for finding a client in FXServ if it even has that capability. Perhaps someone better versed in it could answer those questions.

If someone wanted to make this universal though I would suggest using the %SERVER% tag to detect which server is in use and change the first output (Currently /hidecmd /stats %USERVAR[USERNAME]%) to the command required for the specific server in use and also change the <in>Client: %PARAM%</in> for what is needed for each server.

That would make the script nice and small and completely universal as-long as each server supports the reporting of a users client. Sorry that I'm not familiar enough with FXServ.
Title: Re: Client on enter
Post by: F£¥è® on August 13, 2009, 07:09:19 pm
FXS reports entering clients with an admin message. so this should work fine.
Code: [Select]
<config>
<OnEnter type="script">
<out type="sleep" extdata="10000"/>
<out type="push" extdata="CLIENTCHECK">1</out>
<out type="push" extdata="USERNAME">%NAME%</out>
<out type="push" extdata="USERRAWNAME">%RAWNAME%</out>
<out type="push" extdata="USERIP">%IP%</out>
<out type="push" extdata="USERHOSTNAME">%HOSTNAME%</out>
</OnEnter>

<command mode="thread" type="script" condition="==" lvalue="%USERVAR[CLIENTCHECK]%" rvalue="1">
<in>Client: %PARAM%</in>
<out type="push" extdata="USERCLIENT">%PARAM%</out>
// Push 1 to CLIENT_CHECK if an Illegal Client is detected
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="Robo">1</out>
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="Rabbit">1</out>
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="WPCC">1</out>
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="RESERVED FOR MORE CLIENTS">1</out>
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="RESERVED FOR MORE CLIENTS">1</out>
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="RESERVED FOR MORE CLIENTS">1</out>
<out type="push" extdata="CLIENT_CHECK" condition="?" lvalue="$USERCLIENT$" rvalue="RESERVED FOR MORE CLIENTS">1</out>
// Illegal Client Check, Kick/ban and PM/announce if a 1 is present in CLIENT_CHECK, ignore else
<out condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">/Opmsg #c9#User Name: #c10#$USERNAME$ #c9#Client: #c10#$USERCLIENT$</out>
<out delay="100" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">/Opmsg #c9#Illegal Client Detected: #c10#$USERCLIENT$</out>
<out delay="100" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">/Opmsg #c9#$USERNAME$ #c1#Banned For Illegal Client</out>
<out delay="100" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">/banip $USERIP$ 2880</out>
<out delay="100" type="pm" extdata="$USERRAWNAME$" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">$USERNAME$ Your Banned For An Illegal Client: $USERCLIENT$</out>
<out delay="5000" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">/message $USERNAME$ #c1#You've Been Banned For An Illegal Client</out>
<out delay="5000" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">/kick $USERIP$</out>
<out delay="500" type="tooltip" condition="==" lvalue="$CLIENT_CHECK$" rvalue="1">ILLEGAL CLIENT DETECTED\n\n$USERNAME$ - $USERHOSTNAME$ - $USERIP$\n\n$TRANSTATUS$\n\n$USERCLIENT$</out>
// Pop user variables for clean run next time
<out type="pop" extdata="USERIP"/>
<out type="pop" extdata="USERCLIENT"/>
<out type="pop" extdata="CLIENTCHECK"/>
<out type="pop" extdata="USERNAME"/>
<out type="pop" extdata="USERRAWNAME"/>
<out type="pop" extdata="USERHOSTNAME"/>
<out type="pop" extdata="TRANSTATUS"/>
<out type="pop" extdata="CLIENT_CHECK"/>
</command>
</config>
Title: Re: Client on enter
Post by: reef on August 14, 2009, 04:22:05 am
Transfer Status (which also shows WPCC) is exclusive to WCS. In an FXS room, if a WPCC user un-checked "show client name and version" they would report as winmx 3.53 and go undetected from Metis.

Also i believe for FXS, Metis would still have to perform /level <user>
in the OnEnter. Performing the /level <user>
command outputs as:

Client name: "client name here"

Lastly command mode="thread"

might need changed to OnOpMessage mode="thread" ???

Its been awhile since i've used FXS so i could be wrong  on that
Title: Re: Client on enter
Post by: birdman on August 14, 2009, 08:19:15 am
I dont use FXS anymore so i cant test flyers script to see if it works maybe someone else can and report back.
Title: Re: Client on enter
Post by: Bluey_412 on October 15, 2009, 02:45:34 pm
i think that the very supporting of any such practice is counter-productive
people can have many and varied reasons for using a client, and many and varied reasons for having 0 files, like mebbe a newly formatted drive, and they are rebuilding, or a returning long-lost user...

we are supposed to be a community, FFS, not a "me against everyone else" brawl...

I personally have been kicked on enter from a movie room, when my only crime was to enter to search for a particular user...
Title: Re: Client on enter
Post by: Pri on October 15, 2009, 04:21:44 pm
Hosts have the right to run their rooms however they want. If users do not like the way they run things they can leave theres 900 other rooms on the listing. And sometimes the users in these rooms that ban 0 sharers and chat clients actually like those rules as it means leechers cant queue on them from the room.
Title: Re: Client on enter
Post by: wonderer on October 15, 2009, 11:56:54 pm
If hosts and their admins are not able to use the client information as it is meant to be, just information and are going to use it to decide to allow someone in the room or not, the next step will be a client that reports whatever a host wants to see. I don't think this is what the WinMx community should be after.
Title: Re: Client on enter
Post by: Pri on October 16, 2009, 12:59:02 am
Well fortunately you do not have the power to tell rooms what to do. We all have our own ideas about what is right and wrong and what should and should not be allowed on the network and that is why we are free to open our own chat rooms.
Title: Re: Client on enter
Post by: Pri on October 16, 2009, 01:07:11 am
Also just wanted to add, to use your logic we should not be using IP based bans in chat rooms because it makes people use IP Changes which reports false information to the rooms they visit thereby being detrimental to rooms.

To be honest how useful is the client reporter anyway? If your client supports the latest version of the chat protocol like WinMX 3.54b does then theres no need for your client to be reporting anything anyway so hosts that wish to use it in a personalised way should be free to do so without persecution.

And finally least we forget what WinMX is actually for sharing copyrighted works. It's difficult for us to get on a moral high-ground about the way we use the software when its main goal is to facilitate illegal file sharing.
Title: Re: Client on enter
Post by: Stevi on October 16, 2009, 02:31:25 am
Actually Pri, WinMX is designed for file sharing. Weather or not someone shares copyrighted material is up to them.

Back on topic.

If anyone is really concerned RoboMX has the ability to edit the client information to be able to report anything you want it to. So if anyone is going to get around the blocks, they will just use RoboMX and have it report as WinMX.

Now can we stop with this topic?
Title: Re: Client on enter
Post by: Pri on October 16, 2009, 02:47:03 am
Come on lets be honest 99.9% of people on the network are trading illegal content. To say otherwise would be a plain lie.

The only people not sharing illegal content are the ones using Chat Clients
Title: Re: Client on enter
Post by: reef on October 16, 2009, 02:58:22 am
Well fortunately you do not have the power to tell rooms what to do. We all have our own ideas about what is right and wrong and what should and should not be allowed on the network and that is why we are free to open our own chat rooms.

I agree with that 100% . Personally i don't choose to block any clients, but thats my choice. In the end its us the hosts who pay for our internet bill and the users in the rooms are guests on our computers. Blocking or banning is entirely up to the host and only the host, to run the room as they see fit. Theres all kinds of different ideas on running rooms, some are private (password protected) , some i've been in you have no voice until you PM an admin. There is no right or wrong way, it's how the host decides to run the room, and has every right to do so.

Now can we stop with this topic?

No offense Omega, but i don't see why it should be stopped. It's just a discussion about clients in chat rooms and different ideas from winmx hosts. Interesting to see other hosts ideas on matters.  ;)
Title: Re: Client on enter
Post by: wonderer on October 16, 2009, 03:33:18 am
So, I'm a hosting my for over 5 years and one and sometimes more rooms for good friends.
In my view WinMx is a social network where we can chat and to discuss all kinds of subjects. That might be why they are called chatrooms.  :-D
Next to that, we are able to share our files, copyrighted or not. It is up to the clients wether or not to share any files and the nature of the files. It is up to the hosts if they want to cooperate by allowing or refusing clients sharing certain files or lacking to share files.

I'm in no way trying to tell any host what to do or not to do, this is my view on the WinMx community, wether you like it or not. :)
Title: Re: Client on enter
Post by: Pri on October 16, 2009, 03:42:06 am
You are free to voice your opinion I'm not trying to stop you from doing that. I'm just saying that everyone has that right and theres no wrong or right way to run a room and I also do not believe that just because a handful of rooms choose to block people with chat clients that it will cause a bunch of clients to spring up that all report themselves as WinMX to skirt around that.
Title: Re: Client on enter
Post by: Stevi on October 16, 2009, 07:39:37 am
Ok. I am going to lock this topic. This was intended to get a script, and the script was produced.
Title: Re: Client on enter
Post by: Bluey_412 on October 16, 2009, 08:09:45 am
party Pooper...