Skip to content

Configuration

camohax edited this page Sep 21, 2026 · 3 revisions

Configuration

Generated at config/omnisign-common.toml on first run:

Option Default Description
opOnlyEditing true Only players with the edit permission can create/edit sign text at all.
requireOpToTrigger false If true, only players with the trigger permission can right-click a command sign. If false, anyone can trigger a sign an operator already set up (e.g. public warp/kit signs).
allowConsoleCommands true Allow the console-permission command path ([cmd] marker / /sign command add console).
allowPlayerCommands true Allow the player-permission command path ([pcmd] marker / /sign command add player).
cooldownMillis 250 Minimum delay between two triggers of the same sign, to prevent double-firing from duplicate packets.
colorMarkerLine true Auto-recolor a sign using the [cmd]/[pcmd] inline marker (cyan, glowing) the first time it fires, so it's easy to spot.
logTriggers true Record player-caused sign triggers (clicks, menu buttons, proximity) in config/omnisign/triggers.log, viewable with /sign log.
discordWebhooks [] Named Discord webhook URLs, one per entry as name=url. The URL is never exposed to /sign discord list, exports, or templates — only the name is. Must be set here before /sign discord add will work — see Command Reference for the full setup steps.

See Permissions for the omnisign.edit / omnisign.trigger nodes referenced above.

Clone this wiki locally