Maxi

The SDN issues should be resolved. Please report on this thread if it still persists. Remember to restart your clients if you were facing SDN problems earlier. Thanks to @Zach for his help.

Dear community, We are aware of the issue with the script loader. The issue arises from the update to Java 8, which for some reason causes some scripts to not get packed completely by the server. This is most likely due to the update to Java 8 which (for who knows what reason) caused a race condition in the SDN compiler. We have narrowed the possible solutions down and we will have to try each one of them until we find the one that fixes it. We are sorry for the inconvenience but let us reassure that the issue is not being ignored, this is a very important matter to both you and us. Sincerely, The OSBot staff

I'm impressed.

Dear community, Today our server faced something we would have expected the least; failure of two SSD hard drives. Unfortunately the hosting company responded very slow on this occasion but @Zach worked very hard to get everything back up and running. The hardware was replaced with new hardware and the server was re-installed. Our back-ups were pretty much up to date, we might have only lost a couple of hours of the database. What did we learn from this? Don't rely on SSD's not breaking down, have multiple backups available. If you have lost posts or threads you made in those couple of hours between our last back-up and the server failure, please repost yours if important. If you forgot what you post in your thread you could use Google's webcache for example. We are very sorry for your inconvenience and are happy we can shrug of the stress this brought with it today. The bot server is back online as well as the forums. Various parts of the website / server are not working as they should yet, this will get straightened out over the next few hours. If you encounter any problems or issues, please report them. NOTE: The bot server is still being configured, this means that for some it will work, for others it won't. This should be resolved shortly as we are working on it. -Thanks to @Dex for notifying @Maldesto. -Thanks to @Maldesto for notifying @Zach and me. -And last but not least, thanks to @Zach for the work done on the server. Sincerely, The OSBot team

Mirror Client mode does perform injection. It does it in a different way though which results in any injection performed not being visible on the level of the JVM, thus bypassing the injection detection systems used by the OSRS client.

One of the things we could do is the Mirror Client mode, which bypasses this detection. We have several other ideas that could bring performance back to the same as the standard mode, but we will have to experiment with that in the future.

Actually the improvements have been made, but were not included in the weekend release. Reason for this is that we wanted to make sure there are no bugs in it.

Please post in the correct section.

There is proof of client level detection systems. It's their server though who flags it as a modified client and determines what specific client it is though. But the data to be able to do so is collected client sided and send to their server. There are multiple ways within that system that could lead to detection, simply bypassing it not something that is easily done. To answer your other question: there most likely multiple reasons why they don't instant ban all bots. One of them could be that they need information to feed their machine learning systems a.k.a. Bot Watch. Another reason could be how the economy would crash if they would ban all bots at the same time. Another could be a strategy to get players to play legit again. Making them loose accounts that have build up things might still keep the players attached to the game but stay away from botting. I simply wouldn't know what their motives are, this is all speculation, but what isn't speculation is the fact that they can detect most bots on a client level (all regular injection / reflection bots, Mirror Client is injection with an entirely different story though).

No.

The Mirror Client uses injection but done completely different than what the botting scene has seen so far. Let's just say it does a way better job at hiding its presence. In fact, the injection can't be seen with their current client. It does two things, it hides its injection for their client level detection systems and leaves the OSRS client in its original execution environment.

Yes they can detect most bot clients and identify them specifically. But if injected in the right way, it becomes way harder to detect at the client level. The Mirror Client mode on OSBot does that and proves that many bans are based on client detection for the biggest part, seeing as how much lower the banning rates are on the Mirror mode. The standard mode on OSBot is similar to the injection methods most other bots use and comes with a higher ban rate. You can read about our thoughts on their detection system in the thread I posted about reducing ban rates in the main announcement section. @ person above me: They gather information for their machine learning systems. Just logging in a bot client won't get you banned as their detection system is not solely based on client detection, but probably also on gains (xp, wealth etc) and behavioural patterns learned by their machine learning systems. It may get you banned though by just logging in alone. Like I already said, I think the mirror client proves the point. Besides that, they have publicly admitted they can identify most main stream bigger bots specifically. As a developer I know why and how they do it.

The mirror client mode compromises CPU and memory resources for less detectability. Results have shown that the mirror client greatly improves your chances of not getting banned. In the future we will be able to bring the difference down by a lot, but this will take time.

It's just best practice not to provoke or wake up sleeping dogs.

Not mine, but thought it would be nice to share:

I saw someone sharing this, pretty impressive:

Update your java.

There is a guide. Read it.;)

There will be a warriors guilds script that's free for VIP's, I will probably have it ready for testing by the end of this week. Also a Bandits script will be released, I still have a private one laying around that I used for myself a long time ago but it still works.

Edit: http://osbot.org/forum/topic/68899-mirrorclient-v1052/#entry760314 Download the latest version of the mirror client. When the mirror client gets out of BETA the mirror client won't be a separate download anymore and will be automatically updated. For now each OSRS update you will have to download the newest mirror client when once it has been patched.

Dear community, Some really old legacy code in our updater, which amazingly lasted 2 years before it broke, broke today on OSRS update #76. I've patched it and you can all return to your bots. Happy botting! Regards, The OSBot team P.S. Users of the Mirror Client - don't forget to update your mirror client.jar here: http://osbot.org/forum/topic/68899-mirrorclient-v1052/#entry760314

Request a good script writer to make one, he will if there is enough market.

Dear community, Some time this week we will release an update that will give the client a nice performance boost, especially when interacting with entities. Today I have rewritten the model triangularization, which gave a nice boost to the mouse movements. There is another part though, the part where the mouse movements for entities are evaluated which requires an overhaul. Without it the gains gained by the first part I did today are still useless as the second part is a rather large bottleneck. On top of that, we will introduce overal performance on accessing most entity types. Overall this should boost OSBot's performance in terms of speed and also CPU and memory usage spikes. These should also give a noticeable performance boost to the mirror client mode. Regards, The OSBot team

They ban IP's but not based on the actual IP. They ban the ip's based on the uid in the random.dat file. It helps them track accounts that are related to each other. They then used that information to ban ip's and accounts.

All we can do is make assumptions based on logical thinking. If we stick with the tier system, it's likely that they have all sorts of monitor detail levels where the higher level tiers use more computational resources and therefore only used for a very small group of characters. In general, the first tier will most likely be things like hours of play time, break times and activity. This costs very little resources to track and compute. For example, a new account, that is playing 10 hours a day doing only activities that have a very high banrate, no quests or talking etc. Second level tier might then actually compare behaviour of the activities. Imagine a woodcutting script that performs the same actions in the same order: bank, walk to first tree, chop first tree, walk to second tree, chop second tree, walk to third tree, chop third tree, eat rinse and repeat. Anti-ban is only checked between certain actions, making that an easy to detect pattern as well. Then when a bird nest appears, it will immediately grab it. When a tree spirit appears or an ent, it will immediately react to it. Normal players tend to perform their actions by a similar pattern. But these patterns are different every once in a while and most certainly will be different from other players. The key in making scripts less detectable is breaking patterns but also trying to achieve a certain difference between different players based on a profile. The more difference there is between two players using two scripts, the less likely it is their machine learning technology is able to identify another player using the same script as using that same script. But then again, it is possible that once you get in to a higher level tier, they start creating profiles based on mouse movements. These profiles can be compared and identified as similar. So that means there is definitely work on our side to be done as well to make key elements of our bot perform different for each player as well, like mouse, keyboard and interactions. I think if both parties can improve on this, together with the mirror client, we might make a jump ahead in the cat and mouse game on which we have been behind for some time now.