[arbiter]

Introduction​

The cat-and-mouse-game between our friends at the Jagex Game Studio and RuneScape botting clients is an age old tale. Today I am happy to announce our initiative aimed to secure a comfortable lead in the arms race for the foreseeable future: RuneMate Spectre.

The intention of this project is to architect and implement a new process flow for how the bot client will access and play our favorite game with a focus in making it indistinguishable from a legitimate player for years to come. This will be a drastic divergence from the stale patterns that all botting clients currently employ, leading to a more long-term solution and a steep barrier to detection. We will be leveraging cutting edge technologies that have previously never been utilized in this scene with the expectation of creating the new standard for the next generation of botting.

While this is primarily an internal change to permanently thwart client detection attempts, it has widespread implications that will also give us the opportunity to provide you with awesome new features, free of charge.

Phases​

Phase A: Aimed to provide a stable implementation of the new process flow with completed internal changes. Release will have a similar user experience and feature set to what currently exists.

Phase B: Will leverage the new process flow to provide features previously not possible, both at a user and developer level. Includes a redesigned user interface.

Phase C: Further feature releases with a focus on remote access and bot management.

Note: Phase A will be a bulk update due to its internal nature, while Phases B & C will follow the typical release cycle of incremental updates.

Dev Updates​

Phase A Dev Update​

As promised, here is the development update on RuneMate 2.0 Spectre. We began from scratch with a new code base and code repository, making sure that we can take this opportunity to review and optimize every part of the application. So far the core of the project is in late stages of development. There are several more tasks that need to be done before the objectives of Spectre will have been met, but we're well on our way.

Unfortunately due to how drastic of a paradigm shift Spectre is, a large portion of the API's internals are going to need to be rewritten which may introduce some delays although I'm not going to jump the gun and say that we need more time just yet. In addition to that, the current structure of the API may not be optimal performance wise so we're considering introducing an optional new API that would better utilize the core (post-release).

One of the new features that will be made possible by Spectre is "tabbed botting", although not quite in the way you may be used to. Multiple bots can be controlled from the same management interface, separated by tabs. This should make it easier for our power users to control larger amount of bots at once. The reason "tabbed botting" is in quotes is because only the bots will be running in the tabs. The game itself will be running in separate, isolated Java virtual machines (JVMs). This method is analogous of how Google Chrome has a separate process for each browser tab allowing for blazing fast speeds.

Before anyone jumps to a conclusion about what Spectre really is, it is not a Java agent attached at startup like some of our competitors use. From our extensive evaluation of options we have found that detecting that method is far too easy for our taste. We're still using a form of reflection as we always have, although with our new approach we do have more flexibility than we did in the past.

tl;dr Spectre development is coming along well and although we had a few unexpected hurdles we think we're on schedule for a release at the end of the countdown. There are a couple time intensive tasks in regards to upgrading the API that could potentially delay it, but it's too soon for us to guess. Multiple bots can be ran on one JVM per bot manager and be able to be controlled through a tabbed interface while each instance of the game will run in its own JVM.

Final exams hit @Cloud and me harder than expected. We haven't been able to put in the hours we wanted to this week due to them and thus have to delay Spectre Phase A by a week. That being said, it'll give us the chance to pack more into the initial release without having to rush it so there's a silver lining. I hope you all are as excited about this as I am. Can't wait to show you guys what we've been working on.

Here's the situation folks. @Cloud and I set an insanely ambitious deadline on purpose so that we work crazy hard towards it. But as we usually do, we scope creeped, or increased the number of things we wanted to do. We basically combined Phase A and Phase B tasks into one since it turned out it was just easier to do simultaneously. But there are only so many all-nighters one can pull in a row before the blurred vision kicks in, so it's time to take a step back and rest. I am extending the ETA by a few days in which we can both get some shut-eye and wrap up the last few loose ends. I will try to collect some statistics that explain the magnitude of this overhaul as well as get some teaser screenshots. In the meantime, happy holidays and happy botting!

@Cloud and I have to come clean about something: we intentionally set an impossible ETA, one we never could even dream of meeting. Why you may ask? Like many of you, we perform at our best when we're under extreme amounts of pressure. It's what allows us to be full-time students, full-time programmers/engineers, full-time business owners, and full-time RuneMates all at the same time. A few short weeks ago we set out to overhaul the 62,746 line application we all love and know as RuneMate 1.0 in order to pioneer the unexplored future of botting. The changes affected every facet of the application from how we access the RuneScape client to the design of the user interface. We initially had a multi-phase timeline, as posted in the original post, but the paradigm shift affected too many things and as such we had to combine Phase A and B to avoid redundant work. As such, we had to postpone the ETA to reflect the increased scope. However, in our haste and optimism we did not give ourselves enough of an extension to deal with the added objectives and that is where we are now. To prevent making that mistake again, we have withdrawn the ETA in order to properly assess how long it will take us to wrap up Spectre as well as spend some time with our families this holiday season. With three consecutive all-nighters working on this with @Cloud, we have been neglecting both our health and our loved ones. Spectre was well-engineered. Spectre is an inevitability. Spectre will be the new gold standard. It just won't be today, and that's okay.

A little teaser as promised. More to come soon.

What's Spotify guys?

Spectre video:

Since people have been complaining about the lack of any 'proof' that Spectre is as close to release as we say it is, here's a quick video to showcase it:

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

RuneMate Spectre is officially in closed beta with all Bot Authors getting automatic access to it. They are hard at work patching up your favorites bots so there is no downtime when Spectre is publicly released.

 

[aria]

2spooky

 

[defeat3d]

my name's bond

 

[srpronto]

"Soon TM" Jk, i know you will bring it as fast as possible. @Cloud and @Arbiter what a massive beast duo you are.

 

[yubibotter]

I don't even bot but I must admit Remote Access is a long overdue feature, definitely looking forward to seeing that.

 

[red]

*cough* get rid of JFX

 

[insomniac]

I hope it's not just a fancy name, but some real shit going on. Either way, Arbiter and Cloud will deliver asap.

What happens when you put a random bengali dude with a mysterious guy no one knows shit about? Well, you get executives of RuneMate: @Arbiter & @Cloud

 

[philosobyte]

Sounds exactly like what the botting scene has always needed.
Not going to say "excellent work" since we haven't seen the work yet, but we can say "excellent idea" This showcases once more your forward thinking and talent.

 

[cloud]

*cough* get rid of JFX

no.

 

[czcompl]

any idea? desktop bot management console?
it will make us easy to manage all bot account haha

 

[red]

no.

cloud y u mek me kry

 

[derk]

*cough* get rid of JFX

Lel you're just asking to get raped.

OT: Very nice, but the schedule does seem very short (time-wise). How are you going to pull it off?

 

[savior]

tight name bro

 

[arbiter]

Lel you're just asking to get raped.

OT: Very nice, but the schedule does seem very short (time-wise). How are you going to pull it off?

With mind-numbingly long days.

 

[jesse]

With mind-numbingly long days.

At least you're doing something you enjoy for people who appreciate you.

Try setting up festival hire. Working 14 hour days $15/Hour so some sweaty drugged up cunt can jump around in a tent to *doof doof doof*

 

[bonecode]

I notice you used a lot of meaningless words, so in all it may sound good but it makes no sense. You always imply how unintelligent I am (even though I am almost right more often than you) so could you please explain this as if you were talking to a five year old (I am 6 but I just wanna make sure there are no new words I havent't learned yet)

Here are some things to simplify:

What the heck is a 'process flow' and how the heck does it effect ban rates.

"making it indistinguishable from a legitimate player for years to come" there are currently a lot of ways to tell a bot from a legitimate player mainly through actual java use and not through the way a bot plays a game (as all truthful developers will say player a game a certain way with certain mouse movements, camera changes etc will not lead to a ban) so in short, does this intend to do it on that side too or just make cleyboard aswell?

"stale patterns that all botting clients currently employ" hard to say when the other bots weren't detected in a long time.

"We will be leveraging cutting edge technologies" what cutting edge technology? and I assume it has been 'leveraged' somewhere else as you specifically said it hasn't been used in "this scene" therefore it has been used somewhere else, where? and does jagex have access to this technology?

"Includes a redesigned user interface." hopefully with swing amirite?



EDIT: Also I know how you like to ban me for pointing out the truth of things, so please don't ban me like a child and come up with a good response (i hope!)

 

[basedbotter]

I notice you used a lot of meaningless words, so in all it may sound good but it makes no sense. You always imply how unintelligent I am (even though I am almost right more often than you) so could you please explain this as if you were talking to a five year old (I am 6 but I just wanna make sure there are no new words I havent't learned yet)

Here are some things to simplify:

What the heck is a 'process flow' and how the heck does it effect ban rates.

"making it indistinguishable from a legitimate player for years to come" there are currently a lot of ways to tell a bot from a legitimate player mainly through actual java use and not through the way a bot plays a game (as all truthful developers will say player a game a certain way with certain mouse movements, camera changes etc will not lead to a ban) so in short, does this intend to do it on that side too or just make cleyboard aswell?

"stale patterns that all botting clients currently employ" hard to say when the other bots weren't detected in a long time.

"We will be leveraging cutting edge technologies" what cutting edge technology? and I assume it has been 'leveraged' somewhere else as you specifically said it hasn't been used in "this scene" therefore it has been used somewhere else, where? and does jagex have access to this technology?

"Includes a redesigned user interface." hopefully with swing amirite?



EDIT: Also I know how you like to ban me for pointing out the truth of things, so please don't ban me like a child and come up with a good response (i hope!)

Maybe if you conducted yourself in a mature fashion you would not be banned so frequently?

 

[bonecode]

Maybe if you conducted yourself in a mature fashion you would not be banned so frequently?

If you saw the things I got banned over you'd change your statement quickly.

http://i.imgur.com/5gwWFrj.png related to the ban received for posting "If it uses a lot of resources (which it does) computers that aren't capable (ur free one) have trouble running it." just as an example

 

[derk]

If you saw the things I got banned over you'd change your statement quickly.

http://i.imgur.com/5gwWFrj.png related to the ban received for posting "If it uses a lot of resources (which it does) computers that aren't capable (ur free one) have trouble running it." just as an example

I hope you realize that not only that is the motivation behind your ban. Obviously there's been a history of toxicity and general misbehavior.

OT: I'm sure he's using "vague" words to avoid spilling the exact beans so that Jagex isn't 100% ready to counter when it's done.

 

[arbiter]

I notice you used a lot of meaningless words

Just because it is beyond your limited vocabulary, it doesn't mean it is meaningless. I encourage you to expand your diction by looking up the words you don't understand. Feel free to verify my application while you observe it applied in a sentence kindly provided by me.

even though I am almost right more often than you

Lol... no comment.

What the heck is a 'process flow' and how the heck does it effect ban rates.

A process flow (diagram) is the systems engineering parallel of an activity (diagram) as is commonly seen in UML and general computer science theory. Both terms were considered for clarity with end users and the more intuitive one selected. I will not spoonfeed you a definition but there are plenty of resources online to learn more about these including, but not limited to, Section 3.7.2 of the NASA Systems Engineering Handbook. In the particular context, the term refers to "how the bot client will access and play" as explicitly stated in the OP. Further details were intentionally excluded to protect against the wrong people gaining unnecessary insight.

not through the way a bot plays a game (as all truthful developers will say player a game a certain way with certain mouse movements, camera changes etc will not lead to a ban)

I am showing extreme restraint when I state that you are simply ill-informed. I suggest you re-evaluate your sources.

hard to say when the other bots weren't detected in a long time.

Agreed. The fact that the scene has survived with old methods for a long time is exactly why there hasn't been a motivation to move the technology in use forward. This is not the case today. While some opt to patch the immediate problems we have decided to go with a more involved long-term solution.

what cutting edge technology? and I assume it has been 'leveraged' somewhere else as you specifically said it hasn't been used in "this scene" therefore it has been used somewhere else, where? and does jagex have access to this technology?

Any omission of details is intentional as previously mentioned.

hopefully with swing amirite?

This is why you get banned.

---

This is the last time I will entertain anything you have to say. I dislike your attitude and personality as I have clearly expressed before. I kindly request that you do not attempt to interact with me moving forward.