What's new
By:
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

Autologin

V

vspr

New Member
Joined
Jun 8, 2016
Messages
10
Reaction score
0
When im gettin Chiken script DC, bot not even trying to login back.

Code: 
[FinishCurrentAction] Waited 120 ms for the action to finish Move.
[LootItemTask] Now attempting to interact with the item. This is the #1 attempt.
[Execute][oldgrindbot_on_loot] Scroll of Wisdom Metadata/MiscellaneousObjects/WorldItem 0 Currency 3527.
[InteractWith] Now attempting to highlight 3527.
[InteractWith] Now attempting to interact with 3527.
[LatencyWait] Now sleeping 85 ms.
[FinishCurrentAction] Waited 0 ms for the action to finish Interaction.
[FinishCurrentAction] Waited 131 ms for the action to finish Interaction.
[AreaStateCache] The location 3527 [Scroll of Wisdom] is being removed because the WorldItem does not exist.
Can cast Flame Totem
Casting Flame Totem1
[UseAt] 2 True {728, 455}
*Casting Totem Because there are no totems near our main target or one of the totems can't see 
[Logic] Now moving towards {737, 459} because [dist (58) > MaxRangeRange (35)]
[BeginUseAt] 8 False {779, 472}
[Logic] Now moving towards {737, 459} because [dist (58) > MaxMeleeRange (10)]
[Logic] Now moving towards {737, 459} because [dist (56) > MaxMeleeRange (10)]
[Logic] Now moving towards {737, 459} because [dist (55) > MaxMeleeRange (10)]
[Logic] Now moving towards {737, 459} because [dist (52) > MaxMeleeRange (10)]
[Logic] Now moving towards {737, 459} because [dist (50) > MaxMeleeRange (10)]
[Logic] Now moving towards {737, 459} because [dist (48) > MaxMeleeRange (10)]
[Logic] Now moving towards {737, 459} because [dist (45) > MaxMeleeRange (10)]
[Logic] Now moving towards {737, 459} because [dist (44) > MaxMeleeRange (10)]
[TrackMoreMobs] Now adding Ancient Archer (415) at {610, 401}.
Can cast Flame Totem
Casting Flame Totem1
[UseAt] 2 True {727, 456}
*Casting Totem Because there are no totems near our main target or one of the totems can't see 
[Logic] Now moving towards {737, 459} because [dist (39) > MaxRangeRange (35)]
[BeginUseAt] 8 False {758, 466}
[Logic] Now moving towards {737, 459} because [dist (38) > MaxMeleeRange (10)]
[Logic] Now moving towards {737, 459} because [dist (36) > MaxMeleeRange (10)]
[FinishCurrentAction] Waited 0 ms for the action to finish Move.
[FinishCurrentAction] Waited 108 ms for the action to finish Move.
[FinishCurrentAction] Waited 233 ms for the action to finish Move.
[FinishCurrentAction] Waited 344 ms for the action to finish Move.
[UseAt] 3 True {737, 459}
Can cast Flame Totem
Casting Flame Totem1
[UseAt] 2 True {728, 455}
*Casting Totem Because there are no totems near our main target or one of the totems can't see 
[FinishCurrentAction] Waited 0 ms for the action to finish Flammability.
[TrackMoreMobs] Now adding Ancient Archer (416) at {578, 436}.
[TrackMoreMobs] Now adding Ancient Archer (418) at {591, 419}.
[TrackMoreMobs] Now adding Ancient Archer (417) at {591, 405}.
[TrackMoreMobs] Now adding Shambling Cadaver (608) at {595, 624}.
[FinishCurrentAction] Waited 101 ms for the action to finish Flammability.
[FinishCurrentAction] Waited 237 ms for the action to finish Flammability.
[FinishCurrentAction] Waited 365 ms for the action to finish Flammability.
[UseAt] 3 True {737, 459}
[BeginUseAt] 2 False {739, 459}
[InjectKeyEvent] 156 ms sleep for 32.
[UseAt] 7 True {757, 467}
[BeginUseAt] 2 False {739, 459}
[InjectKeyEvent] 83 ms sleep for 32.
Can cast Flame Totem
Casting Flame Totem1
[UseAt] 2 True {730, 455}
[InjectKeyEvent] 113 ms sleep for 32.
*Casting Totem Because there are no totems near our main target or one of the totems can't see 
[FinishCurrentAction] Waited 0 ms for the action to finish Summon Flame Golem.
[FinishCurrentAction] Waited 113 ms for the action to finish Summon Flame Golem.
[FinishCurrentAction] Waited 227 ms for the action to finish Summon Flame Golem.
[FinishCurrentAction] Waited 342 ms for the action to finish Summon Flame Golem.
[FinishCurrentAction] Waited 446 ms for the action to finish Summon Flame Golem.
[BeginUseAt] 2 False {739, 459}
[InjectKeyEvent] 153 ms sleep for 32.
[BeginUseAt] 2 False {739, 459}
[AutoLogin] DelayBeforeLoginAttempt | LoginAttemptDelay: 00:00:10.
[AutoLogin] The bot will wait 00:00:10.8000000 before logging in.
[AutoLogin] > An unexpected disconnection occurred.
[Stop] Now requesting the BotThread to stop.
[OldGrindBot] OnStop
[CommonEvents] Stop
[AutoLogin] Stop
[DevTab] Stop
[GemLeveler] Stop
[ItemFilterEditor] Stop
[ObjectExplorer] Stop
[Stats] Stop
[StuckDetection] Stop
[Totemizer] Stop

Tryed to delete
Code: 
else
			{
				foreach (var entry in logEntries)
				{
					// Unable to connect to login server.
					if (entry.Contains("Unable to connect"))
					{
						BotManager.Stop();
					}
				}
			}

but it doesn`t help
 
pushedx said:
It's actually this set of logic, https://gyazo.com/80936a63e8b57fef777aba5c5ea54509 but I highly recommend not removing it.

How are you chickening, because a normal logout shouldn't have that DC message.
Click to expand...
i'm using external Gurud`s autoflask and autoscripts, btw i was using that chiken before, w/o any problems w exilebuddy.

Thanx a lot, thats work.

pushedx said:
highly recommend not removing it.
Click to expand...
Yes, i got it, but w/o autologin - bot is useless for me.
 
pushedx said:
It's actually this set of logic, https://gyazo.com/80936a63e8b57fef777aba5c5ea54509 but I highly recommend not removing it.

How are you chickening, because a normal logout shouldn't have that DC message.
Click to expand...
Is there a logic behind not trying to reconnect after "unexpected dc"?
It causes much downtime for me and I would be interested in removing the code, but I wanted to now first what was the reason behind adding it.
 
I'll try to make some changes to reduce the plugin from stopping when it happens a few times.

And yes, there's a few specific error cycles where if you login successfully to character selection, then join the game, and are booted back to the login screen, the bot before would endless try again and again. The only way to detect that error and other back to title screen errors is though the new check, but it can use some tweaking I guess.
 
You must log in or register to reply here.
Back
Top