MGI

fixed

Mirror mode does support dialogue interactions

Release notes (2.5): Many interface related bug fixes! Most scripts that weren't working should work without problems now. Loading messages are back (requires latest stable osbot version) Crashes in certain rare scenarios fixed Ability to disable the mirror mode text via Shift + F5 Other miscellaneous bug fixes. MAC/LINUX users please note: Mirror mode was originally designed for windows, and is optimized the most for it. And while it's now supported on OS X & LINUX - the performance of it is best when used on windows.

Release notes (2.2): Added support for OSBuddy, please use at your own risk. Miscellaneous bug fixes. MAC/LINUX users please note: Mirror mode was originally designed for windows, and is optimized the most for it. And while it's now supported on OS X & LINUX - the performance of it is best when used on windows.

It says what it says: login to the game and set your window mode to fixed in settings tab, use mirror afterwards. For the screen #1: try loading runescape via browser by going to http://oldschool1.runescape.com/

your os type/version?

was patched

How much credits do you want?

looking for something cheaper sorry

how much?

~70%+

Requirements: Lvl 30 EU east/west (or with enough RP for transfer) Has most champs

will check those methods

While we are working the best we can to squeeze every possible bit of performance (and compared to the first mirror release, current one uses 5+ times less cpu), the ability to access osrs client remotely (from another process) without injecting and loading bot code inside of it comes with a cost, whether small or not - it is unavoidable. What you can do to reduce amount of cpu it uses is press SHIFT+F2 and lower the fps to 20 or 10. Most scripts do not need high fps to run smoothly and reduced fps means reduced cpu usage.

Will be adding additional debug info on the next build regarding this issue.

I need steps to reproduce this bug

Changelog 2.4.43: Misc. webwalking fixes, including fix to http://osbot.org/api/org/osbot/rs07/api/webwalk/impl/CustomInteractingScript.html#install-boolean-org.osbot.rs07.api.map.Position-java.lang.String-java.lang.String:A-org.osbot.rs07.api.map.Position-org.osbot.rs07.api.map.Position- Improved certain anti-detection features. Now collects certain data from client to help us improve anti-detection features even more (Can be opted out in launcher's "About" tab). Other silent fixes.

fixed

I'm pretty sure i've fixed that bug so @czar, I need a confirmation that collision data is still not refreshing.

Are they?

was fixed

Attach to browser clients.

With reaction of 2000, it will take bot up to 2 seconds to notice that a new npc, object, etc has been spawned/died/etc. Fps setting affects other data refresh rate (such as opened interfaces, npc hp, etc). So with 50 fps, it will take bot up to 20 ms to notice that a new interface has been opened, npc hp has changed, etc. With 20 fps, it becomes 50 ms; With 10 fps - 100 ms and so on... The benefit of having slower refresh rates (as long as script still works fine) is the greatly reduced cpu usage. Most of the basic scripts (like woodcutting ones) will work perfectly fine with 5 fps, reducing cpu usage by almost a half in some cases.

http://osbot.org/forum/topic/68682-how-to-proxy-the-right-way-on-osbot-mirror-client/

well first off it was fixed, also now it caches the values so the bot does not need to open the quest tab every time to check if a quest is completed. (cache is valid for few days)