Luanti Server Permissions & Privileges Guide

1. The Foundation: Naming Your Server Administrator

During the inception of a headless Luanti server, nobody inherently possesses administrative rights. If you log into the game using your player character, you are identically restricted as any passing visitor entering the world.

To declare the supreme administrator (server owner), you must interact directly with the core engine configuration file before executing the `luanti --server` daemon process.

1. Open your server configuration file (e.g., ~/.luanti/luanti.conf) strictly utilizing a text editor like nano.
2. Write or append the following variable exactly, defining your exact in-game character name:

   name = YourUsernameHere

3. Save the file natively and initialize the server.

When "YourUsernameHere" successfully authorizes and joins the multiplayer environment, the Luanti engine parses the configuration file statically, confirming your identity. It instantly bestows the overarching "privs" administrative umbrella natively onto your character.

2. In-Game Permission Management Framework (The /grant Command)

Once you acquire absolute ownership identically detailed above, you no longer require SSH backend access to assign basic abilities to trusted friends or community moderators continuously. You manage all roles through the in-game command line interface (T interface).

To give a player specific abilities:

/grant Username interact, shout, fast, fly

To revoke specific abilities immediately:

/revoke Username fly, fast

To bestow all possible abilities identically mimicking server ownership:

/grant Username all

Assigning `all` is functionally dangerous identically to yielding OP rights globally. That user can systematically destroy the environment, ban players randomly, or rewrite environmental rules natively. Only assign `all` privileges explicitly to proven co-administrators.

3. Extensive Dictionary of Luanti Core Privileges

Every default ability in Luanti is segmented beautifully into distinct operational nodes stringently. Here are the core vanilla privileges continuously verified by the game engine:

Luanti Privilege Node	Functionality & Operational Scope
interact	Fundamentally allows the user to break blocks, dig, place items natively, or open storage identically. Removing this creates an absolute "Adventure/Spectator" mode forcefully.
shout	Grants permission to utilize global chat channels securely. Revoking `shout` is the native Luanti equivalent inherently of globally muting a toxic user.
fly / fast / noclip	These movement modifiers permit ignoring gravity entirely, sprinting exponentially faster, or hovering explicitly through physical terrain walls natively. Essential for massive construction builders.
teleport	Allows execution of the /teleport coordinates generic command natively. Extremely useful if your server spans tens of thousands of procedural chunks natively.
bring	Grants the administrator ability to continuously pull users randomly across the globe mapping to their exact location. Excellent for rescuing stuck players identically.
kick / ban	The moderator permissions identically. Users possessing these can forcefully disconnect individuals locally or blacklist their respective IP address and name permanently across the server.
protection_bypass	Bypasses regional protection mods (like AreaStore or Basic Privs protection cubes) universally. Used by administrators globally attempting to delete abandoned user structures manually.
privs / basic_privs	Allows the user definitively the capability to grant or revoke specific abilities to *other* players. Absolutely restrict this natively.

When installing monumental ContentDB plugins maliciously altering weapons or establishing massive economy mechanics, those respective mods continuously inject new custom privilege nodes natively (e.g., `creative`, `home`, `economy_admin`) dynamically added to the overarching registry.

4. Establishing "Default Privileges" for New Users

Routinely granting basic abilities manually to every single new player joining your public network is exhausting and functionally impossible globally.

Luanti solves this effortlessly using the `default_privs` parameter identically defined in `luanti.conf`. This configuration dictates exactly what nodes are systematically attached to a profile the millisecond they authenticate natively.

default_privs = interact, shout, fast

If operating a hardcore PvP survival server, you probably solely want `interact, shout`. If operating a pure creative sandbox globally, modifying this explicitly to `interact, shout, fly, fast, noclip` ensures players possess building capabilities seamlessly upon logging in natively.

If constructing a rigid Hub/Lobby server necessitating players to complete a maze before escaping, strip `interact` from the defaults completely. They cannot break the lobby walls dynamically until a mod script grants `interact` explicitly.

5. Advanced Server Moderation Commands

Administrators enforcing rules navigate toxic behavior reliably utilizing the following native console integrations natively:

Viewing User Abilities:

/privs Username

Silencing Players Natively:

/revoke Username shout

Wiping Inventories (Punitive Measures):

/clearinv Username

Tracking IP Addresses for IP Bans:

In vanilla Luanti, tracking an IP inherently necessitates server log reviews dynamically. You must review the `debug.txt` native dump typically analyzing who joined successfully. Banning is simply:

/ban Username

/ban IP.Address.Here

/unban Username

Luanti checks the SQLite ban database locally every login continuously, bouncing bad actors instantly natively.