WhereIsMyMind
Member
- Joined
- Oct 12, 2013
- Messages
- 848
- Reaction score
- 5
Dear Dev,
UPDATE: I could login moments ago, I returned the leveling gear to a mule. I will abandon this account.
UPDATE2: Could it be cause this account was demanding a "UNLOCK CODE:"? My bot accounts get this because they are being logged on from different locations (protecting against an IP ban)
Found the bot like that after ~4 hours. Logs stopped after 2 hours. I presume this will be an IP ban but I am prepared for that (will update when known).
I SUSPECT it is because I left the setting on the 'Chicken' tab 'Login after Log out'. But Chicken was not selected... thus I thought this would not matter.
Perhaps have a safety there? x number of random time attempts in x number of minutes? (ah, I see there is, below, but I suspect it is buggy)
Analysis of log:
Problem occurs at 2013-10-24 20:39:18,832 'Stopping the bot. Reason: Could not log back into the game'
This was ~15 minutes after starting the bot after I had monitored it for 45 minutes on mudflats. I had not monitored it in the act 1 'prison' way point map where I left it running.
The above 'Stopping the bot. Reason: Could not log back into the game.' goes on for 80 minutes and then, below, '2013-10-24 23:52:50,060 [1] DEBUG BotMain (null) - Stopping the bot. Reason: UI Button Pressed'
I did not press the button. Can the log entry be changed for this operation? Say.. 'EB has stopped the bot by forcing a UI Button Press'?
Interesting, 'your settings are asking us not to' but it has been trying to login. So.. it looks like the required operation, stopping of the bot, did not trigger after 3 attepts.. so the bot continued to attempt the 3 logon cycle. And then when it did trigger, or was registered in the logs, 80 minutes later, it still did not stop.
So I found the bot still trying to login 4 hours later with:
"Abnormal operations you have tried to long on too many logins in a short duration' popup appearing"
which stopped when I stopped the bot. But logs had not been updating for ~2 hours.
Otherwise, bot was working awesome.
WIMM
UPDATE: I could login moments ago, I returned the leveling gear to a mule. I will abandon this account.
UPDATE2: Could it be cause this account was demanding a "UNLOCK CODE:"? My bot accounts get this because they are being logged on from different locations (protecting against an IP ban)
Found the bot like that after ~4 hours. Logs stopped after 2 hours. I presume this will be an IP ban but I am prepared for that (will update when known).
I SUSPECT it is because I left the setting on the 'Chicken' tab 'Login after Log out'. But Chicken was not selected... thus I thought this would not matter.
Perhaps have a safety there? x number of random time attempts in x number of minutes? (ah, I see there is, below, but I suspect it is buggy)
Analysis of log:
Problem occurs at 2013-10-24 20:39:18,832 'Stopping the bot. Reason: Could not log back into the game'
This was ~15 minutes after starting the bot after I had monitored it for 45 minutes on mudflats. I had not monitored it in the act 1 'prison' way point map where I left it running.
Code:
2013-10-24 20:39:03,116 [Main Bot Thread] DEBUG SpellManager (null) - Casting Freezing Pulse on Brittle Poacher
2013-10-24 20:39:03,182 [Main Bot Thread] DEBUG SpellManager (null) - Casting Freezing Pulse on Brittle Poacher
2013-10-24 20:39:03,249 [Main Bot Thread] DEBUG SpellManager (null) - Casting Freezing Pulse on Brittle Poacher
[B]2013-10-24 20:39:18,832[/B] [Main Bot Thread] DEBUG BotMain (null) - Stopping the bot. Reason: Could not log back into the game. Attempted 3 times, but failed. Please check for any game-related errors!
2013-10-24 20:39:18,832 [Main Bot Thread] DEBUG TreeHooks (null) - Removed hook [BotBehavior] 9db7d181-3107-42b5-87a7-617a7b793c7e
2013-10-24 20:39:18,833 [Main Bot Thread] DEBUG BotMain (null) - Removing memory patches.
2013-10-24 20:39:18,836 [Main Bot Thread] DEBUG BotMain (null) - Applying required memory patches.The above 'Stopping the bot. Reason: Could not log back into the game.' goes on for 80 minutes and then, below, '2013-10-24 23:52:50,060 [1] DEBUG BotMain (null) - Stopping the bot. Reason: UI Button Pressed'
I did not press the button. Can the log entry be changed for this operation? Say.. 'EB has stopped the bot by forcing a UI Button Press'?
Code:
2013-10-24 23:53:07,420 [Main Bot Thread] 2013-10-24 23:52:37,055 [Main Bot Thread] DEBUG BotMain (null) - Applying required memory patches.
2013-10-24 23:52:37,054 [Main Bot Thread] DEBUG BotMain (null) - Removing memory patches.
[B]2013-10-24 23:52:50,060 [1] DEBUG BotMain (null) - Stopping the bot. Reason: UI Button Pressed[/B]
2013-10-24 23:52:50,092 [Main Bot Thread] DEBUG TreeHooks (null) - Removed hook [BotBehavior] 4b1aa9e1-8c1a-44b7-8d77-91557e039bd8
2013-10-24 23:52:50,092 [Main Bot Thread] DEBUG BotMain (null) - Removing memory patches.
2013-10-24 23:52:50,095 [Main Bot Thread] DEBUG BotMain (null) - Applying required memory patches.
2013-10-24 23:52:50,096 [Main Bot Thread] DEBUG TreeHooks (null) - Added new hook [BotBehavior] 04ec47c0-8b94-4c52-b44d-0aca598a782e
2013-10-24 23:53:07,417 [Main Bot Thread] DEBUG BotMain (null) - Stopping the bot. Reason: Could not log back into the game. Attempted 3 times, but failed. Please check for any game-related errors!
2013-10-24 23:53:07,418 [Main Bot Thread] DEBUG TreeHooks (null) - Removed hook [BotBehavior] 04ec47c0-8b94-4c52-b44d-0aca598a782e
2013-10-24 23:53:07,420 [Main Bot Thread] DEBUG BotMain (null) - Applying required memory patches.
2013-10-24 23:53:07,421 [Main Bot Thread] DEBUG TreeHooks (null) - Added new hook [BotBehavior] dd44f492-6828-4e04-abf2-747038e4bb52
2013-10-24 23:53:07,418 [Main Bot Thread] DEBUG BotMain (null) - Removing memory patches.
2013-10-24 23:53:22,661 [Main Bot Thread] DEBUG BotMain (null) - Stopping the bot. Reason: Could not log back into the game. Attempted 3 times, but failed. Please check for any game-related errors!
2013-10-24 23:53:22,662 [Main Bot Thread] DEBUG BotMain (null) - Removing memory patches.
2013-10-24 23:53:22,665 [Main Bot Thread] DEBUG TreeHooks (null) - Added new hook [BotBehavior] d2c21c65-057c-4aa0-b555-a3c1c8641df9
2013-10-24 23:53:22,661 [Main Bot Thread] DEBUG TreeHooks (null) - Removed hook [BotBehavior] dd44f492-6828-4e04-abf2-747038e4bb52
2013-10-24 23:53:22,664 [Main Bot Thread] DEBUG BotMain (null) - Applying required memory patches.
2013-10-24 23:53:22,727 [Main Bot Thread] DEBUG BotMain (null) - Stopping the bot. Reason: Could not log back into the game. Your settings are asking us not to.
2013-10-24 23:53:22,728 [Main Bot Thread] DEBUG BotMain (null) - Removing memory patches.
2013-10-24 23:53:22,728 [Main Bot Thread] DEBUG TreeHooks (null) - Removed hook [BotBehavior] d2c21c65-057c-4aa0-b555-a3c1c8641df9
2013-10-24 23:57:56,250 [3] INFO (null) - Session is invalid!Interesting, 'your settings are asking us not to' but it has been trying to login. So.. it looks like the required operation, stopping of the bot, did not trigger after 3 attepts.. so the bot continued to attempt the 3 logon cycle. And then when it did trigger, or was registered in the logs, 80 minutes later, it still did not stop.
So I found the bot still trying to login 4 hours later with:
"Abnormal operations you have tried to long on too many logins in a short duration' popup appearing"
which stopped when I stopped the bot. But logs had not been updating for ~2 hours.
Otherwise, bot was working awesome.
WIMM