MineDown Formatting
The [Text](arguments) syntax SlateChat accepts in chat and in config files.
Every SlateChat config file — channel formats, /chatcolor messages, all of
it — accepts MineDown syntax
alongside plain MiniMessage
tags. Players can also type MineDown directly in chat.
Basic format
[Display Text](arguments)- Display Text — what shows up in chat
- arguments — colors, formatting, links, hover text, space separated
Automatic hover
Using a link or command always shows a hover — by default it's just the link/command itself, so players know what they're about to click before they click it.
| Written as | Shows | Hover shows |
|---|---|---|
[Click here](/kill) | Click here | /kill (automatic) |
[Visit](https://example.com) | Visit | https://example.com (automatic) |
Custom hover needs a permission
Adding your own hover text ([Click here](/kill Execute the kill command))
only works for players with chat.hover.bypass. Without it, the custom
text is ignored and the automatic link/command hover is shown instead.
Examples
Clickable link
[Visit our website](https://example.com)Shows "Visit our website", opens the site on click, hovers the URL automatically.
Clickable command
[Click here](/help)Shows "Click here", runs /help on click, hovers /help automatically.
Command with custom hover (needs chat.hover.bypass)
[View rules](/rules Click to see server rules)With the permission, hovering shows "Click to see server rules." Without it,
the automatic /rules hover is shown instead — the custom text is dropped
silently, not an error.
Hover only, no link
[Information](Hover for more details)Any argument that isn't a link or command just becomes hover text. No permission needed if there's no link attached.
Colors
[Colored text](red)
[Hex color text](#FF5733)Requires chat.colored
Solid colors, gradients and rainbow are silently ignored for players
without chat.colored — the text just falls back to whatever color
already surrounds it. Links, hover and plain formatting (bold, italic,
underline, strikethrough, obfuscated) still work regardless.
Formatting
[Bold text](bold)
[Italic text](italic)
[Underlined text](underline)
[Strikethrough text](strikethrough)
[Obfuscated text](obfuscated)Combinations
Arguments stack, space separated:
[Admin](red bold)
[Click here](green underline /warp spawn Teleport to spawn)
[Website](aqua https://example.com Visit our website!)Gradients
[Colored text](#FF0000-#0000FF)Rainbow
[Rainbow](rainbow)
[Slow rainbow](rainbow:50)Escaping
Prefix the [ with a backslash to show the raw syntax instead of triggering
it — handy when explaining the format to someone instead of using it:
\[Click here](/kill)This prints [Click here](/kill) as literal, non-clickable text.
Processing order
- The first argument starting with
/orhttp(s)://becomes the link or command - Anything after that becomes hover text
- Colors and formatting apply to the display text
- With no link at all, every unrecognized argument becomes hover text
Hover text is resolved outside of the click action, which is resolved outside of formatting, which is outside of color — in that order.
Common mistake
[/kill](Click here)This is backwards — it displays the literal text "/kill" and "Click here" never becomes clickable. The link/command always goes in the parentheses:
[Click here](/kill)In chat
Players can type MineDown directly:
Hello [everyone](yellow bold)! [Click here](/warp spawn Go to spawn)"Hello" renders as normal text, "everyone" comes out yellow and bold, and
"Click here" becomes clickable — running /warp spawn with a "Go to spawn"
hover.
Permissions
| Permission | Grants |
|---|---|
chat.hover.bypass | Setting custom hover text on links/commands, instead of the automatic one |
chat.colored | Using colors, gradients and rainbow (see Commands & Permissions) |
