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.

Why script writers on osbot fail so hard.

Featured Replies

Why botters on OSBot fail:

 

1. They think that when they get banned it's the scripter's fault for not including enough anti-ban.

2. They think that anti-ban holds precedence over their idiotic botting habits such as suicide botting at a popular botting spot.

3. Many of them try and tell the scripter what they need to do to fix problems using their deluded pseudo code 

(one time a user told me to use "strings" for rocks instead of "ids", little does he know that all rocks wheter runite or tin are all called "rocks").

4. They think scripts are made overnight.

5. They will frequently try scripting only to release terrible scripts because they have no knowledge in programming.

6. They think that randoms are handled by the script.

7. When a hook or method is broken on an RS Update, they scream and chargeback scripters because they think it's the script's fault.

8. They don't read client debugs

9. They don't read instructions on how to use the script on the script topic, instead they make a post stating that it doesnt work. One example is where to start a script and/or required items.

10. They have a limited knowledge of Runescape outside Lumbridge and Varrock and any scripts that require a quest will never be as popular as a flax picker or bow stringer.

Damn, you summed it up like it was nothing.

  • 3 weeks later...

The script was coded to click on the spell ONE time, then click on the NPC. Then go back to the spell and click the NPC. The fact that it missed and couldn't click the spell again would be the script's fault because it doesn't have a failsafe on it. 

I'd honestly love to here the language you've been programming for "5+ years". I've made Apple applications in Objective C, Multiple things in C++, and a few in Visual Basic. And the fact that you're saying that it's the scripters fault for the spell not being clicked? No, it's not and I'll show you since you're so smart. 

client.getInterface(Parent).getChild(Child).interact("Cast");

Now what this means is that the CLIENT meaning the OSBOT PROGRAMMERS, developed the exact method you used to say is the scripters fault and not the developers. Just keep complaining about things people make for free.

Recently Browsing 0

  • No registered users viewing this page.

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.