What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Preserving current instance after executing chicken logout

poe3210

New Member
Joined
Mar 25, 2014
Messages
17
Reaction score
0
Currently a chicken logout is treated as instance termination, i.e, when the bot auto relogs, and continues its routines, it opens a fresh instance of the chosen map instead of going back to the half completed instance. This obviously means that all the progress accrued in the chickened instance is lost, including possible loot that was dropped and not instantly picked up prior to chicken execution. Apart from possible loot loss another implication is slow level progress. It is quite possible that a character is weak enough to never be able to reach a waypoint in a map despite multiple attempts and resets, but if chickened instance were preserved, the bot could easily be expected it to eventually attain that waypoint after some number of chicken attempts.

Note: the feature Deaths before new instance accomplishes the advantage of exactly what I am suggesting but it is obviously incompatible with Chicken use

One way would be to count a chicken execution as a death wrt deaths before new instance
 
Last edited:
I guess the best 'solution' to this is to equip/skill your character accordingly, make him stronger.

I don't see anything positive (exceptions may proof me wrong, though) in going back to an instance that caused my character to chicken.
 
The current plan is to add a simple system to track the area name and a flag for if a new instance should be taken. We'll then have a function users can call along with using Logout to set the flag so the next time the area is taken, it'll use that flag rather than the default logic of either never or always making a new instance. A similar system would be useful for corrupted areas as well to avoid the infinite looping issue.

This will be worked in soon, but priority right now is integrating in the new input changes and gradually enabling them for different parts of the bot rather than doing it all at once, which might cause too many issues to solve in a timely manner. In addition, exploration will be changed in the future to allow users to specify completion stuff.
 
Back
Top