• Log in or sign up for an account here: https://www.sythe.org/login

What was the bot nuke?

Status
Not open for further replies.

Ladbrokes

Member
Banned
Joined
Jan 24, 2012
Sythe Gold
0
Messages
71
What was the bot nuke?
I have just come back to runescape in the last week, since 2010. I used to bot back then quite alot with rsbot/rsbuddy/nexus.

I realise botting is kind of been defeated now..but i want to understand what exactly was the bot nuke and how does it stop bots from working?

thanks
 
What was the bot nuke?
If I'm correct, JaGeX changed the code of how RS worked; from a static one to a dynamic one. The static code was easily handled, as there was nothing new each time the hook needed to 'hook' itself to the code. Now that it is dynamic, the code isn't easily hooked anymore and it's pretty much random. That's what defeated the injection bots; they relied on client hooks, which now are pretty hard to get.

Correct me if I'm wrong, though.
 
What was the bot nuke?
The bots were using a loophole in the way Java reads the program, something about higher level classes or something like that, so they changed the way they had the code so that it effectively eliminated the loophole. It is just a set back for botters, eventually they'll be something new. OpenGL will probably become very popular as the next wave of bots, they're a few private ones out there as I understand it.
 
What was the bot nuke?
Correct me if I'm wrong, though.

I've heard about that as well, but I've heard of another explanation that made more sense to me (which doesn't mean that is the correct one).
As you can see there's a lot of green dragon bots and other easy money making bots around, and as Emperor_Nero said, there's already some private OpenGL bots, however, this dragon bots, look so Identical to the old ones that I'm pretty sure it's java scripts like the old rsbuddy/rsbots/etc bots.
This other explanation I heard was that Jagex made a change to the client that makes the people that make the bot clients have to break copyright rights.
And according to my knowledge, the botting developers only break the copyright rights when they make their software public.
If they keep it for themselves it's all fine. That would explain the bots around, that obviously belong to a gold farming company, which has probably developed it's own bot and by not making it public is not breaking any rights.

Feel free to correct me if I'm wrong.
 
What was the bot nuke?
OpenGL will probably become very popular as the next wave of bots, they're a few private ones out there as I understand it.

And ye, as if what I posted before was right, and Java can't be used without breaking copyright rights, OpenGL indeed will be one of the best options, far better than Simba I believe.
 
What was the bot nuke?
Essentially Jagex obfuscated all of Runescape, (nearly doubling the size of the .jar file) and obfuscated their obfuscates (not exactly but it's a much simpler concept to understand).

Essentially, this means that all Injection and Reflection bots have been made exceedingly more difficult to make a functional bot with.

Hooks are still possible from strong patterns, but Jagex updates the game every 6 hours anyway, which means they can easily break any returning reflection or injection bots that make the ever-so-small chance of working again.

What this means is that now, there are only 4 public botting sites that still work:

RiD (Robotz In Disguise) - Works off of color, 3D object recognition, textures, spatial recognition, and advanced mathematics to simulate the most human mouse movements currently available. It uses AI to make decisions in realtime rather than from a infinitely looping script like almost all reflection and injection bots They do not break any copyright or irl laws by making this bot, so it will be around for years to come. No one has been banned from their bots while following Guidelines since 2008.

SCAR - (www.freddy1990.org) Works based off of the Pascal language, and uses color and shapes to interact with Runescape. It's been around since 2004 iirc, and the quality of the script is entirely dependent on the skill and experience of the programmer. It is possible to implement AI into bots with SCAR, however it's not very common, as it is very line intensive programming method. It does breach the DMCA (Digital Millenium Copyright Act), however, it is very difficult to use it for mass goldfarming purposes, and most of it's userbase tends to just level up skills, and therefore Jagex has little reason to go after them legally, however, it is possible in the future.

Simba (http://villavu.com) - Very similar to SCAR from what I understand, pretty all of what I said about SCAR applies to Simba

Runedream (www.runedream.org) - Pretty much the closest thing to RSBuddy as you can get post-bot nuke, as far as similarity. It runs a client, and uses color to function. Only on version 1.02 for the moment though.
 
What was the bot nuke?
I've heard about that as well, but I've heard of another explanation that made more sense to me (which doesn't mean that is the correct one).
As you can see there's a lot of green dragon bots and other easy money making bots around, and as Emperor_Nero said, there's already some private OpenGL bots, however, this dragon bots, look so Identical to the old ones that I'm pretty sure it's java scripts like the old rsbuddy/rsbots/etc bots.
This other explanation I heard was that Jagex made a change to the client that makes the people that make the bot clients have to break copyright rights.
And according to my knowledge, the botting developers only break the copyright rights when they make their software public.
If they keep it for themselves it's all fine. That would explain the bots around, that obviously belong to a gold farming company, which has probably developed it's own bot and by not making it public is not breaking any rights.

Feel free to correct me if I'm wrong.

Incorrect, clients that load RS are breaking copyrights regardless if its a public or private bot. It's just harder to catch if you keep it private because then Jagex doesn't know about it. But its still breaking copyright laws.
 
What was the bot nuke?
" It does breach the DMCA (Digital Millenium Copyright Act), however, it is very difficult to use it for mass goldfarming purposes, and most of it's userbase tends to just level up skills, and therefore Jagex has little reason to go after them legally, however, it is possible in the future."

I just like to clarify this, we are loading actual runescape from a weblink. Rather loading the entire website, we are only loading the JRE which are found online.

Bots like RSBUDDY actually had to compile rs rather than just loading it, to make it simpler.


At the moment, TRIBot will be the future within a week or 2 unless runedream can pushout open gl.
 
What was the bot nuke?
Basically what everyone said above was more or less what happened. The old style injection/reflection bots essentially used the static object/item/npc ID codes. "Go to ID #####, use ID ##### with #####" was how it worked, in a nutshell at least. For an example of how bad it was when an object ID was switched, you may recall some random events becoming FUBAR with about a hundred accounts stuck. This happened, for example, when Jagex changed the object ID of the teleport portal in the Freaky Forester event. The bots successfully went to the coordinates, but they could not find "ID #####" and were stuck.

Nowdays, every single object/item/npc ID is randomized whenever you log in. This meant that 98% of bots were removed instantly from the game.

There are other elements of their bot-nuke as Jagex continues to fight. For instance, instead of a 6-hour forced logout, there is now a 6-hour client token failure. Every 6 hours you have to physically restart Runescape, which is a major pain in the ass to do on dozens of accounts at once. They also won a rather hefty lawsuit against iBot/the Snellman brothers, which establishes legal precedent against doing exactly what Main ftw said.

Right now the RiD/Simba movements have led the botting community through the nuclear fallout, but they are still extremely far behind the giants of RSBuddy and Nexus. Like Main FTW said as well, a few new bots offer some promise of filling their shoes, but it'll be a while until a good enough programming base has been established for anything along the lines of iDungeon Pro or a Frost Dragon Killer that can use cannons, recharge chaotics, etc.
 
What was the bot nuke?
Basically what everyone said above was more or less what happened. The old style injection/reflection bots essentially used the static object/item/npc ID codes. "Go to ID #####, use ID ##### with #####" was how it worked, in a nutshell at least. For an example of how bad it was when an object ID was switched, you may recall some random events becoming FUBAR with about a hundred accounts stuck. This happened, for example, when Jagex changed the object ID of the teleport portal in the Freaky Forester event. The bots successfully went to the coordinates, but they could not find "ID #####" and were stuck.

Nowdays, every single object/item/npc ID is randomized whenever you log in. This meant that 98% of bots were removed instantly from the game.

There are other elements of their bot-nuke as Jagex continues to fight. For instance, instead of a 6-hour forced logout, there is now a 6-hour client token failure. Every 6 hours you have to physically restart Runescape, which is a major pain in the ass to do on dozens of accounts at once. They also won a rather hefty lawsuit against iBot/the Snellman brothers, which establishes legal precedent against doing exactly what Main ftw said.

Right now the RiD/Simba movements have led the botting community through the nuclear fallout, but they are still extremely far behind the giants of RSBuddy and Nexus. Like Main FTW said as well, a few new bots offer some promise of filling their shoes, but it'll be a while until a good enough programming base has been established for anything along the lines of iDungeon Pro or a Frost Dragon Killer that can use cannons, recharge chaotics, etc.

Thanks alot mate, has really helped me understand more about the bot nuke. & Everyone's posts above. Thanks :)
 
What was the bot nuke?
RS got sick & scared 'cause of their IGE (In game economy) because of too much bots being released and being used a lot. So they decided to nuke about 99% of the working bots. Therefore, majority of the bots are not working anymore.
 
What was the bot nuke?
" It does breach the DMCA (Digital Millenium Copyright Act), however, it is very difficult to use it for mass goldfarming purposes, and most of it's userbase tends to just level up skills, and therefore Jagex has little reason to go after them legally, however, it is possible in the future."

I just like to clarify this, we are loading actual runescape from a weblink. Rather loading the entire website, we are only loading the JRE which are found online.

Bots like RSBUDDY actually had to compile rs rather than just loading it, to make it simpler.


At the moment, TRIBot will be the future within a week or 2 unless runedream can pushout open gl.

Loading RS to RAM on through any location or client other than those that have been approved by Jagex = Breach of DMCA. That's how Blizzard took down someone who made a client for WoW.
 
What was the bot nuke?
Its not even that, I am 100% sure there is nothing wrong with loading unmodified runescape, because I can easily write a browser that just loads the rs applet, which is essentially what swiftkit and all those other rs tool kit is. Loading runescape from source or modified source is breaking dcma because those files are not publically available, but the link to their applet is.
Sec. 1201. Circumvention of copyright protection systems

* (a) Violations Regarding Circumvention of Technological Measures.
o (1)
+ (A) No person shall circumvent a technological measure that effectively controls access to a work protected under this title. The prohibition contained in the preceding sentence shall take effect at the end of the 2-year period beginning on the date of the enactment of this chapter.
Loading rs does not bypass anything, but if some where were to obtain their source code (obviously only through hacking) they've bypassed their anti copyright.



Back to blizzard, the guy wrote a completely (minimal) client where he was able to run 100s of bots per comp.
[youtube]AUjuefLqphY[/youtube]
 
What was the bot nuke?
Its not even that, I am 100% sure there is nothing wrong with loading unmodified runescape, because I can easily write a browser that just loads the rs applet, which is essentially what swiftkit and all those other rs tool kit is. Loading runescape from source or modified source is breaking dcma because those files are not publically available, but the link to their applet is.

Loading rs does not bypass anything, but if some where were to obtain their source code (obviously only through hacking) they've bypassed their anti copyright.



Back to blizzard, the guy wrote a completely (minimal) client where he was able to run 100s of bots per comp.
[youtube]AUjuefLqphY[/youtube]


Doesn't matter. Loading any game to RAM through any client or location other than is approved by the game makers = breach of DMCA. Swiftkit was actually nearly sued by Jagex when it first came out, and users were banned for using it at first. Swiftkit met with Jagex and settled on a legal agreement, allowing Swiftkit to exist. It's all straight in their ToS. Jagex has the right to sue anyone who develops even a client that loads a normal version of RS. Is it likely that they will to a company that isn't really harming them? No. But that doesn't mean they can't or won't do it to Simba.
 
What was the bot nuke?
Thank goodness simba doesn't come with smart :)

Even so: http://services.runescape.com/m=rswiki/en/Macroing,_and_third-party_software
These are some examples of third party software we ask you not to use:
*Software that attempts to communicate directly with our game worlds.
*Software that monitors, modifies or decrypts the communications between our game applets and our game worlds.
*Software that generates input to our game applets. This includes software that automatically moves the mouse pointer or generates mouse clicks or key presses.
*Modified or replacement versions of our game applets. Reverse-engineering our game applets is strictly prohibited. Using a modified version of our game applets is not permitted for any reason. Third-party software that displays pages/content from our website(s), and that has specific features (i.e. toolkits) must not be used to access our website unless that software conforms with all of the other rules, and the following additional rules:


It must not encourage rule-breaking or endanger users.
It must not contain adverts or links to websites that encourage rule-breaking or endanger users.
It must not automatically make repeated page/content requests from our website or otherwise make excessively bandwidth-intensive requests from our servers (each page/content request should only be in direct response to a user request each time).
It must not bypass the normal navigation of our website for users wishing to reach the game worlds. The software should initially only point at the front page of our websites, and should require the user to navigate through the website normally to reach the game worlds. The software must not contain or acquire direct links to the game applet.
It must not hide or encourage the hiding of any of the adverts on our website. To avoid encouraging users to hide the advert above the game, the pane displaying pages from our website must default to at least 630 pixels high (if viewed on a screen with a resolution higher than 800x600), and it must not be possible to resize it to less height than that, i.e. the page must be displayed in such a way that both the game and advert are fully visible at the same time.
It must not attempt to make it easier to enter a busy game world than it would be for users not using the software. It must not contain any features to make it easier to enter or monitor busy worlds.
If the software has its own integrated chat feature, separate from the game chat, it should make it very clear to users that this chat is not part of our games and is not official, endorsed, or moderated by Jagex in any way. Furthermore, this chat should still be moderated (just not by us), and the moderators should not allow chat which infringes our Rules of Conduct. To avoid confusion with the official game chat, moderators of the external chat should not be indicated with a silver or gold crown. If the chat is IRC based, then the software should only allow access to IRC channels which conform with the above rules.
We ask our players to be aware that there is dangerous software available that won't necessarily be spotted by their anti-virus software.

But again, simba doesn't have any of those feature unless they install 3rd party applet and applet (which only violate the one of them), people must install smart applet made by benland and the srl library made the entire community + people from years ago + those who has passed away during those time.


Its like how I can bot runescape with eclipse or visual studio, simba and scar is just a compiler, and people abuse the ability to add extension and library to do illegal things.
 
What was the bot nuke?
Yeah, jagex destroyed all good bots that were stable and good. Now all we are left is with simba, and other cheap ass coded bot called rid.
 
Status
Not open for further replies.
Runescape Gamblingrunescape gambling
Back
Top