kagamihiiragi17
Community Developer
- Joined
- Jun 24, 2014
- Messages
- 873
Okay, I think I might have it fixed. as kagamihiiragi17 suggested, I added a decorator just for setting _done to true (pretty much a copy/paste from their post because its 3am and I am tired/lazy,, thank you by the way kagamihiiragi17). I also added treeroot.stop in that decorator, set _isdone to true, and called treeroot.start after setting the value. I know this probably is not the correct way to do this, but lets face it ... im new to creating plugins for buddybots, but have been using them for many years now.. if anyone knows of a better way, Please let me know.
I tested this with a cluster farm clipping that was posted in previous page.. since I did not feel like sitting here the hour to test it.. i made random time conditions in the profile and let the bot run for a little bit. At each timebetween condition, it switched to appropriate class and ran to specific hotspot and waited for the next timebetween condition.. it then changed class and ran to that one.. this is about the extent of the testing that was done so far.. please try it and monitor it and see how it works for you. Updated attachment in OP
thanks to everyone for input.
Yeah, I just had the thought that with the way you had it set up before (setting _done within one decorator), if the ChangeJob tag was called and the player was already the correct class, the tag would never exit because _done would never be set to true. With the way you have it set up now, if the ChangeJob tag is called and the player is already the right class, it'll set _done to true instantly and move on to the next thing in the profile. I think that's way better behavior.