Gingerbread
New Member
- Joined
- Jul 29, 2012
- Messages
- 171
- Reaction score
- 3
hi,
I mentionned this a while back in #demonbuddy, have had another idea regarding the Inactivity timer and how to improve it so thought I'd post here.
Rather than automatically forcing a LeaveGame when the timer trips can we please be able to choose a behaviour for it as an alternative to quitting and starting over.
Since we have been able to split profiles into chunks and use a plugin to switch profiles mid run if we could choose to TP to Town in the event of the timer firing this would allow users to continue until the end of their profile set without potentially losing 5 stacks of NV and the added MF/rares that that gives.
Also if a timer trip could set a flag that could be read from within a profile that would help a lot in debugging potential stucks before releasing new work.
If there was a variable called "stuck" which was set to False by default that switched to True in the event of the inactivity timer firing that you could query inside a profile, we could have an alternate pathing route the bot could run on a retry of an area. <if condition stuck=true> use this set of moveto commands</If> something like that.
Another small addition that would help is if the stuck variable recorded the bots position on the map when the inactivity timer fired. So that you could query stuck and it would return false, or would return true; xyz.
I mentionned this a while back in #demonbuddy, have had another idea regarding the Inactivity timer and how to improve it so thought I'd post here.
Rather than automatically forcing a LeaveGame when the timer trips can we please be able to choose a behaviour for it as an alternative to quitting and starting over.
Since we have been able to split profiles into chunks and use a plugin to switch profiles mid run if we could choose to TP to Town in the event of the timer firing this would allow users to continue until the end of their profile set without potentially losing 5 stacks of NV and the added MF/rares that that gives.
Also if a timer trip could set a flag that could be read from within a profile that would help a lot in debugging potential stucks before releasing new work.
If there was a variable called "stuck" which was set to False by default that switched to True in the event of the inactivity timer firing that you could query inside a profile, we could have an alternate pathing route the bot could run on a retry of an area. <if condition stuck=true> use this set of moveto commands</If> something like that.
Another small addition that would help is if the stuck variable recorded the bots position on the map when the inactivity timer fired. So that you could query stuck and it would return false, or would return true; xyz.
