Configuration

Location

<plugin data dir>/config.json. Written with defaults on first boot.

Full config

{
    "chat": {
        "channel": "staff.chat",
        "prefix": "[Staff]"
    },
    "tables": {
        "punishments": "staff_punishments",
        "players_seen": "staff_players_seen"
    }
}

Permission gating no longer lives here. Each command checks a permission node (networkstaff.<command>) via Hytale's PermissionsModule. Configure those in the Hytale server's own permission config - see 03_Commands.md for the full list of nodes.

Fields

chat

Field	Default	Meaning
`channel`	`"staff.chat"`	MessageBus channel used for cross-server staff chat. Don't share this with other plugins.
`prefix`	`"[Staff]"`	Visual prefix on every staff chat line.

tables

Field	Default	Meaning
`punishments`	`"staff_punishments"`	Table name. Change only if you really need to and you're prepared to migrate data.
`players_seen`	`"staff_players_seen"`	Same.

Setting up staff permissions

In your Hytale server's permission config, create a staff group (or whatever you want to call it).
Grant it networkstaff.* (or pick specific nodes - see 03_Commands.md for the list).
Assign your staff members to that group.
Players need to reconnect for newly-granted permissions to apply.
Test with /lookup <staff-member-name> from a staff account. If you see the lookup output, the perms are wired.

Environment variables

None specific to Staff. The relevant secrets (MYSQL_PASSWORD, NETWORK_AUTH_TOKEN) live in NetworkCore's env.

1.7 KiB Raw Blame History