logout bots to much last time

[booting1]

At last time, very much go to character start menu, so that i must say enter world.
Last in the micromacro window:

Code: Select all

.....
Moving to wayoint #17, (12175, 10418)
Clearing target
The game has been disconnected.
08/24/12 06:38:43 Auto-loggin out
Erfolgreich: The Prozess with PID 5020 was been closed ( i hope i have correcty change to english, this is in german in my micromacro windows)
Runes of magic process successfully closed
did not find any cashed game clients.
06:38am - exeting: auto-logout

why so much logouts?

[lisa]

My guess is this part of your profile is set to log out after a period of time.

Code: Select all

		<option name="LOGOUT_TIME" 			value="0" />			<!-- in minutes, 0 = timer disabled -->

There are no errors in what you posted, it is just saying it is logging out.

[rock5]

There is a bit of repetition in those messages though.
"Auto-loggin out" and "exeting: auto-logout"
"The Prozess with PID 5020 was been closed" and "Runes of magic process successfully closed"

booting1, it's hard to match the error messages when you mispell words. Please learn to copy and paste.
http://www.solarstrike.net/phpBB3/viewt ... 878#p30878

[lisa]

Also you don't need to translate it for us, copy paste what is on Micromacro as it is.
If this is happening regularly you can start the bot with "debug" and it will also print the corresponding number for the message, makes it easier for us to identify the message

example

Code: Select all

rom/bot.lua path:partyhealer debug

[langelot]

i've got exactly same thing and it happens more and more since a month

Code: Select all

Stopping waypoint: Target acquired.
Engaging enemy [Ancient Demon Bloom] in combat.
Use MACRO: MAGE_FIREBALL       =>   Ancient Demon Bloom (5201/5201)
Use MACRO: MAGE_FLAME          =>   * Failed to cast *
Use MACRO: MAGE_FIREBALL       =>   Ancient Demon Bloom (5201/5201)
Use MACRO: MAGE_FLAME          =>   * Failed to cast *
Use MACRO: MAGE_FIREBALL       =>   Ancient Demon Bloom (5201/5201)
Use MACRO: MAGE_FLAME          =>   * Failed to cast *
Use MACRO: MAGE_FIREBALL       =>   Ancient Demon Bloom (5201/5201)
Taking too long to damage target, breaking sequence...
Clearing target.
Fight finished. Killed 50 Ancient Demon Bloom. (fight #50 / runtime 22439152 min
utes)
Clearing target.
The userfunction 'lootBodies()' is obsolete and might interfere with the bots 'l
ootAll()' function. Please delete the 'addon_lootbodies.lua' file from the 'user
functions' folder.
Moving to waypoint #20, (6185, 12648)
Moving to waypoint #21, (6572, 12545)
Moving to waypoint #22, (6695, 12476)
Moving to waypoint #23, (6734, 12294)
Moving to waypoint #15, (6612, 12164)
We changed the option 'MAX_TARGET_DIST' from '100' to '100'.
Moving to waypoint #16, (6582, 11976)
Stopping waypoint: Target acquired.
Engaging enemy [Ancient Demon Bloom] in combat.
Fight finished. Killed 51 Ancient Demon Bloom. (fight #51 / runtime 22439153 min
utes)
Clearing target.
Moving to waypoint #16, (6582, 11976)
Clearing target.
The game has been disconnected.
08/30/12 19:53:25  Auto-logging out.
Opération réussie : le processus avec PID 4112 a été terminé.
Runes of Magic process successfully closed.
Did not find any crashed game clients.
7:53pm - Exiting: Auto-logout


Please enter the script name to run.
Type in 'exit' (without quotes) to exit.
Script>

[Jandrana]

i've got exactly same thing and it happens more and more since a month

For me, it happens sind the last patch. I have chained "malatainas survival", "malatinas corse of terror", "a script that walks chars to entry of ancient treasures", "ancient treasures" ....

Currently if happens very often, that the game terminates/disconnects at the end of "malatinas corse of terror" (usually when I'm not watching).

[silinky]

the game itself randomly disconnects my internet connection sometimes just for 1 second. by the time i reconnect, the game logs out. don't know why, but it only happens when i run the game. i think the geniuses from RW made a funny again.

i have an idea to counter this but since i am a nub, i don't know the solution:

when the bot detects a disconnection, it should rest for 1 mminute, then try to log the char in again. i have autologin, so i have all my char's data in the login fields, it only should press the login, and then "enter game" button, then update player position and resume botting. can this be done?

[Jandrana]

I don't know if this is related to the disconnects. If wrote a few scripts to harvest ore, herb, wood. To keep the yield higher the script monitors the harvested items for each loop and prints a short log at the end of each loop. The script itself only uses item IDs, but to print the log it uses GetIdName.

During the last weekend, it happened that the log being printed contained a lot of funny characters. It looks like the function GetIdName returned a string with "random bytes from memory". It looks like something is broken here. Maybe the memory of the client got corrupted. Hard to say, if this a side effect from running the bot or this is a problem of the client itself.

If memory gets corrupted you easily run into situations that something goes wrong - maybe the server disconnects the client if he detects, that "wrong data" is being transmitted.

[Jandrana]

I think we should keep a look at this problem. It annoys me.

As I wrote above I have the situation, that the bot disconnects with a very high probability (> 80%) always in the same situation.
I have a log of the MM output in this situation. Malatina's COT is finished, the script going to AT is being loaded. The numbers are printouts in my "onLoad", because I suspected the problem happening there. But "onLoad" completes. Then the bot rebuffs itself and disconnects. When I start the script manually, the bot NEVER disconnects in this script.

We successfully target NPC Malatina and try to open the dialog window.
Use MACRO: Executing RoMScript "ChoiceOption(1);".
Use MACRO: Executing RoMScript "ChoiceOption(1);".
Succeeded with 11:00 remaining.
Loaded waypoint path goto_at.xml
No return path with default naming goto_at_return.xml found.
We use the normal waypoint path goto_at.xml now.
1
2
3
GM detection started
4
5
Clearing target.
Moving to waypoint #1, (4867, -1895)
Use MACRO: PRIEST_AMPLIFIED_ATT=> <UNKNOWN> (1000/1000)
Use MACRO: PRIEST_MAGIC_BARRIER=> <UNKNOWN> (1000/1000)
Use MACRO: PRIEST_GRACE_OF_LIFE=> <UNKNOWN> (1000/1000)
Use MACRO: PRIEST_EMBRACE_OF_TH=> <UNKNOWN> (1000/1000)
Use MACRO: PRIEST_AMPLIFIED_ATT=> <UNKNOWN> (1000/1000)
Use MACRO: PRIEST_MAGIC_BARRIER=> <UNKNOWN> (1000/1000)
Player address changed: 0x478A6E00
Ranged skill found: SCOUT_VAMPIRE_ARROWS
Use MACRO: PRIEST_GRACE_OF_LIFE=> <UNKNOWN> (1000/1000)
Clearing target.
The game has been disconnected.
09/09/12 10:15:12 Auto-logging out.
SUCCESS: The process with PID 3916 has been terminated.
Runes of Magic process successfully closed.
Did not find any crashed game clients.
10:15am - Exiting: Auto-logout


Please enter the script name to run.
Type in 'exit' (without quotes) to exit.
Script>

I would like to add more debug output, to narrow down the piece of code, where the disconnect happens. Can anyone point me to the right direction?

B.t.w - the game crashed a few days ago - the bot did NOT detect a crashed game client.

[rock5]

From your output I'd guess you edited cot_tele to teleport out of the game. You probably made a mistake. Maybe you forgot to add a "waitForLoadingScreen()".

[Jandrana]

Rock, thanks a lot the hint. Yes, you are right "waitForLoadingScreen" is missing. But I did this at least 8 weeks ago. Interestingly this didn't cause any troubles until the last patch. Will fix it and hopefully the disconnects with this script are gone then.

[rock5]

Interestingly this didn't cause any troubles until the last patch.

Probably because the bot is better at detecting when not in the game. So it now detects that it is no longer in the game so it assumes you have been disconnected, which is the way it's supposed to work. You were just lucky, before, that you didn't have any issues when you tried to execute code when the loading screen was up.