القائمة
Troubleshooting format display, hover/click events, gradients, images in formats, and color permissions
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Troubleshooting rule matching, replace vs rewrite, groups, and rule processing order
Troubleshooting channel system: messaging, range, modes, proxy, and Discord linking issues
Troubleshooting /tell, /reply, /ignore, PM formatting, social spy, and mail delivery
Troubleshooting command spy, transaction logging, and database log browsing
Troubleshooting Boss commands, PAPI placeholders, and permission issues
Troubleshooting timed announcements, MOTD, books, images, and scheduled broadcasts
| name | chat-formatting |
| description | Troubleshooting format display, hover/click events, gradients, images in formats, and color permissions |
Message break gradient rendering. Use gradients only on plain text without inner color/format tagsRun_Command per format part — Minecraft protocol limitation. Split into separate Parts if multiple click commands are needed{player_prefix+} vs {player_prefix} — the + variant includes a trailing space. Without +, there's no separator between prefix and nameMessage: does NOT execute commands — it only displays text. Users sometimes put /chc a image ... inside a Message: value expecting it to render images — it will print the command text literally. To show images in format parts, use the dedicated image keys belowFormat parts support showing images alongside text using these keys:
| Key | Purpose | Example |
|---|---|---|
Image_File | Image from the images/ folder | creeper-head.png |
Image_Head | Player head from avatar API | "{player}" or "Herobrine" |
Image_Url | Image from a remote URL | "https://example.com/logo.png" |
Image_Height | Height in chat lines (default: 8, min: 2) | 10 |
Image_Type | Filler character style | BLOCK, DARK_SHADE, MEDIUM_SHADE, LIGHT_SHADE |
Only one image source allowed per part — you cannot combine Image_File, Image_Head, and Image_Url in the same part.
Example — player head image in a MOTD format:
Parts:
Welcome:
Message:
- " Welcome back to MyServer {player}"
- " Your return is appreciated!"
Image_Head: "{player_name}"
Image_Height: 10
Example — static image from file:
Parts:
Logo:
Message: "Welcome to our server!"
Image_File: "creeper-head.png"
Image_Height: 8
The /chc a image <file> <height> <message> command is for one-time broadcast announcements only — it cannot be used inside format files.
<head:> / <sprite:>)Foundation ships Adventure 5.0.0, which adds two standard MiniMessage tags that work anywhere a format Message (or rule rewrite) is parsed: <head:name|uuid|texture[:outer_layer]> and <sprite:[atlas:]sprite>. They render as native vanilla "object" chat components, so they need a client on MC 1.21.9+. On older clients they fall back to plain text.
These are NOT custom Foundation/ChatControl resolvers, they come from TagResolver.standard(). So:
<head:Notch> inline in a chat format Message renders Notch's head next to the text on supported clients. Different rendering from Image_Head (the format-part key), which draws an 8-line ASCII block from the skin texture and only sits beside text, not inside it.chatcontrol.tag.action.head to use <head:> themselves (see Colors.hasPermissionForTag). Same pattern applies to <sprite>, <click>, <hover>, etc.[head:player] -> <head:player> works — the previously raised concern that <head> "gets dropped silently by MiniMessage" is wrong on Adventure 4.25.0+.When asked whether a MiniMessage tag exists, do not assume from memory. Check the current Adventure standard tag list (https://docs.papermc.io/adventure/minimessage/format/) — the standard set grew in 2025 (pride, sprite, head, shadow).