@FrostBug Would it be possible to change the osbuddy API to an alternative one. This might make the profit feature a bit less accurate but it would be up all the time, meaning it doesn't rely on osbuddy's api being up all the time. I am not concerned about knowing my profit in the gui, but the script keeps spamming DEBUG: Re-submitted lookup of item: xxxx which floods my network and makes the script unusable alltogether.
Thanks for clearing it up. I don't consider it an issue tho, just wanted to point it out in case it was a 'small' fix. I used to code a little myself and find things like this interesting.
It bothered me since it was hogging some network bandwidth.. Since it kept sending the same request.
I did not mean to start something as I was just pointing out a part that did not work properly at the time asking for an explanation so I could better understand it.
Plus I made a valid suggestion for the script later as there is a flaw regarding killing small monsters for the XX%.
I sincerely hope you understand the reasoning better now.
Also, whenever it is going for more % and it is killing bloodworms, skeles, etc. it starts combat with a new target after killing the last one required at say ie. 83% when I want 88% and then immediately stops combat and clicks on the door to open it. Could you maybe find a way to check the % completed and when you only need to kill one more make 'open door' the next action. This would seem a bit less 'scripted'.
Works fine but since today it started spamming the debug with DEBUG: Re-submitted lookup of item: xxxx rune
And it just keeps doing this in the background over and over.