Regarding mirror clients

[arm2]

So it's basically color/reflection without loading RS into a custom client? Is it possible to do other methods, such as Injection or OGL/DX interception in much the same way?

Yes, that was the first way someone did OGL iirc and osbots mirror is still using injection.

 

[Rawr12345]

Obviously there is some level of hostility here. I understand a lot of people think its a ploy, and maybe it is.

It can be debated whether or not Jagex bases any bans off of detecting clients. They say they aren't, so its probably a non-issue. But Jagex aren't really known for sticking to their word, so excuse me if I prefer not obviously displaying to Jagex what client I'm using.

My description was accurate. If you think the only point of reflection is to have 2 windows open you've clearly missed the point.






RiD is/was color based, so essentially the same benefit. You're running the bot on top of an official client, so Jagex isn't able to detect based on the client you're running.

Same goes for Simba/Smart, it uses reflection.

I know what reflection is. Sorry but your description of mirror mode is off

 

[Darkest Dream]

I know what reflection is. Sorry but your description of mirror mode is off

My description is wholly accurate.

Detection of bots can be divided in two main strategies. The first strategy is detection on a low level, this means detection of the modified RS client. The second strategy is by analysing behaviour of players. Both can be extremely efficient at what they do. Combined they do a pretty good job, considering the banning rates some people are facing on any bot they use.

The first strategy is done by detecting whether the RS client that runs is modified or not and whether it is running in it's natural environment. The way current way most bots work is by downloading the RS client and modifying the client to be able to communicate information of the game with the bot engine. There are ways around it, but the way RS currently has their system set up means that battling their strategies to detect bots on a code level are meant to break and would require a lot of updating. Basically using a bot these days or for example RSBuddy (a runescape helper, not a bot) just plain out tell RS that they are bots.

The second strategy is behavioural analysis. By having intelligent systems that compare behaviour of players/bots and compare it to statistics they have of players that are proven to be bots, they spin an entire web of intelligence that could recognise bots. This they can't obviously do for every player, so they most likely have different monitor levels, where each level higher means that the behaviour is analysed in more detail.

Those two strategies are then probably combined, where the first strategy is probably the main flagging system to be upgraded to monitor tier 1. Monitor tier 1 then monitors on a global big picture view. Botting times, activities, quests being done, experience gain, trading activity etc. If monitor tier 1 suspects suspicious behaviour, your account will be moved in to monitor tier 2 which might analyse mouse behaviour or other more in depth and resource intensive analysis. From there there might be more tiers until you get banned. This of course is speculation.

Having good scripts does lower the chance on detection by a lot. Changing scripts, having different behaviour on the same scripts by two different users, intelligent and human like action etc can all make a difference. But these won't make a difference if a bot basically says it's a bot based on a technical level of the code.

So what is the solution? The theoretical solution seems simple. Come up with an idea that has no possible detection on a code based level. The implementation of it however is far from easy. Now to the interesting part: MGI has been working on an idea conceived several months ago and is nearing its completion. We call it the mirror system. The mirror system should tackle strategy one completely.

MGI called this feature the Client Mirror System. It leaves NO trace in the RS client of our bot and is by no means visible on the JVM. The RS client runs in its own environment which makes it even better. You still have all the controls you had in the past. This could potentially knock out the initial flagging system that takes your account in to monitoring. We don't know for sure how their system works though, but this completely diminishes the detection on a code level base.

This feature does require additional CPU, so the future will have to show how much of an impact it will have if you use this for big bot farms. We will however provide you with the option to use the old injection system or the new Client Mirror System and they will be able to be used in a mixed fashion if you prefer. In any way, the performance overhead might be worth it for everyone in the end.

Work is still being done on finishing the entire feature including optimizations.

 

[arm2]

My description is wholly accurate.

You believe something posts by an OSBot dev? My God...

 

[Trent!]

Another question, do mirror clients take over the mouse, or do they simulate the mouse like previous methods?

 

[scrubsickle]

Mirror clients are bs.

 

[Darkest Dream]

You believe something posts by an OSBot dev? My God...

Whether or not Osbot is a true mirror (I've been told it isn't) is irrelevant.

That's how a true mirror client works, if you think the point is just to open 2 windows smfh.

Another question, do mirror clients take over the mouse, or do they simulate the mouse like previous methods?

Simulated, mouse runs on top of an official client.

 

[Rawr12345]

Whether or not Osbot is a true mirror (I've been told it isn't) is irrelevant.

That's how a true mirror client works, if you think the point is just to open 2 windows smfh.



Simulated, mouse runs on top of an official client.

Reflection and mirror mode are 2 completely different things.

 

[notoriouspp]

Another question, do mirror clients take over the mouse, or do they simulate the mouse like previous methods?

A "mirror" client is just a normal botting client, though instead of injecting hooks into a locally stored gamepack, they use the Sun Tools Attach library to attach a agent onto a running RS game instance.

In this particular case, they add a few things to the instance. A .dll which is used in combination with JNI to add a native method that allows them to grab remote classes from the game, a jar containing the API, and last but not least a injector jar. The injector jar uses that native method to grab all the classloaders for the running game instance for each class, and uses them to inject callbacks which point to their API.

So almost everything about the "mirror" client is just like a normal bot client in terms of how it works, just how it is loaded/injected is different.

I'm not saying the mirror client helps or that it doesn't. Just it seems like there is tons of misinformation floating around about how it works, and wanted to clear that up. If we all know how it works, we could all then make informed decisions as to if it is beneficial or not when it comes to bans.