Maxi

NullPointerException in your drawTile method in Core at line 92.

This must be a mistake. I've forwarded this to MGI.

Please report in the mirror client section. This is a mirror client related issue.

Dear community, We are slowly making progress in getting rid of the last bugs in the new widget system. There was one particular bug at a very low level that made the widget system perform in a rather unexpected way but this should now be fixed as well. Changelog: -@Alek -- New boot loader GUI -@Maxi -- New widget caching system for API modules - improves overall CPU usage -- DepositBox / Trade / Banking offer / remove / withdraw / deposit X functions have been patched -- DepositBox + Banking have been converted to use the new widget system for slot destinations -- Widget interactions should perform correct now due a bug with isVisible() being patched causing problems with all kinds of mouse and interaction events -- Various other bug fixes related to the new widget system -@Zach -- Various fixes for the above. NOTE: The Mirror option is ONLY available to VIP, Sponsors, Scripters and staff. Sincerely, The OSBot team

Was this fixed for all of you? If so please let us know so I can close and move this to the archive.

Download the latest mirrorclient.jar here: http://osbot.org/forum/topic/66800-osbot-mirror-client-your-guide/

http://osbot.org/forum/topic/66800-osbot-mirror-client-your-guide/ Download the latest mirrorclient.java there

http://osbot.org/forum/topic/66800-osbot-mirror-client-your-guide/ Download the latest mirrorclient.jar there.

Quoted from: http://osbot.org/forum/topic/66338-reducing-banning-rates-behind-the-scenes-at-osbot-27-febuary-2015/ Mac is supported now

Dear community, We are happy to announce the release of the Mirror Client technology written by @MGI. You can read about the Mirror Client here: Article on Mirror Client and ban rates. This feature will be available for VIP, staff and scripters. You can read how to use it here: OSBot Mirror Client Guide Also there were various little patches regarding widgets in this update. NOTE: Do not post errors related to the Mirror Client here but post in the designated forum section here: Mirror Client Bug Report Section Make sure you read the rules here: Article on Mirror Client and ban rates. Sincerely, The OSBot team

That doesn't matter at all, both instances of bank are the same. widgets is an API instance like all other API instance containing references to other API instances. Major change should be RS2Interface/RS2InterfaceChild -> RS2Widget && MethodProvider.interface.blabla -> MethodProvider.widgets.blabla

There is no need to do widgets.bank, it is the same instance as bank. That code will of course not work, because at the moment the interact method returns the interface is not open so the code between the while block is never executed. pseudo code if booth.interact("Bank") { // wait for the bank to be open new ConditionalSleep... { boolean { return bank.isOpen } }.sleep // perform banking logic here if (logic performed correctly) { close bank conditional sleep to make sure bank is closed continue what you want to do } There is a method in the API to open banks, you know that right?This is the actual code: /** * Searches for the best bank, based on type and distance from player. This * method will only interact with RS2Objects. * * @return If bank was already open, or opened successfully. */ public boolean open() throws InterruptedException { if (isOpen()) return true; final RS2Object bankObject = bot.getMethods().objects.closest( new NameFilter<RS2Object>("Bank booth", "Bank chest"), new ActionFilter<RS2Object>("Bank", "Use")); if (bankObject != null && map.canReach(bankObject)) { Event event = new InteractionEvent(bankObject, "Bank", "Use"); execute(event); if (event.hasFinished()) { return new ConditionalSleep(5000) { @Override public boolean condition() throws InterruptedException { return isOpen(); } }.sleep(); } } return isOpen(); }

I don't see why not. I've been running a NON ported script that runs fine, banking, interacting etc.

Go ahead and do what you what I can't stop you from doing. We are doing necessary maintenance that all scripters were aware of ahead of time. I have spent 36 hours straight in mitigation of the issues that occurred as I couldn't foresee all of them with over a 100 classes changed, partially rewritten in an effort to not break scripts. The other option was to just not try port the old to the new system and force all the scripts to be broken and wait for the script writers to update. Customer is always important, but don't take it too far calling bullshit. This is not a help thread. Please post in the correct section of the forums with programming related questions.

You are not being ignored. If you haven't noticed we are in the middle of a big transition between two systems whilst trying to minimise damage.

Dear community, This update contains further patches to the port between the old and the new interface system. I would like to point out that we should all encourage scripters to update their scripts to the new system. We are doing our best to make sure the old system will work as it used to however in some cases we won't be able to do so. Also there is a temporary widget explorer available again. R stand for root, - is second level and -- is third level id. Any reports are welcome. Sincerely, The OSBot team

Guys, the point is to get RID of interfaces. So get your scripts updated! In the meanwhile I'll be working my ass of to see if I can minimise damage by checking out bugs and see if I can make a quick fix for it.

Keep them reports coming, I'll patch them as I go.

Yes dialogues require some optimisations with the new widget system. They will get optimised during this or next week. On another note, API javadocs have been updated.

Dear community, With the new widget system affecting a large area of our code it was inevitable there would occur performance issues. I have profiled the bot and applied a first set of optimisations. I know there are more optimisations to be done on the new system, but this should already make a big difference. Scripts might spike a little cpu usage on start up when the system caches some data. If you still experience issues with performance, please report in detail so I can investigate and optimise further. Your help is appreciated. I will upload the javadocs shortly after. Sincerely, The OSBot team Edit: API java docs have been updated. A packaged version of the docs to use in your IDE's can be found here: https://osbot.org/api/javadocs.zip

I have found the source of the issue. I will upload a new version asap.

I will profile the bot for the issue with interactions. I have now experienced it myself as well. Due to the nature of the size of these updates it might have affected something unnoticed. I'll report on my findings asap.

The issue is with the script. Some scripts were affected by the changes in v2.3.34. These scripts will have to be updated in order to function properly again. Report on the script thread of the specific script(s).

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.