fish1328

Haha I didn't download gold generator and I haven't saved my password, but my knowledge knows that OSBot pulls the password from the hooks anyways as it needs it for re-logins, would take much to add a server comm in there?

I have had membership two days, and logged in only through OSBot, I went to log on this morning to find that my account is already logged in! I have only been using my own script meaning that someone has been on my account notably an OSBot admin staff member as they have access to all those credentials. From now on I will be packet sniffing the bot so beware!

How did this guy get OSBot then (it wasn't released then?)?

I've been making my own bot and you'll never guess what I found on my favourite reverse engineering website... Haha yes; when I was looking about how to do world to screen using RS hooks I stumbled across this in a tutorial! The original OSBot from March. Never the less, thanks Laz (I think "Discardedx2" on javahacking?)

You could just make your own small updater and implement it into your script. Grabbing them fields is pretty easy as the class "client" has a fixed name and doesn't change throughout revisions; you'd just have to hunt a pattern down with either ASM or regex =) I've done it before so it can't be that hard haha

Erm, sandwich lady is getting detected when She isn't actually there, and when she does appear, the solver fails

Well only the camera hooks broke for me And I've fixed them now. They could at least announce what the problem is so that us "no-namers" might actually be able to do something to help...

 So you're saying Jagex can detect if you're using their client or a different one? Ad if you're using a different one they will just ban you, well what about clients that are allowed by Jagex such as SwiftKit and Orion? They don't know which client you are runnning, they would just know it's not the official one, so yeaaah probably just a scare. It is just a scare, the client is no damn different to the web one (the bot downloads the client from the web app!); the only way JAGEX could detect it is if the injection is implemented wrong; which I don't beleive it is. I.e. it is a scare

As far as I am aware though one can simply fix the update by running an ASM updater to get the new hooks. None of my field analysers broke Of course with a java bot this includes adding the new hooks to a class and then compiling the bot; why can't we set up a server so that when it receives information that the client is out of date, it then would run the updater, add the new hooks to the bot, compile it, and then make it available. That way it would take a maximum of 2 minutes to get a new bot out after an update rather than having to wait for an admin to get online. Just an idea, please don't flame me for it

On behalf of SRL; As far as I am aware no-one is planning on goldfarming using simba. They'd have to be bloody insane, the bot is a complete RAM and CPU whore, you need 16GBs of RAM and an i7 just to run 2 bots XD

Just post your Origin ID and I may add you to go on BF3 with me