DUXPLIMA Documentation

Permissions

The permission nodes, who has them by default, and the Discord-side lists that permissions do not cover.

Every node below is declared by the plugin with a default, so operators have the staff nodes and every player has uxmdiscordsync.boostreward without any setup. The command nodes are the ones commands.yml ships with: if you rename one there, grant the new name instead.

Nodes

PermissionDefaultGrants
uxmdiscordsync.boostrewardEveryone/boostprize
uxmdiscordsync.adminOperators/dsadmin, /linkstatus <player>, and the in-game notice of a new version
uxmdiscordsync.admin.reloadOperatorsreload
uxmdiscordsync.admin.statsOperatorsstats
uxmdiscordsync.admin.forcelinkOperatorsforcelink
uxmdiscordsync.admin.forceunlinkOperatorsforceunlink
uxmdiscordsync.admin.forcesyncOperatorsforcesync
uxmdiscordsync.admin.boostownerOperatorsboostowner
uxmdiscordsync.admin.networkOperatorsnetwork
uxmdiscordsync.admin.debugOperatorsdebug
uxmdiscordsync.admin.databaseOperatorsdatabase importflatfile
uxmdiscordsync.admin.notifyOperatorsHears about a denied 2FA login. See Two-factor login
uxmdiscordsync.2fa.requiredNobodyIs asked for 2FA, when two-factor.require-permission is true
uxmdiscordsync.admin.*OperatorsEvery uxmdiscordsync.admin node above
uxmdiscordsync.*OperatorsEverything except uxmdiscordsync.2fa.required

/link, /unlink, /linkstatus and /discordreward need no permission.

uxmdiscordsync.* leaves out uxmdiscordsync.2fa.required on purpose: with require-permission: true, a wildcard would otherwise put every operator under 2FA without anyone deciding it. Grant the node itself to whoever should be asked.

Nodes you name yourself

Three settings take a permission of your choosing:

SettingEffect
two-factor.on-deny.admin-permission in two-factor.ymlWho hears about a denied 2FA login. Ships as uxmdiscordsync.admin.notify
plugin.version-checker.notify-permission in config.ymlWho is told about a new version on join. Ships as uxmdiscordsync.admin
chat-logging.filter.ignored-permission in logging.ymlPlayers holding it are left out of the chat log. Ships empty, which turns it off

Permissions Discord decides

Some things are decided by Discord ids, not by permissions:

WhoSet in
Who may use /servercommanddiscord-server-command.authorized-users in config.yml
Who may use /broadcastdiscord-broadcast.authorized-users in config.yml
Who may use a custom commandrequired-roles and required-user-ids in its file. See Custom Discord commands

Administrator rights in Discord grant none of these. /servercommand is console access, and it should belong to named people rather than to whoever holds a role this week.

A staff group

uxmdiscordsync.admin
uxmdiscordsync.admin.stats
uxmdiscordsync.admin.forcesync
uxmdiscordsync.admin.network
uxmdiscordsync.admin.notify

Enough to look into a sync problem. forcelink, forceunlink, boostowner, reload, debug and database change data or settings, and belong to a smaller group.