Commands and permissions

The main command is /mm, with the aliases /manukamod and /moderation (and /manukamoderation:mm when another plugin also registers /mm). In game, type commands with a slash (/mm status); in the server console, without it (mm status).

Typing /mm alone lists the subcommands you are allowed to use. Tab completion only offers what your permissions allow, and never suggests anything for a password or a license key. Answers come in your own language (see /mm lang); the console uses the server language.

Player commands #

/mm panel and /mm password need manukamod.panel, /mm alerts needs manukamod.alerts, and /mm help and /mm lang need any manukamod.* permission. They work in game; help and lang also answer in the console.

Staff commands #

These need manukamod.admin (except /mm case, see below) and also work from the console.

/mm case is also allowed for anyone with at least one manukamod.panel.violations.* permission; they only see the violation types their permissions grant.

mm status
mm license activate MMPRO-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
mm case list Steve
mm export 2026-09-01 2026-09-30
/mm alerts off

Over RCON #

The console commands also work over RCON (from an RCON client or a hosting panel's web console). RCON only returns what a command prints while it runs, so the commands that need the database, the network or a file (mm case, mm user, mm exempt add|remove, mm email test, mm ai test, mm update, mm license activate|deactivate, mm debug dump, mm export) answer at once that the result will be written to the server console. The full answer then appears in the console and in logs/latest.log.

Passwords and keys stay out of the log #

The server normally logs every command a player types. For /mm password, /mm user add, /mm user setpassword and /mm license activate, the plugin removes that line from logs/latest.log, the console and anything that forwards the console (such as a DiscordSRV console channel), and marks the command as cancelled so command loggers that skip cancelled commands do not record it either. Other plugins can still see what you type (a command spy, for example), so /mm panel, with no password typed at all, is the safest way into the panel.

Permissions #

manukamod.admin includes every permission below except manukamod.exempt, so operators have them all. In the Default column, "op" means operators have it and "–" means nobody has it until you grant it.

The manukamod.panel.* permissions add panel access on top of access.groups on Pro (access.permissions-override), and they are the only source of panel access, on every tier, when neither LuckPerms nor Vault is installed. Most servers only need the group mapping in config.yml, plus manukamod.panel for whoever should log in.

With LuckPerms #

From the console:

lp group owner permission set manukamod.admin true
lp group mod permission set manukamod.panel true
lp group mod permission set manukamod.alerts true
lp group helper permission set manukamod.panel true
lp group helper permission set manukamod.panel.violations.spam true
lp group helper permission set manukamod.panel.violations.caps true
lp group builder permission set manukamod.exempt true
lp user Steve permission set manukamod.update.notify true

The two manukamod.panel.violations.* lines for helper give that group spam and caps cases through permissions, which counts on Pro. On Free, make the group one of the first two entries of access.groups instead.

The panel reads a player's primary and inherited groups from LuckPerms. To see what it will find for someone, compare lp user Steve info and lp user Steve parent info with /mm user groups Steve.

PlaceholderAPI #

When PlaceholderAPI is installed, the plugin registers the manukamod expansion on its own (it survives /papi reload). The numbers are refreshed every 30 seconds.