Swizzbeat Posted January 9, 2017 Posted January 9, 2017 except for the fact that they can see what client you are using, so if it looks like you are using osbuddy it looks much more legit. until the bot throws an exception and a stack trace with "org.osbot" in it gets uploaded to osbuddy servers for dev analysis 1
ScottFTW Posted January 9, 2017 Posted January 9, 2017 (edited) Any update on this matter devs? @@Zach @@Alek Edited January 9, 2017 by ScottFTW
Abuse Posted January 10, 2017 Posted January 10, 2017 until the bot throws an exception and a stack trace with "org.osbot" in it gets uploaded to osbuddy servers for dev analysis That's not how things work
fstyle Posted January 10, 2017 Posted January 10, 2017 Think about it, why does people not care much about mirror mode compared to injection? Yep.
Swizzbeat Posted January 10, 2017 Posted January 10, 2017 That's not how things work what do you even know what a stack trace is 1
ScottFTW Posted January 11, 2017 Posted January 11, 2017 what do you even know what a stack trace is (traceback) is a report of the active stack
Abuse Posted January 11, 2017 Posted January 11, 2017 (edited) what do you even know what a stack trace is Mirror mode duplicates the attached client state (OSBuddy in this case), and does it's computations within the clone, there won't be any reference to anything external within the attached client. Any exceptions happen in the instance Edited January 11, 2017 by Abuse
kushad Posted January 11, 2017 Posted January 11, 2017 this is nothing new, mirror mode has always been neglected. I once thought it was the most amazing thing until i ran vs the normal stealth and i found lesser ban rate. It is a waste of cpu and money if you are not using multiple accounts for it. Ditch it and dont expect updates for it.
Swizzbeat Posted January 11, 2017 Posted January 11, 2017 Mirror mode duplicates the attached client state (OSBuddy in this case), and does it's computations within the clone, there won't be any reference to anything external within the attached client. Any exceptions happen in the instance To the best of my knowledge mirror mode operates using the Attach API. I'm not sure if you're familiar with it, or even if you have any sort of programming experience outside of basic goldfarming scripts (going off your user title here) but if you do you should understand the loaded agent is running within the target JVM. Even if they've switched it up and do things differently now (native C++ lib with JNI?) it's still quite easy for Jagex to detect. Scanning processes, it's modules, etc. You'd have to do some fancy API hooking to even begin covering up your tracks. 1
Abuse Posted January 11, 2017 Posted January 11, 2017 To the best of my knowledge mirror mode operates using the Attach API. I'm not sure if you're familiar with it, or even if you have any sort of programming experience outside of basic goldfarming scripts (going off your user title here) but if you do you should understand the loaded agent is running within the target JVM. Even if they've switched it up and do things differently now (native C++ lib with JNI?) it's still quite easy for Jagex to detect. Scanning processes, it's modules, etc. You'd have to do some fancy API hooking to even begin covering up your tracks. Yes, you are correct. Mirror mode more than likely uses the attach api (Or a lower level implementation of it), however it is not possible to get any valuable information about attached agents, which means that, to my knowledge, it's impossible to detect OSBot using common methods. Of course process scanning is a way out, but Jagex doesn't do that.
thechuck Posted January 11, 2017 Author Posted January 11, 2017 Weird, mirror client doesn't matter at all. Yet i've been botting an account for the past 2 months on mirror mode, then I start using stealth injection 3 days ago and get a temp ban? 1
Swizzbeat Posted January 11, 2017 Posted January 11, 2017 Yes, you are correct. Mirror mode more than likely uses the attach api (Or a lower level implementation of it), however it is not possible to get any valuable information about attached agents, which means that, to my knowledge, it's impossible to detect OSBot using common methods. Of course process scanning is a way out, but Jagex doesn't do that. Ok, again, I don't think you know what you're talking about. Read the documentation, write some sample applications and play around with it. Jagex used window title enumeration awhile back so saying "Jagex doesn't do that" is just naive. If any of us knew what Jagex did we'd have an undetectable bot (inubot ftw).
Artifacts Posted January 12, 2017 Posted January 12, 2017 Weird, mirror client doesn't matter at all. Yet i've been botting an account for the past 2 months on mirror mode, then I start using stealth injection 3 days ago and get a temp ban? I can agree, I also was motivated to buy VIP because of this function, but for now it seems I'm going to wait a little bit 1
Vichy Posted January 12, 2017 Posted January 12, 2017 (edited) Using their client DOES seem to reduce the ban rate. Had suicide bots running with a different botting client that uses the same technique (but as primary and only) for dayzzz. It just seems like more of a 'legit' player if I say so myself. But, of course, if you complete a quest, do some changing up once in a couple hours you'll get much, much more further. Edited January 12, 2017 by Vichy
