Search results
Results from the WOW.Com Content Network
Except it isn't at all, since OPs script doesn't pass any input into the game. It's more similar to having Rust labs open on a second monitor with a script that let's you look up how much boom you have to use for certain wall types, you still have to identify the wall type, track the damage you've done so far, and use the boom optimally, all the script does is save a few seconds the user would ...
A few days ago, I got a positive response from people on a story of me and a friend code raiding a base. Code Raiding is quite easy to do and, in the case of very large or hard to raid bases, may be the easiest way in. I'll teach you how to do it, but even more importantly, how to make your base more secure.
Yeah, just click the link and press the buttons to cycle through the codes. If u want more specific instructions click on "built on code studio" and "view code" and look at the top for a comment with a bunch of tips.
One time I code raided a group whose leader was named Jimbo7056, because their code was 7056. Just find people as dumb as that! If that isn't an option, as others have said, try common patterns - both numerical and like, physically on the numpad. People like codes that are easy to type in repeatedly.
Rust Devs should give the option on code locks to use either 4-digit or 6-digit codes and not specify to guests accessing the lock which one is used. Goes from 10,000 combinations to 1,000,000 possible combinations.
If this doesnt work, then I switch to a list common bank pin codes (with these 576 codes removed). But it works like 25% of the time for me. (and it seems worth it since 576 is not a lot to test). It takes me 1.5 to 2 hours to test all the codes. Story time: One time I used this to ruin the base of a zerg french clan while they were out raiding.
I made a program with AppLab (ik, im a pleb) which generates rust codes to help with code Raiding. Because the vast majority of codes use one side of the keyboard (0-5, 6-10) and have atleast 1 repeating digit, you can narrow down the possible likely combinations to ~1000.
Traditionally they have always tried to stop code raiding which is why the shock was added in the first place. The shock doesn't stop code raiding, so if that was the intent with adding that feature it really speaks to efficacy of the reasoning skills of the development team.
but more e.g 2121 or 7845 which is between 0-3000 in the ordered list 2. Using that list and going from the bottom up or in the middle, thoughts being that maybe rust players try to think up a password people won't guess so it's better to start off that end. But might be giving rust players too much credit and the code could just be 6969 3.
The way it works is by having you add a base that you want to raid and then it generates a random code between 0000-9999, without ever repeating the same code twice. It makes use of global hot keys so you could have the program on a second monitor and press "CTRL+N" while in Rust to generate the next code.