Permissions
Every Marriage permission node, and the config option that decides whether the player ones are enforced at all.
Up to date for v2.2.0.
Most servers need to grant nothing at all: marriage is handed to the default groups
automatically on first boot, and the player commands are ungated until you ask for them
to be gated.
The two switches that decide everything
| Config option | What it does |
|---|---|
Grant-Menu-Permission |
Grants marriage to the default groups once, automatically. On by default. |
Use-Permissions-For-Commands |
When false (the default) the player command nodes below are not checked at all. Turn it on to gate them. |
Player nodes
Checked only when Use-Permissions-For-Commands is true.
| Permission | Allows |
|---|---|
marriage |
Opening the Marriage menu. |
marriage.marry |
/marry player |
marriage.divorce |
/marry divorce |
marriage.tp |
/marry tp |
marriage.msg |
/marry msg and /marry channel |
marriage.gift |
/marry gift |
marriage.home |
/marry home, /marry sethome and /marry clearhome |
marriage.chest |
/marry chest |
Admin nodes
Always checked, regardless of Use-Permissions-For-Commands.
| Permission | Allows |
|---|---|
marriage.admin |
The Admin page inside the Marriage menu (the in-game config editor), and a Divorce control on the Married Couples list. |
marriage.admin.requirering |
/marriage requirering |
marriage.admin.force |
/marriage force marry, force divorce and force info. |
Each
forcesubcommand re-checksmarriage.admin.forcefor itself rather than inheriting it. All three either end a marriage or create one, and a permission that has to be revoked in one place should not be revocable in only one place.