Jump to content
View in the app

A better way to browse. Learn more.

OSBot :: 2007 OSRS Botting

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Valkyr

Members
  • Joined

  • Last visited

Everything posted by Valkyr

  1. I played the beta, which was dank. Two maps got boring rather quickly. How many maps does it come with? The all-heroes battle pretty much sold it for me anyway tbh
  2. Already have CSGO. Zombies is cancer anyway, gonna get Battlefront
  3. Bank.open() uses the NPC as well as the booth. The scrip is probably clicking the NPC before the player is actually in the bank. It's because the NPC isn't reachable, but the bank (obviously) only opens when you're facing the booth..
  4. Hunter isn't available presently
  5. Not presently Which script?
  6. Works great now, thanks!
  7. Today, out of the blue seemingly.
  8. In debug mode! Listening for transport dt_socket at address: 5005 Stealth injection class-filter enabled! Loaded 32 local scripts and 5 SDN scripts. [DEBUG][11/09 11:47:56 PM]: OSBot is now ready! [INFO][11/09 11:47:57 PM]: Loaded 6 RS accounts! [INFO][11/09 11:47:58 PM]: Welcome to OSBot 2.4.2! [INFO][11/09 11:48:18 PM]: Updated injection hooks for client revision : 98! Created temp copy of nattach_64.dll as C:\Users\Aiden\AppData\Local\Temp\rrqw3680894836048588893.dll Created temp copy of stream_64.dll as C:\Users\Aiden\AppData\Local\Temp\wqw8526087086504495623.dll Bot exited with code : -1073741819 Process finished with exit code -1073741819 (0xC0000005)
  9. cos i'd be breaking da r00lz if i did
  10. Oh, so this is like when I went from VChopperAIO to Zen Chopper Pro
  11. my code is self-documenting
  12. context.getTaskExecutor().execute( new SelectionTask(context, () -> !context.getInventory().contains(food), // When out of food new WebWalkTask(context, context.getWebWalker().getClosest(bank)) .chain(new WithdrawTask(context, food, -1)), new ExecuteOnConditionTask(context, context::isIdle, // Only run when idle new WebWalkTask(context, context.getWebWalker().getClosest(FLESH_CRAWLER)) .chain(new InteractEntityTask(context, FLESH_CRAWLER, ATTACK)) .chain(new ExecuteOnConditionTask(context, () -> context.getCombat().getHealthPercent() < 25, // Eat when HP is low new InteractItemTask(context, food, EAT)))) ));
  13. It was likely fixed and broke again. Banking is currently broken afaik (API issue). If it's not banking, submit a bug report and I'll fix it.
  14. Very nice update Alek! As per my suggestion though, I would say the p2p/f2p world option should ideally be paired with the accounts. I'm guessing that will require AccountDB changes though. Regadless, love it, good work!
  15. Free postcount plox?
  16. Key word; "yet". It's happened before.
  17. They're generally known to profile on a per-account basis. If you're switching between botting and legit play, then you're giving two different patterns of data; giving them a red flag. Botting one account shouldn't leave a seperate, legit account at risk. Not unless you're trading between the accounts in question, which would only result in a ban because your legit account is now in possession of illegitimate items. All IP flagging does is say "Hey, this IP is known to have been used by a bot". This information is pretty useless, since each IP can potentially be used by hundreds/thousands of different people, and isn't generally effective for catching bots. I like to believe their detection is based primarily on behavioral analysis on a per-account basis and nothing more (beyond a small number of other mechanisms).
  18. It's not on the SDN anymore.
  19. "a few features such as dynamic signatures should be restored as well (pending script updates)." What?

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.