1. Rust Devblog 88:
    "In this update I also adjusted the default user level for antihack to include admins and developers (antihack.userlevel 2) since we were getting a bunch of exploit reports that were only possible because the people who tested them used admin accounts and were therefore excluded from the server side movement checks. If you want to noclip as an admin, you can temporarily make antihack exclude admins (antihack.userlevel 0). I’ll also add something that automatically does this for you when admin noclipping is enabled as soon as I’m certain it won’t open up any potential exploits."
     
  2. That moment you entered the command and saw everyone flying around... Priceless. But now im in doubt, can i set it safely or not?
     
  3. Leaving it as it is. Just have to put up with it.

    Allowing users to fly around is silly and will cause problems.
     
  4. what is the result cant we pass objects? walls? :(

    Ty,
     
  5. Question for antihack.userlevel if set to 1 would that mean that ownerID would be the only ones able to fly? if so im happy with that, I can not currently test it as doing overtime at work.
     
  6. Only with antihack.userlevel 0 ...the admins can pass through walls ... didnt test it yet the players, if the can fly (with antihack.userlevel 0)
     
  7. It does not affect if a player can fly. Setting to 0 just means that antihack only works for players and ignores admins and developers.