Nate Thompson

Hey @Czar - mind if i get a trial for this?

Running into two repeatable loops during Fairytale I, both inside the missing-item resolver. Posting them together because they appear to be the same root cause (script treating non-buyable or produced items as direct missing items instead of falling back to create/craft steps). 1) Crushed gem loop (IDs 1633 / 1625 / 1755) The script tries to get 1633 – Crushed gem. Instead of crushing a gem, it loops between: 1625 – Uncut opal 1755 – Chisel re-adding items to the multi-missing list trying to buy a chisel from GE resetting the list repeating forever It never actually performs use chisel on gem. Relevant log snippet: We need Crushed gem for the quest addItemToMultiMissingList (1755, 1) Pursuing multi-missing list item id 1755 for main item: 1755 pursueMissingItem->1755-1 secondary: true Buying item off GE (3) "missing_item_multi_id_list" changed to "1625_1,1755_1," (2) We have this item (1625) in our bank doWithdrawMissingItem 1625 mainWithdraw(uncut opal-1625) We need Crushed gem for the quest addItemToMultiMissingList (1755, 1) ... (repeats indefinitely) Expected: Withdraw gem → use chisel → produce 1633 → continue quest. Actual: Script treats chisel itself as a “missing product,” tries to buy it, then loops. 2) Charged druid pouch loop (ID 2958) Later in the quest, the script gets stuck preparing a charged druid pouch (2958). Instead of switching to the actual charging logic (Nature Grotto), it: Treats 2958 as a directly missing item Adds it to the multi-missing list Calls pursueMissingItem() again Re-adds it Re-pursues it Infinite loop Relevant log: pursueMissingItem->2958-1 secondary: true Preparing a charged druid pouch for the quest addItemToMultiMissingList (2958, 1) Pursuing multi-missing list item id 2958 for main item: 2958 pursueMissingItem->2958-1 secondary: true Preparing a charged druid pouch for the quest addItemToMultiMissingList (2958, 1) ... (repeats indefinitely) Expected: If 2958 missing → withdraw 2957 (druid pouch) → go to grotto → charge pouch. Actual: Script loops endlessly because 2958 cannot be bought/withdrawn. Setup details: Started Fairytale I from the beginning (bot initiated the quest). Normal teleports/tabs available. Coins in inventory. No special modes (AFK/cannon/etc). Client restart doesn’t change behavior. Can provide more logs or run in debug mode if helpful.

Want to see if this is more reliable than Token's version. You mind if I get a trial?

Trial please, looks good.

FYI / Bug Report: 1-Day Ban While Running “X Marks the Spot” on Stealth Quester Not blaming the script - just sharing what happened so others know what to look out for, and in case it helps the dev troubleshoot. I picked up a 1-day botting ban early this morning while running on the X Marks the Spot quest. What Happened The bot got stuck at the Veos interaction near Port Sarim. It started looping - trying to walk to the same tile ([3228, 3242, 0]) over and over while logging WebWalkingEvent; Terminated! Exceeded attempt threshold. It never broke out of that loop, didn’t move or rotate the camera, and kept retrying the same failed path roughly every two seconds. From a detection standpoint, that kind of repetitive behavior probably looked obvious. After about 20 seconds of looping, the account was logged out. When the auto-login triggered, it came back with Login Code 4 (“Your account has been involved in serious rule breaking”), and the script shut down. Environment Mode: Stealth Injection (not mirror) Quest queue: 9 quests total - failed on #8 (X Marks the Spot) Hop / break settings: Default (world hop between quests enabled) Input: false Timestamp: 11-Nov-2025, around 2:00 AM Session log: https://pastebin.com/peGRgaiT Jagex Ban Evidence Offence: Bot Busting Moderate “Account temporarily banned for macroing in OldSchool. Our macro detection system has detected illegal third-party software… Jagex are able to accurately detect all illegal 3rd party software…” Pretty standard canned message, but it lines up exactly with when the loop occurred. Takeaways The issue looks like a navigation fail on the Veos dialogue step. The script doesn’t seem to have a failsafe for repeated WebWalkingEvent failures - it just keeps hammering the same path until logout. For anyone queuing this quest, I’d recommend watching it or running it manually until that logic is updated. Not pointing fingers - the script works great for most quests. Just posting this as an FYI and log reference in case it helps with a patch or saves someone else a ban. Tagging @krisped for visibility.

[INFO][Bot #1][12/13 05:08:53 PM]: Location: Rimmington [INFO][Bot #1][12/13 05:08:54 PM]: Terminating script Progamerz AIO Prayer... [ERROR][Bot #1][12/13 05:08:54 PM]: Error in script executor! java.lang.NullPointerException at org.osbot.rs07.api.model.Item.isNote(bk:229) at b.cON.F(t:8) at org.osbot.rs07.api.util.ItemContainer.filter(ip:45) at org.osbot.rs07.api.util.ItemContainer.getItem(ip:194) at b.cON.k(t:8) at b.cON.F(t:234) at b.cON.E(t:240) at main.Main.onLoop(i:96) at org.osbot.rs07.event.ScriptExecutor$InternalExecutor.run(eo:181) at java.lang.Thread.run(Unknown Source) [INFO][Bot #1][12/13 05:08:54 PM]: Script Progamerz AIO Prayer has exited!