-
Posts
271 -
Joined
-
Last visited
-
Feedback
0%
Everything posted by dantan
-
I've seen people get this alot , 48 hours. Ive seen pmods answer this on official rs forums. 48 hour ban is actually because a) Bot busting b. Jagex anti bot flagged you as suspicious and is pending review. The 48 hours is meant for a J MOD to review evidence and is normally pending a permanent ban AFTER ( Depending on the investigation ) on how you bot. If you're an obvious gold farmer the permanent ban hammer will definitely be stamped on your account. Jagex does give chances but after that 48 hour ban, they will definitely highlight your account. Stay low, change your IP get more involved legitly. Avoid areas/skills with high ban rate that would be my suggestion. There is no room for gold farmers that suicide bot. Reporting other players has been made easy by jagex so be vigilant and bot smart.
-
What kind of vps, Windows or linux?
-
Would it be illegal if jagex scans your disk for folder names? eg OSBot
-
Been there before. idk if you have to go to court and choose sides tho because i was practically forced to do that -_-
-
What do you mean by invisible random events :')
-
that shoe looks ugly and retarded
-
Dayz SA
-
Disclaimer : post taken from another forum which will not be named. I would like if script writers read this post and express their own opinion, draw their own conclusion and the validity of the statement below. Client detection (client-side): Jagex detects if you're logging in from another client than the original one. How do they detect the client? - Check the title of the window (They did this in 2012) - Checksum of all files are being send to the server and they check if the values are the same (http://en.wikipedia.org/wiki/Checksum) - They count the methods/fields of all files and see if any code (hooks) have been injected like *** does now ("private int getHealth();") - They can check if cookies have been updated and where they're directing from, if there's a valid user agent according to your operating system and standard browser (http://en.wikipedia....Request_Headers) These are the only client detection methods I can come up now but there are definitely more Behaviour Analysis (Server-side AKA BotWatch): This is software running on the Jagex servers. Every action that you do will send a command to the server. If you click the rs-map ingame the client will send a command to the server like this: "Packet Id:137 X:3125 Y:1253" the server will calculate the path and send movement info with animations to the client which will display them. These packets can be used to track all activity on your account. And this is what they use for their BotWatch system How does BotWatch work? Well first of all nobody is sure but there are speculations/theories. I have searched some papers on Server side bot detection written by Profs/Students who are located in some of the best universities in the world. But here are some that I think Jagex applies: - Command timing: This is where they time the reaction time of a player when the server send data to the client. If the delay is too short or the delay is static you are detected. If you ploth this out on a graph you can easily spot out the botters. - Heat maps: They track all your mouse clicks and build heat maps where you clicked on an object / path. If you graph this out over time you will see bots use the same points but randomized by 20 coordinates while real players have different heat maps - Packet patterns: Tracking of all packets with their parameters and running a neural network with heuristics over it to see if any patterns have been detected - Simulation: (Probably used in the very early days of BotWatch) Jagex has a team of people which load whole a player's session (packet recording) in a closed environment and decide if the account looks like a bot. Thus they can watch your acitivity even though several days/weeks have been passed For more technical information on how BotWatch could work please take a look http://asp.eurasipjournals.com/content/pdf/1687-6180-2009-797159.pdf The reason why bots like (R** - cant mention bot name ) aren't so easy detectable is. It uses colors thus no modification (no client detection). It's slow because all it's actions are being sent from their server to the program. If a bot is not very functional the system is less likely to detect it. I can imagine Jagex setting a high enough treshold for their system not to detect any false-positive bots. If Bot's client wasn't decectable and you wrote a slow script with alot of unneeded camera / mouse moves you wouldn't also get detected. What does the future hold? Today bots and Jagex are in a code war, currently their client detection is very strong which we hope to surpass it within several weeks. After that Jagex will try to update their client detection. So you have to think Jagex ALWAYS has to take the first step and then we can anticipate. Eventually Jagex will run out of methods to detect the client and will mainly focus on scrambling data (which will also be killed in a matter of time) and their BotWatch system. If we can fully withdraw our attention from the client we can work on AI behaviour systems. There's no way they can defeat bots unless they can take legal actions or the owners get bored.
-
Asking this because im hearing information about jagex mods manually checking when they do a bot bust... in game
-
Can jagex detect the type of client we are using? Eg a bot or a browser or a downloadable client or orion? I dont mean "detect" as in automatic but can they do a manual check on someone who is currently connected to their servers?
-
I can surely tell jagex did something because for the past 3 days i notice bans going up
-
i did, was it bot busting tho?
-
I think they might have done a mass ban in the past 4 days.
-
Exactly why i posted this.. because i do actively monitor so its really odd how i got bot busted :\
-
Can someone who knows explain this vs the normal macro ban?
-
To bad jagex dont know how to mitigate shit :'c
-
lol im looking at the server list i have never seen that litle people play rs before lol almost less than 5 per server
-
Quality of the ssd + use case is important i never denied that are you blind? But you were implying general usage + Gaming usage. An SSD WILL NOT wear out in 1 year from gaming usage or general usage. Unless of course you give them OCZ Drives LOL SSD not lasting a year can mean many things, doesn't mean the flash is bad and doesnt last. All SSDs list the maximum read/write cycles, if an ssd fails before the maximum r/w cycles is reached doesn't mean its the nands fault. Please educate yourself more about ssd before you post. You seem so stuck up about ssds, maybe its because you can't afford it getting sick of replying your uneducated post. Atleast post some proof to back up your statements instead of saying ssds arn't worth the investment.
-
You are inexperienced. and i never said anything about 1) quality ssds 2) gamers not using write cycles 3) flash cells FYI the flash market is growing much faster and much more than the hard disk market. And all storage companies are heavily invested in SSDS/flash market. Work wise i deal with ssds and enterprise data solutions fag so i know how ssds work. I bet you don't even know how to setup a san. And i know how long SSD's last and your assumption of 1 year is the dumbest thing ever. I can say HDD fails too in less then 3 months.
-
I handle server hardware and workstations, ssds life span in 2014 are excellent and can handle heavy r/w and have a long life span. An average "gamer" can never wear out an ssd with normal workloads in 10 years. And SSDS are not just to make your boot time faster idiot. And the limitation is not in the flash its the sata controller. At least get your facts right before replying.
-
Oh another ignorant noob who doesn't know much about computers :\
-
limitless