RSPeer uses less resources than any other bot on the market due to our advanced injection techniques and proprietary interaction. Scripters can use any external libraries they please to on local scripts, or many of our approved libraries for repository scripts. We allow developers to fully express their scripting abilities by imposing minimal restrictions on scripts. Increasing the speed and efficiency of scripts ten-fold, while completely removing the possibly of your script being stuck. This is due to our proprietary interaction system that can interact with in-game entities without looking for their model. Replace id in the query string with the launcher id retrieved from the get launchers call.See what makes RSPeer superior to other botting clients. Helpful Routes Here is a list of helpful routes that you can use. Getting A List Of Script Orders You can get a list of orders to know whether your client instances or script instances are about to run out. Each order object will look like this: You can calculate the expiration of your order by taking expirationInMinutes on the item object and adding it to the timestamp. Getting A List Of Orders You can get a list of orders to know whether your client instances or script instances are about to run out. Automatically Purchasing Instances You can automatically purchase instances if yours are about to expire, providing that you have the valid token amount. Automating The Bot Management Panel You can utilize the infastructure of the bot management panel to automatically launch clients on remote computers. You can verify if there is a line break by opening the file in your favorite text editor and seeing if there are any new lines. The file must only contain the key and nothing else. Fortunately, you can do this automatically with the steps below: Locate the RSPeer cache folder. Are you interested in creating a bot farm but want to automate it as much as possible?Īutomatically Logging Into The Client If you are programmatically setting up a new computer and have not logged in yet, RSPeer will require you to login so it can authenticate who you are.
The default for almost every item is 30 daysbut we recommend you calculate it using expirationInMinutes. You can calculate the expiration of your order by taking expirationInMinutes on the item object and adding it to the timestamp. You can get a list of orders to know whether your client instances or script instances are about to run out. You can automatically purchase instances if yours are about to expire, providing that you have the valid token amount.
This will include any running client, even if you did not launch them from the bot management panel. You can copy these requests and replace the session with your api client key. All of these requests can be seen by opening the Chrome Dev Tools and viewing the network requests when starting a client on the bot management panel. This will be different for each launcher you have connected. You can utilize the infastructure of the bot management panel to automatically launch clients on remote computers. Once you have written to that file, start up the client. If you are programmatically setting up a new computer and have not logged in yet, RSPeer will require you to login so it can authenticate who you are. It is recommended to store locally the version of the current jar you have and then checking that version against the current live version to verify if you are on latest.