Commands

Every Madsi command works as a Discord slash command or with your server's text prefix (e.g. w!profile), except /link and /relink (their sign-in card is private, so they're slash-only), and /members, /mc-ban, /mc-kick and /mc-unban (slash-only by default; turn a text form on per command with its Text prefix switch). Run /help in Discord for the full, always-current list. Admins can add aliases, restrict, disable, or add prefixes to any command on the Commands page, see Command permissions.

The page, refresh, tab, picker and editor buttons on a command reply only work for the person who ran it; anyone else gets a private note to run the command themselves. That includes a card's Recipe and Enchantments buttons: run /recipe or /enchant yourself.

They need Discord's Manage Server, or a Madsi team role with Bans once the owner turns on Moderators can use moderation commands on the Members page.

These three are slash commands only by default: a text prefix such as w!mc-ban gets a pointer to the slash command instead. Turn the text form on per command with its Text prefix switch on the Commands page.

On the feedback board, a comment with a link or a Discord invite waits for a quick review before it shows (links to madsi.link and dashboard.madsi.link, the docs included, post straight away); you see yours marked Waiting for review until then. Names that read as Madsi or its staff (Madsi, Umbrarity, staff, admin, moderator, lookalike spellings included) are reserved. A post's comments close once it ships, so open a new post for anything more. Every feedback email has a one-click unsubscribe, and your feedback profile sets which emails you get.

These commands run in-game with a leading slash, or at the server console without one (madsi status). The admin ones check a permission node on every loader: madsi.status for status, madsi.admin for setup, reconnect and update. A permissions mod or plugin (LuckPerms, or anything using fabric-permissions-api or NeoForge's permission API) can grant them to anyone. Without one, operators stand in: level 2 for status and level 4 for the rest on Fabric and NeoForge, any operator on Paper. The console can run them all. link, msg, r and whispers are open to every player.

Commands are available to all members by default, except /members, /mc-ban, /mc-kick and /mc-unban, which need Manage Server, or a Madsi team role with Bans once the server owner allows it on the Members page. Manage them on the Commands page in the dashboard:

• Restrict: limit a command to specific Discord roles and/or channels (leave both empty to allow everyone)
• Disable: toggle any command off entirely
• Aliases: give a command extra names (/newname works alongside the original)
• Prefixes: add text prefixes so w!profile works alongside /profile (Free 2, Basic 5, Pro 10). With none set, / works as a text prefix, so a plain message like /profile is answered too. /members, /mc-ban, /mc-kick and /mc-unban answer a prefix only once their Text prefix switch is on

Custom commands (Free 20, Basic 50, Pro 100) answer with a custom message you build on the Messages page: create one under Custom commands, give it a name, a description and any aliases, link the message, and optionally restrict it to roles and channels or mention the person who ran it. It works with your prefixes like the built-in ones, and as a slash command too when Slash is on: Free registers 2 as slash commands, Basic 5, Pro 10. A custom command's aliases work from a prefix only.

Most replies can be reworded on the Messages page, and so can the lines players see in Minecraft (whisper and in-game link notices), the moderation log, the applications and command builder logs, command alerts, the whisper-tracking lines, the review card's status line, buttons and headings, the prompts and buttons of an application answered in DMs, the /mccommands browser, /roadmap, /changelog and the console channel's replies. The { } button lists the variables that message can use: its own first (like {player_name} or {server_name} for the Minecraft server), then the ones that depend on where it's sent. A reply to a command also has the member ({user_mention}), the Discord server ({discord_server_name}) and the channel; a DM has the member and the Discord server; a post the bot makes on its own, like a join line or a health alert, has the Discord server, the date and time; a line shown in Minecraft has only {date} and {time}. {date} and {time} follow the timezone set on the Stats page. A variable a message can't fill is left as typed, and the preview shows it that way too. A whisper's text, a command's console output and the text of a logged or alerted command are kept private, so they can't go in a link, an image or icon address, or a line that has a link in it.

Some variables were renamed to say what they hold (for example {query} became {player_search}, {item_search} and so on, and {server_name} for the Discord server became {discord_server_name}). Messages you saved with the old names keep working.

The in-game /madsi admin commands need the madsi.status (status) or madsi.admin (setup, reconnect, update) permission on every loader. Without a permissions mod or plugin, operators have them: level 2 and level 4 on Fabric and NeoForge, any operator on Paper. They can also be run from the server console. link, msg, r and whispers are open to every player.