Maxi

Correct.

With the conventional methods of injection/reflection it does not matter.

Also, technically speaking the mirror client is injection based as well. The way it's done though is completely different than what any other bot does. Both conventional ways of injection and reflection are detectable with Jagex's current system. What the mirror client does is the same principle, but could say that it does a better job at hiding what it does. Combined with the fact that the OSRS client is actually ran from the browser, this must bypass some of their triggers. And yes, OSBuddy uses injection but Jagex can pretty much identify specific bot/injection/reflection clients with their techniques. OSBuddy makes no effort to hide what they are as Jagex knows it's not a bot client and won't flag these users as bot users.

Don't forget that Jagex tracks you through the random.dat file. If you haven't deleted your random.dat file, even on a new account that is only used on the mirror client, they can still relate that account to your previous accounts. It's also possible they have more tricks like these on their sleeves with their cache. Deleting both your cache and your random.dat is a smart move and might make a difference when starting a new account. Edit: The random.dat is a file that contains a UID (Unique Identification Number). This file is set by Jagex and related to all the accounts you play from that one computer. It is assumed that Jagex does not ban based on your IP but based on this UID. What we should do in the future, is write a tool that makes the OSRS client use a different random.dat (spoofed) file for each account to make sure accounts are not linked to each other through the random.dat file. This should definitely make a difference when it comes to their tracking system when making new accounts.

We don't give out ETA's.

In general is should not cause problems unless a scripter committed errors. Yes.

Dear community, This patch contains the following change list: - @Maxi -- Fixed issue with bank#getItemCountForTab, fixing multiple issues with banking -- Made doorhandler handle obstacle methods to return a boolean of the interaction result -- Made the store methods return a boolean with the interaction result -- Added a fully functional hint arrow API, supporting location, npc and player hint arrows -- Added a failsafe to the WalkingEvent to hopefully stop the repetitive clicking of the same tile indefinitely -- Added a patch to the RS2Widget#getItems() method to return items that have an amount of 0 -- Changed the way the client authenticates with the server, something we tried doing to solve issues a minority of people are having with the "You need VIP to run multiple tabs" issue whilst not even running 1 tab -- Fixed a NPE in Widgets#isVisible(RS2Widget[] widgets) I'll update the javadocs in a bit. Also, I have forced all SDN scripts to be recompiled, some scripts did not compile and returned errors. This will require scripters to fix their compile errors. Last thing, I've noticed how the WorldHopper doesn't function properly on the obfuscated client, but does work properly on the non obfuscated client. We will have to find the source of this issue, but it will get patched this week. Regards, The OSBot team P.S. The server needs a restart, give it 5 minutes before it is restarted. Until then, the client will not load / inject properly. P.P.S. Server was restarted, the bot should be useable now.

RS is capped at 50 FPS.

Or make a bug report. Without proper bug reports issues like you are having will not get fixed.

Not just this week.

Credits added .

Have you allocated enough memory in the boot loader advanced tab?

Dear community, This update contains a tiny patch for dialogues. Dialogues will no longer send the enter key after sending the numboard or spacebar key. Credits to @Czar for pointing this out. Regards, The OSBot team

Having only used the mirror client and deleting your random.dat before you start using the new account will greatly improve your chance of not getting banned. Users who have created new accounts with fresh random.dat files have proven to avoid the ban hammer with great near perfect succes.

Because the mirror client uses the what you call the 'main' bot. The mirror client is simply a different loading interface on top of the normal OSBot client core, it uses the same API and core functions. The mirror client is being worked on and this is the last post we make about it. The mirror client is not a feature/advertised feature for VIP yet, so please be patient for the update and act nice.

Merchant scripts, flipping scripts.

The Mirror Client is still in BETA and being developed. It is not a promised/featured part of the VIP package yet so please be patient for the update. Posts like these will only agitate the developers.

This will be addressed in 2.3.47.

This issue is addressed in 2.3.47.

We'll investigate it. Can we get confirmation of this being fixed in 2.3.46?

Did you really have to post that three times? Anyways, the code in the OSBot client is verified to be working correctly. Scripts might need an update, however this code works fine at the range guild if (dialogues.isPendingOption()) { dialogues.selectOption(1); // click the first option in the dialogue. } if (dialogues.isPendingContinuation()) { dialogues.clickContinue(); }

I'll check it out. Hmmm: code: if (dialogues.isPendingOption()) { dialogues.selectOption(1); } Please note that the first choice index is 1 now. Edit: read this http://osbot.org/forum/topic/67995-dialogues-please-read/

We have but they are undocumented and not ready for use yet. Alek will finish this soon hopefully. It will be when it will be. Remember that the mirror client is still in BETA and is not a advertised feature yet in the VIP package. The update comes not only with updated hooks but several bugs and performance boosts, at this point these things have to be finished to be able to update the mirror client.

The mirror client is separate from the OSBot client. An update for the mirror client will appear in its own section.

Dear community, With this update comes the following change list: - @Maxi -- Patched Dialogue API to work with the new OSRS dialogue system. It now uses the keyboard (space bar and numboard keys) to interact. -- Patched a bug with the InteractionEvent pointed out by @Khaleesi, thank you for writing a detailed bug report -- The widget system has been given a decent performance boost -- Various parts of the mouse events have been changed to allow for more failsafes Script writers, please read this and update your scripts accordingly: http://osbot.org/forum/topic/67995-dialogues-please-read/ Regards, The OSBot team P.S. Some users running in to problems starting the boot loader might have to delete their store.dat in their OSBot folder. This is likely the case for most users. TL;DR = Delete your store.dat in your OSBot folder (sorry for the inconvenience, this will make force you to saves your accounts and settings again)