Better /admin commands & other features for server security

Discussion in 'Other' started by Nerva, Feb 26, 2015.

  1. Nerva

    Nerva Parsec Taste Tester

    Given the stink raised in this thread and this thread regarding the sudden upswing of people griefing with porn images, I'd like to suggest a few admin commands and features that will help bring these cretins to heel.

    First, bring over /toplayership from Nightly. This way admins can go right to the ships of potential offenders and from there, right down to whatever planet they may be in the process of griefing.

    Next, /invis - this command would render the admin totally invisible to other clients on a server-client level. The clients would not even recieve packets that the admin is there. The admin can't interact with the world in this state (for crash safety), but it's perfect for following around someone without them being aware of it.

    A /toplayer command. Like /toplayership, but it takes you to the current location of a player instead, dropping you exactly where that player is standing. Coupled with /invis, you can transport yourself to any player, any time, and observe them with complete impunity.

    An /amIlegit command. This command scans the inventory of the player you specify, or the player nearest to your cursor. If it discovers any items that have a level over 6, any items that are currently unobtainable without /admin /spawn(item/gun/sword) usage, or any generated weapons whose parameters aren't possible according to the algorithms that generated them, then the command will return a warning only visible to the user of the command. This warning will contain the names of all the items that failed the AmILegit check, their inventory slot IDs on that character, and the reason(s) each of those item failed the check - all of this info should be passed to the server log, too.

    Might be hard to implement, but a /whoplacedme command could be helpful. Hover your cursor over a block or object and enter the command to find the name, UUID and last known IP of the player that placed it where it is.

    A fantastic idea came from @teilnehmer about player permissions - I'm posting it here with his blessing. Basically, admins can set permissions upon a player that restrict or unlock capabilities. For instance, a "canmine" permission which controls whether a player can remove blocks or objects, a "canbuild" permission which controls whether a player can place them, or even something as specific as a "canplacesign" permission, affecting whether or not a player has the right to use signage. This would give admins the means to deal with block and sign griefing problems without outright kicking or banning the players involved.

    You should also take a look at this thread by Warped Perspectiv, which contains another idea by @teilnehmer on how to identify signs and who placed them.
     
    Last edited: Mar 3, 2015
    RatixFarrence likes this.
  2. Warped Perspectiv

    Warped Perspectiv Pangalactic Porcupine

    I think a teleport to player command would defeat the purpose of having a toplayership command.
     
    Last edited: Feb 26, 2015
  3. Jerln

    Jerln Oxygen Tank

    If the player you want to teleport to isn't at their ship, there would be no way to get into their ship other than the party system.
     
  4. Nerva

    Nerva Parsec Taste Tester

    Got it in one. Teleporting to a player doesn't put you in their party, so it doesn't give you access to their ship. You could possibly use /warp to get into their ship, but that requires knowing the name of their .shipworld files. That also assumes that /warp even works on *.shipworld locations. Having /toplayership would be a faster and more user-friendly solution, since it doesn't require complex arguments to use - just enter a player name.
     
    Jerln likes this.
  5. Jerln

    Jerln Oxygen Tank

    Right, I was just saying that without your /toplayership command it would either be impossible or very difficult to get into their ship.
     
  6. RatixFarrence

    RatixFarrence Scruffy Nerf-Herder

    Those commands would be great to have, and sound easy to implement.

    If I may add a related suggestion to this, I would like an admin to have the ability to grant limited admin privileges over a single world, and only as long as they are on that world. The admin should be at the same world as the player receiving the privileges. This can be great for creative level designers (like me) or other great projects and would help boost efficiency. They would not be able to spawn items, however. But they can have control over whether to protect/unprotect their world, view in /fullbright, /debug, and said /teleport to players on the world, etc. I really think that could benefit builders and can protect their hard work even while the admin is away.
     

Share This Page