|
|
| Line 1: |
Line 1: |
| − | ==Introduction==
| |
| | | | |
| − | [[File:Spectate.png|right|thumb|300px|RSBuddy running 3 bots.]]
| |
| − |
| |
| − | I will be working on [http://rsbuddy.com/ RSBuddy] for the remainder of the year. RSBuddy is an application that provides the backend and environment for automation tools known as scripts. Scripts perform tasks in the online game [http://runescape.com/ RuneScape] to acquire in-game currency or experience. Experience accumulates and the player’s game avatar gains levels at specific amounts of experience.
| |
| − |
| |
| − | Hundreds of thousands of RuneScape players use automation software such as RSBuddy to either enhance their gaming experience or acquire bulk in-game currency and high-level accounts to sell for real-word currency.
| |
| − |
| |
| − | This is a very large joint effort between [http://rsbuddy.com/forum/members/paradigm/ myself (Paradigm)], [http://rsbuddy.com/forum/members/jacmob/ James Thompson (Jacmob)], [http://rsbuddy.com/forum/members/arbiter/ Ivan Gomes (Arbiter)], [http://rsbuddy.com/forum/members/blackbone/ Anthony Crimando (Blackbone)], and [http://rsbuddy.com/forum/members/noeffex/ Aaron Rosenbaumer (NoEffex)]. We maintain and develop the website, bot, servers, community/forums, etc. We also have forum moderators that help manage the forums by deleting unwanted posts, moving topics to the proper sections, and providing general support. In addition, anyone who is capable may write and post scripts to our script repository.
| |
| − |
| |
| − | ==Links==
| |
| − |
| |
| − | * [http://rsbuddy.com/ Homepage]
| |
| − | * [http://static.rsbuddy.com/doc Scripting API Javadoc]
| |
| − | * [http://www.youtube.com/watch?v=t4FdrzEKcYg Demo of fishing script in action]
| |
| − | * [http://rsbuddy.com/download/ Download]
| |
| − | * [http://scripts.rsbuddy.com/ Script Repository]
| |
| − | * [http://rsbuddy.com/forum/ Community Forum]
| |
| − |
| |
| − | ==What will I be doing?==
| |
| − |
| |
| − | * '''Updating the hooks.'''
| |
| − | ** The RuneScape client is obfuscated. Bot developers write applications known as updaters to identify the classes and fields our bots need to access. Hooks are the standard-to-obfuscated name mappings (e.g. <nowiki>player.name</nowiki> is <nowiki>kl.rd</nowiki>). We write transforms and identifiers as flexibly as possible to look for bytecode patterns that can continue to identify across RuneScape client versions without modification. Once properly identified, accessor methods are injected directly into the client’s class files’ bytecode with public access modifiers so that the bot can grab the data and act on it. Occasionally, when something big changes, our identifiers break and we analyze the new bytecode in order to write new ones that properly identify the fields/classes. This occurs for a few fields every normal update, and for almost everything in big updates (e.g. game engine changes). I’ve uploaded a very old updater written using the ASM library [http://www.megaupload.com/?d=N7WO3EDC here].
| |
| − |
| |
| − | * '''Developing and maintaining the scripting API.'''
| |
| − | ** Self-explanatory. See “Scripting API Javadoc” under Links.
| |
| − |
| |
| − | * '''Developing the bot'''
| |
| − | ** Working on features like world-wide walking algorithms (so a script can walk from anywhere to anywhere else in the game world with just a few lines of code), usage statistic reports to the server, etc.
| |
| − |
| |
| − | * '''Writing scripts'''.
| |
| − | ** Although there are tons of other people writing scripts, it is important for capable developers that end-users recognize to create scripts that they know will be flawless and reliable.
| |
