irwtonrs1

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?

I'm not sure if you can. I've run into this before. I have multiple VPS's so I simply do 1 client with 2 bot tabs per desktop. I don't think there's a way to fix this other than just using more bot tabs on one client, but then you run into the problem of having so many accounts running on the same IP, which I assume that's something you're NOT trying to do hence the reason you're trying to get this fixed.

You're a goldfarming god?

Is the incorrect object loading bug still present?

What do you have the memory set at?

If it's an account you care about at all, don't bot it again and enjoy the free exp you did manage to get.

Very much possible. You just have to buy something that can run them. I have 2 dedicated servers I'm using to run a minimum of 20 bots via mirror. At 10 accounts per server, it uses like 7-8 out of the 24 cores it has and that's using mirror 1.055, the version that uses MORE cpu. I can't use the latest versions because of the object loading bug but if I was, it would be even less cpu.

http://www.reddit.com/r/2007scape/comments/3bsraz/rat_pits_duplication_glitch_has_been_patched_ama/

Were you botting on the account that had the 200m?

sucks

Basically, objects from one region are being loaded when in a completely different region causeing accounts to just get stuck. I'd supply a picture but I don't want to show what I'm botting. This is happening after about 40 minuets to 1 hour of running. This is happening in mirror versions .61, .70, .80 @MGI I showed you how the accounts where getting stuck the other day in team viewer so hopefully this can be fixed.

fake and gay

Jet fuel doesn't melt steel beams.

Bread and water.