Page 20 of 25
Re: GM detection and banning chance reduction
Posted: Mon Dec 02, 2013 9:15 pm
by lisa
yeah I originally wrote this when I was pretty new to LUA, a lot has changed in my experience since then
Glad someone is picking up the project and updating it, when you are happy with your code I will add it to the first post.
Just one thing
Code: Select all
if string.find(msg,"GM") or string.find(msg,gmMinLevel) or string.find(msg,"Moderator") or string.find(msg,testcharname) or string.find(msg,"Game Master") or string.find(msg,"Gamemaster")then
Since this list is getting long I would be tempted to make a user input section at the top in the form of a table.
so replace that line with
Code: Select all
local detected = false
for k,v in pairs(gmTagList) do
if string.find(msg,v) then
detetcted = true
break
end
end
if detetced = true then
and up the top of file do
Code: Select all
local gmTagList = {gmMinLevel,testcharname,"GM","Moderator","Game Master","Gamemaster"}
Something like that anyway, just an idea =)
Also that will only look for the stated lvl, "85" and nothing more, so if they are lvl 100 it won't be detected in that search as it is purely text search.
Re: GM detection and banning chance reduction
Posted: Mon Dec 02, 2013 10:11 pm
by BlubBlab
I have thought that already.
I'm not sure maybe I make one function for both tables.
"85" is the level for the GM's on the official server at the moment, because it can easily differ so I moved it to the config part.
I took the job because it was needed their was a few guys who got caught in the past weeks, so I thought something must be done.
Re: GM detection and banning chance reduction
Posted: Fri Dec 06, 2013 5:47 pm
by BlubBlab
So this finally works (tested)
my config:
Code: Select all
<option name="GMDETECT" value="true" /> -- enables the GM detection userfunction
<option name="GMnearbylogout" value="true" /> -- If a GM is close to the character it will log out.
<option name="GMonServer" value="pause" /> -- possible: logout/pause/relog
<option name="PAUSEONGM" value="0" /> -- Pauses when GM whispers for value in seconds. ie 300 = 5 minutes
<option name="RECALL" value="true" /> -- if in combat while pausing it will use recall and whisper/logout
<option name="playerDETECT" value="true" /> -- enables the player detection userfunction
<!--
<option name="GMPAUSETIME" value="60" /> -- Pauses when GM is on server. ie 300 = 5 minutes
<option name="GMRELOGETIME" value="60" /> -- RELOG time when GM is on server. ie 300 = 5 minutes
-->
For the rest take a look in the script
EDIT I changed the standard setting to:
Because it curse so much trouble doing that automatically
Re: GM detection and banning chance reduction
Posted: Sat Dec 07, 2013 10:19 am
by spyfromsiochain
Well I get an error after the last version of gmdetect v. 7.6
looks like its when it asks the names of the gms (suppose its a loop from time to time) when that appends I get the error ingame: Search failed, target does not exist or is offline
the bot stops the normal behavior and starts going forwards none stop, till it checks all the names in list, after that is breaks and retrieves the last waypoint position.
I am doing anything wrong in the configuration of the profile?:
Code: Select all
<!-- GM detection options -->
<option name="GMDETECT" value="true" /> -- enables the GM detection userfunction
<option name="GMnearbylogout" value="true" /> -- If a GM is close to the character it will log out.
<option name="GMonServer" value="logout" /> -- possible: logout/pause/relog
<option name="PAUSEONGM" value="0" /> -- Pauses when GM whispers for value in seconds. ie 300 = 5 minutes
<option name="RECALL" value="true" /> -- if in combat while pausing it will use recall and whisper/logout
<option name="playerDETECT" value="true" /> -- enables the player detection userfunction
<!-- <option name="GMPAUSETIME" value="60" /> --> -- Pauses when GM is on server. ie 300 = 5 minutes
<!-- <option name="GMRELOGETIME" value="60" /> --> -- RELOG time when GM is on server. ie 300 = 5 minutes
Re: GM detection and banning chance reduction
Posted: Sat Dec 07, 2013 10:55 am
by BlubBlab
The error is normal because the script ask for each GM if he/she is online, when the script found one the bot should stop moving
If the List is too long and the bot get confused about it (I tested the server search from a still stand ), you can deactivated it with:
Code: Select all
--On which Level search for GM's in the List?' "memory","server","" in last case it is deactivated
local gmSearchMethode = "memory"
AHH okay you must delete the "local" from the script in local function searchGMList() and then in a Waypoint you call it:
Mom I will reupload it without the local
EDIT:I changed the pause between AskPlayer from huge 800 ms to 50 ms that should make it easier to use long list.
EDIT2: I delete
Code: Select all
while(player.Batteling)do
yrest(100)
end
The idea behind the code was that the bot continue fighting if bot/char is in battle and afterwards the bot should do what should be done
Re: GM detection and banning chance reduction
Posted: Sat Dec 07, 2013 2:18 pm
by Danni
Just tried it ...

the edit one.
I only added more names onto the list.
After some testing, a GM was on the Server.
MM printed something like: "Player is going to sleep for
something sec. Press Del to continue.
BUT the script of mine still went on, it didn't "really" pause.
Secondly,... "sleeping" (a "break") is fine, but could you make it without Del? Or somewhere , where each user can choose it on their own?

Re: GM detection and banning chance reduction
Posted: Sat Dec 07, 2013 3:42 pm
by BlubBlab
The Problem is to "pause" is that GM Detection runs in another coroutine, It could take some time to stop.
Hm I could add a custom sleep function ....DONE I will reupload again.
The "DEL" button is part of the script, the pause time can be customized.
From experience I can say it is better to call the function in a waypoint because while the bot search it can't react to something else
Re: GM detection and banning chance reduction
Posted: Sat Dec 07, 2013 4:40 pm
by Danni
From experience I can say it is better to call the function in a waypoint because while the bot search it can't react to something else
Just a little question...
And what would be the function?
It probably has to be in Load, isn't it?

Re: GM detection and banning chance reduction
Posted: Sat Dec 07, 2013 6:11 pm
by BlubBlab
That would be:
I can put where you want but I would recommend it to do it in a WP in you WPfile if you run multiply times through.
Re: GM detection and banning chance reduction
Posted: Tue Dec 10, 2013 11:04 am
by Danni
Found a little problem:
I get this msg in MM:
GM detected! Name: Holydeer, Class IDs: 5/6
Alarm has been sounded
The game client did not crash.
11:56pm - ...ROM/scripts/rom/userfunctions/userfunction_gmmonitor.lua:372: Logging out because GM detected.
After checking this person Information via MACRO , I realize it is player, who is standing next to me. This Char is not a GM. Tried doing the WP 3 times, every time, MM log me out, because the char stand next to me. Does "Class IDs: 5/6" means GM?
Re: GM detection and banning chance reduction
Posted: Tue Dec 10, 2013 2:49 pm
by BlubBlab
The ID is 0
Alternative the script search pattern in here:
Code: Select all
local gmPattern = {gmMinLevel,testcharname,"GM","Moderator","Game Master","Gamemaster"}
or if the char has a name like in local gmNameList = {....}
Was the max level raised today?
Re: GM detection and banning chance reduction
Posted: Tue Dec 10, 2013 6:17 pm
by Danni
I see.
The patch this time did not raise the max level cap.
But Rom did integrated already some lvl 85 items, like world boss and Phirius Shell EQ.
So my guess is something is wrong. Because:
The ID is 0

It isn't
script search pattern

no such words are inside
char has a name like in local gmNameList = {....}

nope it is not defined here either
Might it be that, this happened because I was running 3 clients and 3 MM, so one MM was not able to manage this workload?

Re: GM detection and banning chance reduction
Posted: Tue Dec 10, 2013 10:26 pm
by rock5
How about the characters level? The current gmmonitor, I believe, has a cap of 100, more than 100 and it will think it's a GM. That should be enough but if you have an older version it might have a lower cap.
Re: GM detection and banning chance reduction
Posted: Tue Dec 10, 2013 10:48 pm
by rock5
I see BlubBlabs version has a cap of 85. If you are playing on a server with a higher cap such as rom4u then you'll have to raise it.
Re: GM detection and banning chance reduction
Posted: Tue Dec 10, 2013 11:19 pm
by Danni
nope level cap for the characters is still at 82. And the char "Holydeer" is only 82.
just to buy stuff like world boss items or phirius shell items for lvl 85 is strangly already avialable
... seems like ROM did a mistake at the patching, but since when does ROM update a clean working patch

Re: GM detection and banning chance reduction
Posted: Wed Dec 11, 2013 11:10 pm
by Danni
Today I got two msg. which shouldn't appear:
GM detected! Name: Andrian, Class IDs: 3/6
Alarm has been sounded
The game client did not crash.
11:56pm - ...ROM/scripts/rom/userfunctions/userfunction_gmmonitor.lua:372: Logging out because GM detected.
I know that player personal , so he can't be a GM.
GM detected! Name: Sharika, Class IDs: 1/7
Alarm has been sounded
The game client did not crash.
11:56pm - ...ROM/scripts/rom/userfunctions/userfunction_gmmonitor.lua:372: Logging out because GM detected.
With this Char I am not sure, but I have a question:

Are you sure that the ID have to be "0"?
Because when writing a function to switch classes "1" is a GM while the classes starts at "2" I think. But I am not 100% sure.
Anyway for the other 2 cases "Holydeer" and "Adrian" , the msg should have not come. So I guess somewhere might be a problem.

Re: GM detection and banning chance reduction
Posted: Thu Dec 12, 2013 1:27 am
by rock5
Danni wrote:
Are you sure that the ID have to be "0"?

Because when writing a function to switch classes "1" is a GM while the classes starts at "2" I think. But I am not 100% sure.
Yes, when changing class you use 2 for warrior but the userfunction is checking a pawns class. pawn classes start at 1 for warrior so it would be 0 for GM.
Re: GM detection and banning chance reduction
Posted: Thu Dec 12, 2013 2:27 am
by lisa
I'll d/l V 7.7 and have a look, it is no doubt something simple that was over looked by BlubBlab
--=== Added ===--
Had a bit of a browse and the code itself looks fine.
2 things.
What is the lvl of the other player that is detected as a GM?
What does your list of names look like?
This is the default list.
Code: Select all
local gmNameList = {"Rhakara","Tohros","Saitomentor","Kiovar","Rakymos","Galorian","Inyrion","Riujnara","Lulyane","Akasha","Vayus","Tathros","Ciarog","Aranrod","GMNohdrael","GmNohdrael","Nohdrael","Kiareko","Adelynne","Rednaltor"};
Re: GM detection and banning chance reduction
Posted: Thu Dec 12, 2013 2:54 am
by lisa
Give this a try, it will do a full pawn print of the "GM", might give us a better idea as to what is going on.
No other changes as such.
Re: GM detection and banning chance reduction
Posted: Sat Dec 28, 2013 2:57 am
by Danni
@Lisa:
Sry for the delay reply, I was preparing the christmas celebration
My Search List look the same.
For the lvl of the Characters, all were lvl 82, which is the current lvl cap.
I now using your new file and will try it out. If the same problem still exist, I will write the result
