fennecer

My mirror mode used to have the problem you guys are describing but no longer does since the recent OSBot updates. I can run 8 mirror modes on my system 10 hours no crash. Why would there be this much of a difference between us? Not flaming. Genuinely curious.

Huh. Is there an option for English and also American English? If so try both. There is a bug with systems being in foreign languages and not being able to download the OSRS client. It gives the same error you gave and switching to American English usually allows the client to work.

Change your windows system's language to English, not Portuguese. ? And to answer your other questions, MS stands for millisecond. Reducing the FPS of your bot (as long as the script still runs fine) slows the refresh rate and eases the CPU load allowing you to have more bots. You can have scripts running at 5-10 FPS. It will look a little choppy, but it doesn't effect the productivity of the bot in a good amount of cases. If I am wrong someone please correct me, I am also learning.

I can assume the profit per hour is abysmal with this script.

Yeppers. OSBot then connects to the Jagex RS Client. Stealth injection uses its own client, similar to how OSBuddy and Runelite are their own clients, and is more easily detected. By mirroring the original Jagex launcher you significantly reduce the ban rate at a cost of more CPU usage. You seem new, so you may also not know that holding shift + f2 will reduce fps from 50, to 20, and to 10 with each press. Do it once more to revert back to 50. And shift +4 reduces ms by 50 each press. I see people recommending a FPS of 20 (10 for very simple scripts like woodcutting) and a MS of 500 to lower CPU usage and increase the amount of bots you can run reliably. You will see these details in green letters in the top left corner of the OSbot client. It's something I wish I knew when I first got into botting. Also, be careful not to use stealth injection during Runescape's update day which is always Thursday. Lately they have been detecting and locking accounts immediately upon log-in with stealth injections on Thursday. Mirror mode still safe for not getting auto-locked for me at least. Edit: I said you seem new but your join date is like 2 years before me. Sorry for any insult xP

Appreciate your fix, but the real reason it works is because Patrick fixed it last night with those two updates (2.5.31 being one of them.) ? Also mirror mode, as far as I know correct me if Im wrong, is not necessarily meant to work with OSBuddy and RuneLite. It works sometimes but only the Jagex launcher is actually supported by the team. Edit: Wow that's an obnoxiously large tongue face.

This has been me for about 2 weeks. It used to run the script, but extremely choppy (abnormal for me) and eventually crashing. Now it wont run a script at all.

The simplest way to fix this is to simply wake up half way through your botting session and restart everything (annoying.) As far as I know there is no good way to fix it short of buying more memory or botting on a VPS. Java is terrible with memory leaks and eventually the amount of heap space available becomes cluttered from the leak, eventually becoming insufficient and the program in use will crash. I don't believe its the fault of OSBot so much as it is Java as this happens with other programs I run with using Java. Also keep in mind that your bot auto-logging out as part of a break will not fix the issue. The client itself will need restarted. If I am wrong someone please tell me otherwise so I know for myself. If you're using mirror mode, by the way, I can't get mine to work properly and they will crash. The developer has apparently quit due to outside responsibilities but I believed they hired someone else recently.

The real question you want to ask is if anyone has done it recently. Botting appears to have been much easier back in the day comparatively to today.

Im newer to the site so I just became aware of that happening. No rush of course. Cheers.

My mirror mode over the past week has been incredibly CPU intensive to the point where a script will run for about 30 minutes, and then exactly as you described will happen, with blacked out OSRS clients left over. If it's not fixed soon I'll make a more formal bug report or whatever, I just figured it'd eventually resolve itself with an update or something. Injection works fine, but ban rate is very noticeably reduced on the mirror for sure. Edit: I don't really feel the CPU usage in my task manager, I guess. But it definitely slows down my other programs more than it has in the past so it just has a CPU feel. I dunno.

Most likely just the OSBot update like someone else said, but keep in mind all the most recent Windows 10 updates for the last month and a half should be avoided with impunity, as even their hotfixes for the CPU issues are bugged. They're dropping the ball.