Maxi

Are you starting your script when logged in or do you start it when logged out? The current way things are done means that you should try to start the script whilst being logged out on a freshly loaded OSRS client preferably. Also, please post in the correct section next time. I'm leaving this here for a short while so you don't get lost.

Updated the OP with an extra line on how to use: 4. Make sure you are not logged in before starting your script. Preferably with a freshly loaded OSRS client.

It's the array of grand exchange boxes.

http://osbot.org/forum/topic/67260-has-anyone-been-banned-using-mirror-client/

You can use multiple tabs with the Mirror Client. Most scripts work fine with it now. Over the next few updates performance will be further improved and all scripts should work the same as on standard mode.

Please follow the guidelines and rules for reporting bugs ladies and gentlemen: http://osbot.org/forum/topic/67338-posting-bugs-format/

Our new Mirror Client seems to be doing a good job though, no reports of bans with it so far. It is in BETA testing stage still and still needs performance improvements and bug fixes.

I can't make you guys bot smart, but consider it stupid to bot 24/7. Read this: http://osbot.org/forum/topic/67517-do-not-test-detectability-by-botting-247/

This update contains a patch that was meant to be in the previous release but for some mysterious reason didn't make it to the final build. It should contain a fix for Widgets.isVisible(int rootId). Thanks @Zach and @Mysteryy. On another note, in the coming week you will see some newly introduced API classes and methods. I have hooked the following hooks for which API logic will be written: ------------------------------------------------------------------------ | Friend | -> name | -> world ------------------------------------------------------------------------ ------------------------------------------------------------------------ | Client | -> friends_list | -> friends_count | -> grand_exchange | -> world_count | -> world_array ------------------------------------------------------------------------ ------------------------------------------------------------------------ | PlayerDefinition | -> appearance ------------------------------------------------------------------------ ------------------------------------------------------------------------ | Player | -> skull_icon | -> prayer_icon | -> combat_level | -> definition | -> team ------------------------------------------------------------------------ ------------------------------------------------------------------------ | World | -> id | -> type | -> domain | -> activity | -> location_id | -> population | -> index ------------------------------------------------------------------------ ------------------------------------------------------------------------ | GrandExchangeBox | -> status | -> item_id | -> unit_price | -> amount_to_transfer | -> amount_transferred | -> spent ------------------------------------------------------------------------ Sincerely, The OSBot team

Dear community, Today we celebrate the two years existence of the OSBot forums. Exactly two years ago from now the forums were put online for the first time. In a few weeks from now the first release of the OSBot 1 BETA client was made two years ago and from there on the journey of OSBot started. Two years later and many faces have passed the revue, we are determined to get OSBot back to the top spot we once claimed in 2013/2014. Thank you all for being part of OSBot in good and bad times, it has certainly been a blast so far and may the future bring you glory. Happy birthday OSBot, a big thanks to all the developers and staff that have been working hard lately to get OSBot to the top spot again! Regards, The OSBot team

Click on mirror client.zip to download it. Then copy or move the file to your osbot folder.

Is this bug still prevalent in v1.03?

Is this bug still prevalent on v1.03?

Remember that we need more information on bugs. Please follow the rules so we can go by more information.

Make sure you are running compatible bit versions.

This should be fixed in v1.04 which will be released later on.

Is this still prevalent in v1.03 and the latest OSBot client version?

Allocate more memory in the booter GUI for the OSBot client. If you look closer at the picture you see that your OSBot client's memory is fully being used, when this happens the OSBot client will crash because it doesn't have access to enough memory.

Please follow the rules of posting bugs, we can't do anything with this bug report because it contains too little information.

Dear Mirror Client BETA users, I know it is a tempting idea to see how long you can bot for with the Mirror Client before getting banned but this idea is not smart. Eventually you will get banned if you bot 24/7, regardless of the detectability of the new technology behind the mirror client. This will just offer information to their machine learning system about detecting/identifying the bot, which in the long run will benefit nobody. Please bot smart, not 24/7, take breaks and enjoy. Sincerely, The OSBot team

No it's not worth it. Botting is about being smart. Getting yourself banned will just help/teach their system to identify new systems. This is not smart, because you know you will get banned botting 24/7, no living person on earth can do that.

Will be fixed on next update. This is not related to the Mirror Client but a bug in the general OSBot client.

http://osbot.org/forum/topic/67338-posting-bugs-format/ Please change the OP conform the rules.

Chances are that Jagex keeps a list of proxies and their ip ranges. Unless you have a proxy running on a domestic ip, proxying might not be that safe at all depending on your proxy host. But support will be there in the near future.

HOW TO REPORT BUGS: Please report! This feature is brand new and has only been tested by a couple of people. Therefore there might be problems that occur. A known problem is running a 64bit JVM for OSBot and a 32bit JVM for the OSRS client in your browser, you can't do this. But there are most likely more issues that will occur and we will need your reports to get those fixed! Reports missing the following will get ignored and deleted: Mirror client version Console output / terminal output Crash report if a crash occurred Script that you ran Hooks that failed JVM/Browser bit version (32 / 64)