Page 2 of 25
Re: GM detection and banning chance reduction
Posted: Sat May 28, 2011 9:46 am
by hackzor
still EventMonitorStart a nil value. . . hmmmm
Re: GM detection and banning chance reduction
Posted: Sat May 28, 2011 11:02 am
by lisa
K well eventmonitorstart is a functgion in the function.lua for the bot.
I'd say you deff have an old version or some files arn't up to date.
Please update micromacro, rom and also use revert on the folders using tortoiseSVN.
This is assuming you are on a server that in 3.10 +
Re: GM detection and banning chance reduction
Posted: Sat May 28, 2011 12:23 pm
by hackzor
yea SVN didnt want to update the functions so i deleted it. . .now i got eventstartmonitor but if i start a WP it says GM monitoring started, and thats it. . . no egg farming, no moving, just GM monitoring started lol
Re: GM detection and banning chance reduction
Posted: Sat May 28, 2011 11:03 pm
by lisa
Made some big changes.
Function now gives the choice of pausing bot for a period of time instead of just reply and then logout.
Also added in some ways to deal with agro while trying to pause.
Added in the ability for self testing without actually needing a GM to whisper you lol
Please reread the entire first post to understand how it works now.
Re: GM detection and banning chance reduction
Posted: Sun May 29, 2011 3:39 am
by rock5
lisa wrote:PAUSEONGM...If a GM has messaged in the last 1 minute before pause finishes then it will pause again.
I would have just reset the timer whenever the GM whispered you. That way when the 5 minutes if finally over, it would have been 5 minutes since the last GM message.
Re: GM detection and banning chance reduction
Posted: Sun May 29, 2011 5:23 am
by lisa
GM's seem to be leaving me alone tonight lol
They have been on my back last few days and now I am running a few clients in millers for half the day, nothing lol
Hopefully I get atleast 1 whisper soon just to confirm the GM identification works properly, it should be fine though
Re: GM detection and banning chance reduction
Posted: Sun May 29, 2011 7:33 am
by lisa
rock5 wrote:lisa wrote:PAUSEONGM...If a GM has messaged in the last 1 minute before pause finishes then it will pause again.
I would have just reset the timer whenever the GM whispered you. That way when the 5 minutes if finally over, it would have been 5 minutes since the last GM message.
Tricky part with this is when timer is reset it has a moment where bot starts to continue and then stops again. So for that moment the character moves, so reseting it every time the bot is whispered will result in the character moving each time.
I believe 5 minutes as minimum pause time is the way to go, I will personally probably do 10-15 minutes.
Worst case scenario your bot stands still for 30 minutes and doesn't get banned, I can live with the bot being still for 30 minutes lol
Re: GM detection and banning chance reduction
Posted: Sun May 29, 2011 9:30 am
by rock5
If your in a loop and don't leave it, then reseting the timer shouldn't make you move.
Re: GM detection and banning chance reduction
Posted: Sun May 29, 2011 6:43 pm
by lisa
I do agree reseting the timer when whispered by a GM would be logical
I think I am just over thinking it, tried a few things but it's just not working the way I want and seems to be getting more and more complex as I think on it lol
RECALL isn't working as intended atm, working on a solution.
Code: Select all
repeat
sendMacro("UseSkill(1,2);");
yrest(1000)
until memoryReadBytePtr(getProc(), addresses.loadingScreenPtr, addresses.loadingScreen_offset) == 1
waitForLoadingScreen()
messagereply()
yrest(1000)
RoMScript("Logout();");
error("Logging out because GM whispered.")
For some reason it isn't detecting that the load screen has come up, keeps just using recall non stop. If I can't get that to work I might just add in a distance detection.
Re: GM detection and banning chance reduction
Posted: Sun May 29, 2011 8:27 pm
by rock5
You shouldn't need the repeat loop as, ever since that fix I did to RoMScript, it should pretty much 100% execute the RoMScript andsendMacro commands.
ALso you probably need to make sure recall works because it might be on cooldown. You could probably use the second argument to waitforloadingscreen to set a max time then deal with the consequences if it didn't teleport.
Re: GM detection and banning chance reduction
Posted: Sun May 29, 2011 8:36 pm
by lisa
yeah I just added a check for cooldown on recall. Reason I do a loop is because damage from a mob interupts the skill cast. So it may take 3+ tries before it actually finishes the skill cast.
Looks like this atm
Code: Select all
if settings.profile.options.RECALL == true then
local cooldown, remaining = sendMacro("GetSkillCooldown(1,2);")
repeat
if remaining == 0 then
sendMacro("UseSkill(1,2);");
else
messagereply()
yrest(1000)
RoMScript("Logout();");
error("Recall was on cooldown, so logged out in mob area.")
end
if memoryReadBytePtr(getProc(), addresses.loadingScreenPtr, addresses.loadingScreen_offset) == 1 then _wait = true end
until memoryReadBytePtr(getProc(), addresses.loadingScreenPtr, addresses.loadingScreen_offset) == 1 or remaining > 1 or keyPressedLocal(settings.hotkeys.START_BOT.key)
if _wait == true then waitForLoadingScreen() end
messagereply()
yrest(1000)
RoMScript("Logout();");
error("Logging out because GM whispered, used recall.")
else
messagereply()
yrest(1000)
RoMScript("Logout();");
error("Logging out because GM whispered, used recall.")
end
I decided I was overthinking things again with trying to get bot to kill mobs and then pause or logout. With this code if in combat and if it has RECALL = true in profile it will try to recall-reply-logout otherwise it will reply-logout.
Re: GM detection and banning chance reduction
Posted: Tue May 31, 2011 1:19 am
by do002
Truly good work lisa. I'm glad that u have finally finished this awesome project
Btw I was whispered by a very strange GM, possibly from a different server or something cause I never saw that GM before.(just saying/updating you guyz with what I know that's all)
Re: GM detection and banning chance reduction
Posted: Tue May 31, 2011 2:41 am
by lisa
I bet you were in millers at the time too lol
Yes I have noticed this and I have a few theories but nothing concrete at the moment.
Did the function work for you when they whispered, I haven't received 1 whisper since I last updated this post lol
Re: GM detection and banning chance reduction
Posted: Tue May 31, 2011 8:41 am
by OneofMany
This is great!
Will implement this in the KS script for sure!
Re: GM detection and banning chance reduction
Posted: Tue May 31, 2011 8:47 am
by OneofMany
But, i never ever seen a GM in RoM for as long as i play. How are they being detected? (can answer in PM ofcourse)
Re: GM detection and banning chance reduction
Posted: Tue May 31, 2011 9:06 am
by lisa
OneofMany wrote:This is great!
Will implement this in the KS script for sure!
I wouldn't add it to a public waypoint file, people should have the choice as to whether they want it loaded or not, if people put in in their profile and it is also in a WP then it could cause complications.
I call the function in my profiles onload section, you only want it called once.
Re: GM detection and banning chance reduction
Posted: Wed Jun 01, 2011 8:05 pm
by do002
I have tried it but couldnt get it worked properly. When I loaded macro it said "failed to load the alarm" and when it loaded my profile the macro said there were unknown tags in the profile.
Btw i got the catch cavy function worked
Re: GM detection and banning chance reduction
Posted: Wed Jun 01, 2011 9:21 pm
by lisa
do002 wrote: and when it loaded my profile the macro said there were unknown tags in the profile.
Can you post your profile in code tags please.
I'll look into "failed to load the alarm" , I've never seen that before.
Re: GM detection and banning chance reduction
Posted: Sat Jun 04, 2011 12:52 am
by lisa
error in the code at line 117
V 1.4 has
Code: Select all
if settings.profile.options.PAUSEONGM ~= 0 or settings.profile.options.PAUSEONGM ~= nil then
but it should be this, can either d/l 1.5 or just edit the line. that is the only change in V 1.5
Code: Select all
if settings.profile.options.PAUSEONGM ~= 0 and settings.profile.options.PAUSEONGM ~= nil then
Re: GM detection and banning chance reduction
Posted: Sat Jun 04, 2011 11:25 pm
by kanta
rock5 wrote:I don't see the difficulty.
Code: Select all
ResponseTable = {
[1] = "Sorry, got to go",
[2] = "I'm just logging off, sorry.",
[3] = "My favourite show is about to start. See ya.",
}
print(ResponseTable[math.random(#ResponseTable)])
I apologize that this is off topic, but I'd really like to know something.
Would this sort of table be able to be modified to randomize farming paths? Like linking waypoint tags or loading waypoint files? Such as when I break party to reset an instance, I could have 3 different paths I could take to the merchant NPC reducing "botlike" behavior.