Author Topic: Client on enter (Read 16053 times)

Pri · « **Reply #40 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>

F£¥è® · « **Reply #41 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.

~~birdman~~ · « **Reply #42 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

reef · « **Reply #43 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.

Pri · « **Reply #44 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>

F£¥è® · « **Reply #45 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.

~~birdman~~ · « **Reply #46 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 ?

Pri · « **Reply #47 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.

F£¥è® · « **Reply #48 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>

reef · « **Reply #49 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

~~birdman~~ · « **Reply #50 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.

Bluey_412 · « **Reply #51 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...

Pri · « **Reply #52 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.

wonderer · « **Reply #53 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.

Pri · « **Reply #54 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.

Pri · « **Reply #55 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.

Stevi · « **Reply #56 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?

Pri · « **Reply #57 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

reef · « **Reply #58 on:** October 16, 2009, 02:58:22 am »

Quote from: 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.

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.

Quote from: Omega on October 16, 2009, 02:31:25 am

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.

wonderer · « **Reply #59 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.

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.