irwtonrs1

If you're using mirror mode, the only thing you need to proxy is whatever you're mirroring. So the RSclient, web browser etc.

cool

Yes, you'll have to do 2 bot tabs per client.

Mmmmm...no

1) Add the proxies onto proxifier. 2) If you're using the official RS client for mirroring, right click the desktop icon and open it up with proxifier and select the IP in which you want to use. If you're using a browser, use maxathon http://gyazo.com/460bed18535db61f7f2b0a639de2df2e

Sup

fuck i laughed hard at this

the virgin life

Weath has been back to work for like 2 hours?..

I read the title as you selling one of your "homies" for 20M.

GE doesn't work?

Weath is currently on vacation in America.

I'm not sure if you're aware but there is this thing called the Grand Exchange. It works wonders.

I'm pretty sure Weath if off work this week.

http://osbot.org/forum/topic/68924-for-windows-users-experiencing-could-not-load-stream-library-error/ Look around next time.

Chuck that shit.

http://osbot.org/forum/topic/68924-for-windows-users-experiencing-could-not-load-stream-library-error/ Look around a bit next time.

Nothin like risking your account to organize your bank.

If you scam, you should just be perm banned from the site with no chance of return. If you feel bad after doing so and want to repay the user, feel free but you should still stay banned.

I don't think they really even use these worlds anymore, but I'd avoid going to them on an account you bot with. Although if the accounts is 100% legit, feel free.

For a majority of the time, an account in question is manually looked over by Weath before the ban is applied. edit: I can't tell if you were telling him that or that your statement was sarcasm.

Yes, this has nothing to do with java anyway.

yup

Basically, after about 30-40 minuets of running, whatever platform you're hooking the game from, RSclient/OSbuddy/Webbrowser, it will black screen. On OSbot, your screen is frozen with the "Loading-please wait." (I obviously did the white out) Apparently this happens because the client you're using (not osbot) runs out of memory because the newer versions of mirror load objects faster so it needs to use more memory. The only fixable solution to this problem that @MGI showed me was to go into a file called "oldschool.prm" and change the memory output. (This was for the official oldschool client). The only problem with doing this was that he did mention to me that Jagex sends this information to their servers so changing the memory on the client could possibly flag the accounts, although he wasn't 100% sure. I had tried this fix last saturday and it prevented the clients from freezing up until Tuesday morning, where I had 20 accounts that were all running on mirror and on clients with the increased memory banned. Whether or not changing the clients memory had anything to do with it, I do not want to take the risk again. Does anyone else know how to fix this without changing the memory or is this something that @MGI will have to fix by making changes to the mirror client? Also, is anyone else even experiencing this because I haven't seen anyone else post about this happening to them.

Will we be seeing a fix for this this weekend?