Maxi

You won't be able to load any version prior to 2.3.34 because the hooks were changed and are not compatible with those versions. Scripts that are broken by v2.3.34 and later will have to get patched by the script writers. They are aware of this and any scripts affected should get updated soon. If you're experiencing problems with scripts post on the script threads of the specific script and script developer.

Read first post.

Dear community, In this release a bug with banking that Mysteryy pointed out to me was fixed. It's regarding the issue where you withdraw multiple items consecutively it would fail after 3 or 4 items. This should be fixed now. Please report any bugs with a proper report in detail and we will review them. Sincerely, The OSBot team P.S. My internet is shit atm so the upload was corrupted. Please wait a couple of minutes and redownload the jar from the main page. P.S.S. Second attempt my internet did not fail. Download should work now.

I'm running a non ported script from Divinity right now and I can't reproduce this issue. There is some new caching going though with interfaces that might slow down things at the start. The benefit though is that the bot should use less CPU because the callback we used is gone. But if you could specify your issue in more detail instead of just saying this, I could maybe investigate your issue. Interacting should not be different except for with interfaces. Interacts smooth and fast for me here.

Dear community, This update took a while to round up. We have introduced a new interface system that gives full and correct access to all interfaces. We have called its class RS2Widget and its API can be accessed through the Script.widgets instance. The old system points to the new system and I hope we didn't break any scripts in the transformation, porting this wasn't easy as there are some major differences between the two systems. I can't say for sure that it has not broken any scripts. Never the less, the scripters will have to upgrade their scripts to use the new widget system, regardless of the fact whether this update affected their scripts. This update affected a rather large part of the client. It is possible that scripts using the old interface system possibly face problems. However the entire internal API is now mostly based on the new widget system. What is left of the interface system will get removed once there are no dependencies on the old system anymore in scripts on the SDN. Scripts that are broken by this update should be updated rather quickly as all developers have been notified of this update to come. I have also addressed the issues with banking. I haven't been able to reproduce any of the mentioned problems. However like I said, the scope of this release is so big that it is hard to say if we've missed something in the porting of the old interface system. So please report any bugs you come across with a detailed description of the bug and I will review them tomorrow. If everything is fine, I will rewrite the interface debugger to be useful again. This will most likely happen tomorrow or the day after. I will upload and update the javadocs af fast as possible for the script developers. I hope that you as a community understand that this might cause problems with certain scripts and I'm sure the script developers will update their scripts to the new system as soon as possible if this update affected their scripts. In that case we are sorry for your inconvenience. Sincerely, The OSBot team

Especially F2P accounts are very vulnerable if taken directly to a botting site.

There is an endless list how they could detect injection clients. Cookies is one of them, but could be spoofed. But there are many other ways on the client software level as well. We could infinitely work around all those measures one by one, but instead of that this would target most (if not all).

They won't require any changes. Only the interface to load the bot is changed, the engine of the bot remains the same. We are not saying that you won't get banned by using the new mirror system, but the way this is done will eliminate detectability on the local software level. I'm fairly sure the way this is done is different from what anyone has ever implemented.

Dear community, Prepare for a long but awesome read! I feel like giving you all an insight in what has been happening behind the scenes of OSBot lately and what is to come. We have been working hard in the last couple of months to get the bot back where it used to be in the summer/autumn days of 2013. Fixing issues with the API and the bot is one part of that. The other part exists of creating new innovations and adding new features to keep up with other bots or to make OSBot unique and innovative. These were things we were doing quite nicely back in the days and it's time to reclaim this glory. Many of you must have noticed that MGI was added to the team as a developer. With this promotion we also promised to find a solution for the high ban rates that we, but also other bots, are facing. Ban rates. 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. OSBot's new Client Mirror System. Before blabbing about all kinds of technical details here is a picture of what it looks like. A picture is worth a thousand words they say. 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. Other planned features. OSRS update handling. We will provide a system that will handle with OSRS updates. Once the bot recognises there is an update about to happen, it will log your account out or wait for the disconnection. After that it will wait for the new hooks to become available on the server and reboot the RS instance. The moment when this reboot happens will of course be randomised so that not all OSBot users log back in to the game at once. After the reboot the script will continue where it left of. Grand Exchange API. With the GE released we will be providing an API for scripters to use the GE. OSBot client chat. I have written a server module that will be able to route chat traffic to and from the server and supply it to the forum's IP.Chat module. Users will be able to chat with the people on the forums and vice versa. We hope this feature will increase traffic to the forums and give people something to do when they choose to baby sitting their bots. I hope you had an interesting read , Sincerely, The OSBot team UPDATE:

Dear community, For some reason our automatic server sided updater failed to run today. I have manually ran the updater and updated the server's hooks file. You should all be able to get back to your bots now. Sincerely, Maxi

It's back up now. Usually the updating happens automatically, but for some reason the automatic updater didn't fire today. I've manually updated the hooks, you should be good to go.

$100 and I won't ban you.

Re-download the jar. The jar initially got corrupted on the first upload, it had to be uploaded again. If you re-download it you're set to go ;).

Sorry, the upload failed. Wait a couple of minutes and try again.

Dear community, In this update I have patched issues with stacked ground items, items that are on a stack but not the first 3 items. I know this was fixed before, but last release reverted that fix but fixed another issue. I have now combined both fixes, with the stacked ground items fixed in a more fashionable way. The InteractionEvent should now have all use cases covered. If you encounter any bugs, please file a report in the correct forum section. In the coming days I will stop spamming your bots with update notifications :p. Please enjoy. Sincerely, The OSBot team

Ok now I have your attention, please vote for The StadsKas here: http://www.urbangreeners.com/vote/ VOTE FOR THE STADSKAS, SHARE WITH YOUR FRIENDS, MY FRIENDS ARE ETERNALLY GRATEFUL p.s. There is no $100 p.s.s. But my friends will absolutely love you and so will I

Members Online Today: 1914

Dear community, We got the following change list for this release: -@Maxi -- The DepositBox API was updated to use the XNodeContainer system, all should work properly again -- The InteractionEvent has received a tiny but very important patch, according to @Botre it's all good now -- WelcomeScreen has been patched @Deprecated - Entity.isOnScreen() > see isVisible() Sincerely, The OSBot team

I think Suarez will bite someone's head off.

Congratulations Basic on your new Veteran rank

The answer has already been given on the thread btw ;)

Nope. Nope. This year.

http://osbot.org/forum/topic/153-private-bot-beta-live/ http://osbot.org/forum/topic/351-public-bot-beta-live/

Very close. There were only 2 people and the idea to create the bot was conceived earlier.

Shit, @Oliver knows.