Leaderboard

Hey, A quick release to support the latest changes API CHANGES: - Updated the API to reflect the latest game changes. MISC: - Minor bug fixes. - The OSBot Team

Still a negative on trials, sorry!

Hello and welcome back! Mainly avoid hotspots, try to build them in a unique way compared to farm accounts Take enough breaks and don;t look like a bot

Trial pls

would love to try this

Both are fine, but you'll need some post count to be able to sell accounts on here.

Yes, I noted that it is still beta, that's why I'm trying to report issues as they arise - no judgement on the script as a whole

$20 usd id say

Can i try this out?

can i try this ? trial pls

Is there any update on progress?

Thank you, I did these on my hunter rumour beta acc, maybe something changed but it’s easy fix. Next update will be within <24 hrs Also just as a disclaimer I must mention hunter rumours are still in beta, but every update will be closer to flawless

HEY BRO. your script look very nice can I have a 24 hour trial?? is there any package to buy them alll for a specific price?? thanks

OSBot has been amazing as always, for AI bots.... its just marketing

I do it, hard to test the theory of whats safe or not though. You can't get banned for botting if you don't bot though I think?

Start small and don't get discouraged when accounts get banned. It will take a lot of trial and error, and you will most likely lose money at first. But if you stick with it you might become profitable. Use lots of breaks, try a variety of methods, don't bot too much in one day, residential proxies, premium scripts, hardware mouse and mirror mode is usually best. Best of luck sir!

One is more modern hardware but has smaller heat sinks so it can't run at 100% cpu or it overheats. The other one with older hardware has plenty of cooling, but of course older hardware isn't as fast which is what I'm mainly basing things on since it's the one that's used the most (24/7 since 2019 basically). It has 32gb ram 6 core phenom 2 amd cpu 3.3ghz black edition (on stock clock). It sucks a good deal of power, but it's what I have on hand. I've been using this server for years, and the script hasn't changed to cause the cpu issues. The only changes are after the cpu spiked the first time I added some extra sleeps in possible areas that could spike cpu usage with no change. Like I said, I can recreate the issue with the official client, it started back up with the cpu problems at the last rs update and it has come and went in the past a couple times or so. The script effected the most by this has barely changed since 2019. I haven't tried other bot clients to see if anyone has detected the issue and figured out a workaround/solution to it. I'm sure it's quite a niche issue that most people don't notice it. If I had more time to learn how a bot client is made, I'd probably be able to figure out what's going on exactly. I know RSA encryption is part of the login protocol, but encrypting a message isn't hard for the cpu and 1000's of messages can be encrypted very quickly. This is more like a wait loop with no sleep in Jagex's code, or they intentionally make it high cpu by performing some useless task like md5 junk data 100k times. It comes and goes with rs updates, so I'm almost positive it's 100% jagex's code side of things. If it's just a bad loop or useless processing, I don't think it would be too hard to skip over the work load or add a small sleep. It could be possible they have a different protocol for login sometimes that requires more work to be done (say the 100k md5 thing, but with the password) and they use that to validate if the password matches what they have pre-processed. When the cpu issue happens, java is using 100% usage of a single cpu core. Before the same area of the login would take around 5-20% (1-4% overall cpu usage vs 17%). I suspect in 1-2 rs updates it will be gone again.

They introduced a stronger check on RWT on the 16th, so you might have just been unlucky. Since the update, they are now punishing both the buyer and the seller. I hope you can get this fixed, but with this update they are focusing on it more strictly.