However, it is still important not to go rage hacking due to the risk of getting banned by other players reports. With the help of an individual method of encryption for every user, the anti-cheat cannot track the information of the running cheat. Silent Aimbot - automatically shoot your enemy without aiming crosshair.įOV - Field of View, aimbot will work within the selected range.Īimbot Smooth - adjust the smoothness of the aiming.īones Selection - select the aiming area of the enemy's model.ĮSP Box - highlight your enemy with the box.ĭistance - show distance between a player and an enemy.Ĭrosshair - put a crosshair in a midle of the screen.Īnd by this we mean that our RUST hacks are really undetected. Toggle Aimbot - enable all the aimbot settings of the hack.

Regardless, McFarlane says OVH has done well for Facepunch in the past and that it'll continue using OVH in the future.!ALL OF OUR PRODUCTS USE INDIVIDUAL METHOD OF ENCRYPTED BYPASSING, MAKING IT HARD FOR ANTI-CHEATS TO DETECT! RUST Cheat Features It's unknown how the fire started yet, or whether OVH was at fault. McFarlane estimated that around 30 dedicated Rust servers were lost during the fire, though all of those are now back online. Some players were upset that they lost days of progress in a game that runs in real time whether you're logged in or not, but McFarlane said that, in general, players understood that it was an exceptional situation. 'We did the best we could with the time we had, running on the little sleep we had.' 'I feel we did everything else right,' he continued. 'We need to ensure player progression data is backed up offsite, and we'll make sure this happens going forward.' 'We're always prepared to have servers go down but never en masse,' said McFarlane.Īs for the data on the servers, Facepunch had both local and on-site backups, as well as offsite backups, but player progression data wasn't backed up offsite. That was just four hours after they became fully aware of the fire. Within 11 hours of the first Rust servers going down, the Facepunch team had gotten all of them back up and running. 'We'll need to move the servers again in the coming weeks, but it's all we could source with the quantity we required quickly,' he said.

It wasn't ideal for Rust's players, or for McFarlane's team. That's some 1,000 kilometers from Strasbourg, the server's original location. 'We had to settle for OVH Poland,' he said. On top of the sudden scarcity, they couldn't take just any servers. Complicating things, Rust's servers see large DDoS attacks regularly, and as a result they're particular about the hardware they use. 'We were not the only ones doing this, stock of OVH servers in other locations began selling out,' he continued. That was less simple than they'd have liked. 'We confirmed a total loss of our servers and immediately started sourcing new servers,' said McFarlane.

'I'd guess everyone was trying to log in at once to find any information,' he said, which meant that the server company's web panel nearly unresponsive. Simply identifying which servers were affected wasn't easy. 'It was clear we needed a plan to get the affected servers back online and communicate to our players.' 'I was utterly shocked when I saw the pictures on Twitter of the building fully engulfed on fire,' said McFarlane. (Image credit: Sapeurs-pompiers du Bas-Rhin)

Rust 2018 aimbot server