Jump to content

dev027292

Members
  • Posts

    14
  • Joined

  • Last visited

  • Feedback

    0%

Profile Information

  • Gender
    Female

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

dev027292's Achievements

Newbie

Newbie (1/10)

0

Reputation

  1. ahem* I only said that because there are numerous sources with people who claim to have reverse engineered the game, and there is no need to do so myself at the moment. This isn't even a definitive guide, it is only speculation and discussion for the benefit of the botting community. And so far I have not reached a final conclusion as to whether Jagex' injection detection is "OP" status
  2. First I'm going to discuss reason why Jagex does NOT detect for client modifications: * their lock out system is rudimentary. It is certainly possible that certain forms of injections get flagged and immediately close down the client * extensive memory searching could slow down CPU. * implementing an accurate bot detection is incredibly hard and expensive * although I haven't reverse engineered any code myself. It appears as if their injection detection is indeed rudimentary as I have not heard anything about it * expensive computations as per bot detection are also expensive on the server and can add up and increase it's cost. * It is certainly possible to inject in a read-only way and send input such as keystrokes through hardware emulation rather than using the game's associate functions such as input handling routines, etc. * Jagex uses a lot of scare tactics which means that they probably need them, and seems to just mindlessly ban people regardless of whether they are botting or not. If they could easily detects peoples shit. They probably would not need to use scare tactics against us. ======== Now on reason why Jagex might be able to detect an injected client *guaranteed the original client must leave some kind of footprint *WINAPI offers an extensive amount of tools for scanning a processes memory *bot makers that aren't mindful of Jagex's practices will likely provide a garbage product that would just get detected on use ======== discuss
  3. I noticed the Model class has a vertices API. I always wanted to build a private server and figured ripping some of the game's models would be an excellent starting point. Hope is not lost however, a lot of these textures are so basic they can be cloned quite easily
  4. I honestly dont give a fuck, but i just wanna know if any of you devs have gotten your pay pal banned for publicly posting it's email in here.(not sdn but publicly posting it elsewhere here) you never know when some griefer could just skim by and report you to paypal
  5. Don't quit, otherwise you'll never find out the real reason they banned you . If you start using scripts with high anti ban, bot on more than one skill, and only log into rs 3-4 hours per day you might survive the ban.
  6. well consuming all the system resources could be flagged as a virus actually. If the bot just a null pointer exception and crashes the program. I would classify it as a virus.
  7. if that leak got out I'm pretty sure that whoever discovered it had already traded that in for RWT and then published it for jagex to fix.
  8. clear the jagex cache each time before logging in never use your real name/ birthday information on any new account that you create actually play like you don't want the account getting banned, make pure account, etc, don't make it seem like you're just another level 3 bot dont make it so obvious that you're botting, go kill other bots that are at wilderness, dont bot with cheap armor, use realiable combat scripts actually play the game from time to time, do some pking, chat to strangers, etc. bot a maximum of 3-4 hours per day, don't bot every single day randomize break-times and hours played use different scripts(trusted) for each skill that you bot, since they gain xp/ money at different rates. don't ever get your account hacked, the hacker could send proof to jagex that you are botting, use very distinct emails/passwords for each bot. stay away from other bots and bot-heavy areas, especially level 3 bots stay away from 13 year old kids that tend to abuse the report option don't use garbage scripts with poor anti-ban measures. avoid using more than one bot provider as they could have script trailing that could be detected by jagex have multiple bot accounts, but NEVER actually bot on your main, make your way to pmod and never get banned on that account use a proxy server and a VPN, never user your real ip *DEVELOPERS ONLY: jagex does things like swap the ID's of rocks and if you take too long writing down each ID their system could flag a potential bot dev - not sure on this but apparently buying members could decrease the odds of getting banned. things to consider: a massive botnet with ip's different than that of your own to distract Jagex and not get your real accounts banned.
  9. I think it might have something to do with Jagex and their bot detection systems.
  10. I don't usually visit more than 1 bot site. At the moment all of my scripts will be osbot exclusive. I'm pretty sure osbot doesn't have any viruses embeded in it, but imagine running 3-4 clients, that only increases the odds
  11. I'm trying to develop my own bot and also help the cause, however I'm still researching how to exploit the native client to get a better understanding of how the game is written and their anti-ban / memory scanning practices.
  12. i don 't see any virus, what's the deal?
×
×
  • Create New...