2.95 - Reduced CPU Settings

Hey everyone, so the big topic of this update is the addition of options to reduce the cpu usage of RuneScape while you're botting. We wanted to make sure that the new settings we added would only improve your botting experience and wouldn't break any of your existing bots or increase your chances of getting banned. We also didn't want to implement a single "low cpu" mode, where you wouldn't really have any idea of what it's doing to result in lower cpu usage, nor did we want to stop rendering things that are important to the game and the way you (or rather your bot) interacts with it (which sadly is done by many other clients). This meant that we weren't going to just add an option to stop rendering players, npcs, objects, or any other scene entity because then you wouldn't be able to interact with them.

We ended up adding two options to reduce your cpu usage, with more coming in the future if people aren't satisfied with the crazy reductions in cpu usage that are capable of being achieved depending on what you set their values too.



By default, RuneScape runs at 50 frames per second. This is a reasonable cap when your playing the game yourself, but when you're botting rendering 50 frames per second is probably not necessary, especially when the game logic runs independently of the rendering logic. By allowing you to set a value of anywhere between 1 and 50 FPS for your game to run at, you can reduce your cpu usage down to just a small fraction of what the game was using before. And reducing the frame rate doesn't impact the botting experience in any way at all since the game's logic and your bots continue to interact with the game at a smooth 50 cycles per second.

The next way we managed to reduce cpu usage for you is by allowing you the option to remove the scenic floors that are displayed as a backdrop when you're in the upper floors of buildings of castles, that look nice but aren't intractable and are only a waste of cpu cycles when you're not staring at the game trying to enjoy it's graphical wonderland. If you enable this option, your game will go from

to a much less impressive looking

Now although it looks WAY different, everything that was removed from the scene wasn't able to be interacted with in any way. It was just being rendered to provide scenery and make for a less depressing landscape. The moment you go downstairs, all the scenery that you saw disappear when going up the stairs will immediately reappear.

Now by default, neither of these options are turned on. We want you to choose to use them, based on your needs and preferences. That's why you can choose to set a different framerate than the game defaults to based on your needs. If you only want to squeeze a little bit more performance out of your pc so you can run an additional bot, then maybe just lower the framerate to somewhere in the 30s. On the other hand, you could set it to 5 frames per second, and get the exact same gains as you would otherwise while being able to run quite a few more bots. Combine these options for best results. You won't be disappointed.

Other changes this update include

• Fixed "SpriteItem has name "Members object" in members world after world hopping in lobby " (github issue #4)
• Added WorldOverview#isSkillTotal2200
• Added a new HitsplatListener
• Fixed RS3 world hopping
• Added Camera.getJagZoom to determine how far zoomed in you are into OSRS. There will be a method named getZoom added in a future update once the RS3 zooming mechanics are understood and we're able to provide normalized data.
• Added a SoundEffects API

 

I must suggest that you try again, I am testing it right now and you can immediately see the fps adjust once you start running a bot.

 

@Luis Miguel @Gengsta
It turns out that the frame limiter was only being effectively applied when your viewport was set to resizable. This has been resolved in RuneMate V2.95.5 which is now available. I hope you find the results to be satisfactory