Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. it was for sure, they changed the interface like a few times in the past few months
  3. I have a Zombie axe and rune crossbow with rune bolts would this be supported?
  4. Today
  5. Is it worth it to appeal to a ban saying you just got a bond and wanted to grind what you could with the short membership? Or will it be leaving me open to an investigation to make matters worse?
  6. 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.
  7. nicee tyy for the charter ship fix that was suuuuuuch a pain <33
  1. Load more activity
×
×
  • Create New...