SolarStrike Software

I'm starting this thread to discuss an idea that was generated from within a different topic. I didn't want to hijack that thread so I'm starting this new thread.

Every once in a while, one of my characters gets stuck inside the Ancient Treasures minigame at the point where it is supposed to click the candlestick to transport out. When this happens, it seems the MM code is stuck in a loop where it thinks it clicked the candlestick and selected the option to transport out but did not and it sits there waiting (sometimes for hours until I notice it). If I manually click and exit the minigame, MM then resumes the waypoint where it should. So the question is... how can you watch for it getting stuck and force it's way out? Because the code being executed is stuck in a loop, no code you add to that waypoint can watch for the player being stuck. It would have to be in a separate MM window. So this got me to thinking... maybe I could create the following as a solution:

in my AT waypoint file, I add code that will launch a new, separate MM window, attach it to the same character, and all it will do is it's own loop of watching for player.X and player.Z. If those aren't constantly changing (for example, 30 seconds goes by and those values haven't changed) then the bot must be stuck. If those conditions are met, then I could either have it attempt to click the candlestick and get out, or I could have it do a recall and go to where it needs to go. Regardless of which route I choose to make it go, I would then have to make it detect whether it is now working or not, and decide also if I need to kill the other waypoint file/MM that is running and start a fresh one, or whether to take it over from the new one that was watching to unstick.

On top of that, If I wanted to be able to use this functionality from more than 1 waypoint, I would have to either build conditions within the "unsticking" waypoint, or make it where the recovery option is the exact same regardless of which waypoint it was running.

I'd like to hear anyone's input on this as I begin attempting to build such a function. There are a lot of you on these forums that are much better than me at coding so as I work on this I'll post some code and surely, I'll be asking for assistance.

i have been having a small problem when a char goes to leave castle it thinks it clicked the portal and then stands there waiting to exit. I think I may know a way to fix it just make it wait so long back up and try again.

I have never used the exit from AT so not sure about the getting stuck at candlestick I usually run that one manually since I just do a few chars. I was thinking of setting up a path to do those minis.

I had also here and there problems with the mini-game wps I simple added more checks and repeat it when it fails.

I had added checks and repeats as well, but they didn't help because as Rock5 mentioned, it gets stuck in a loop so it's not going to time out or check anything else. Unless something external makes it stop, hence a second MM window to monitor for lack of movement. If I can get something built and test it with AT and it works, then I can think about other ways to implement it.

I think he meant extra checks inside the loop. In the end stopping it getting stuck in the loop in the first place is probably the best solution.

Oh, I see. Well, I had tried to figure out how to put an extra check in there to keep it from getting stuck and it doesn't seem to work. So here's the part of code where it gets stuck:
I think it gets stuck on the waitForLoadingScreen because the bot will sit there forever until I manually click the candlestick and exit the minigame. Then the bot will resume. For some reason it thinks it clicked the candlestick and the message popup but the click didn't actually take. And like I said, it only does this maybe once every 5th or 6th time so it's not every time. How could I change this code to make absolutely sure those items get clicked? Also, I don't know why the waitForLoadingScreen doesn't timeout. I thought it had a built-in timeout function?

You have to put a maximum time in it for it to time out, eg. The problem you are having might be because there is no time between clicking the candlestick and checking the popup. Try putting a yrest between them.

To make sure it works you could repeat it like so.

Thanks Rock5. I'll give that solution a try. Hopefully it will take care of it.

I check the popup has actually popped up and you can check which type it is too, I use this to watch for an invite to ride a mount invitation.
The thing to also keep in mind that the StaticPopup1 will only accept the top popup, if you have another popup already there for what every reason then it will accept the top one. An example is when you join a party and are in different channel to the party leader, a popup will appear asking if you want to change channels.

I think I had a function to simplify this once. Here it is. It searches for the popup with the matching name then accepts it even if there are other popups open at the time. Requires you to know the name of the popup but if you don't supply the name then it accept the first popup it finds.

To get the popup name you can just initially use Then when it prints the message You can insert that into the AcceptPopup command to make sure it always accepts the right popup.

So, I wonder if the problem could be (because I've never witnessed it, it always happends when I'm not watching) if the low on memory error pops up and maybe that's causing the bot to click the wrong popup or something weird? Anyway, I've ben using my new code on this part and haven't seen the problem yet. Still monitoring to see how it works though because I haven't had much time to run my stuff lately, and I think I introduced a problem somewhere else in code (the code that controls my many dailies and minigames amongst my characters) so I've got to work on fixing that.

with the code posted it will just keep on doing the click staticpopup1 so in that case it wouldn't matter if there was other popups because it will eventually click on them all.

The reason I created my userfunction was because I used to worry about player hanging around teleporter npcs, watching for botters. Then if they challenge you to a duel just before your bot reaches the npc it could end up accepting the duel.