# Chat Formatting > Troubleshooting format display, hover/click events, gradients, images in formats, and color permissions - Skill: `kangarko/chat-formatting` (Agent Skill) - Install (CLI): `npx skillmds@latest add kangarko/chat-formatting` - Raw SKILL.md: https://api.skillmd.com/api/skills/kangarko/chat-formatting/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: kangarko (https://skillmd.com/u/kangarko) - Updated: 2026-09-10 - Page: https://skillmd.com/skills/kangarko/chat-formatting --- # Chat Formatting Troubleshooting ## Common Mistakes - **Gradients are "unsafe"** — MiniMessage tags inside `Message` break gradient rendering. Use gradients only on plain text without inner color/format tags - **Only ONE `Run_Command` per format part** — Minecraft protocol limitation. Split into separate Parts if multiple click commands are needed - **Hover max 21 chars pre-1.13** — older versions truncate hover text. Use shorter text for compatibility - **`{player_prefix+}` vs `{player_prefix}`** — the `+` variant includes a trailing space. Without `+`, there's no separator between prefix and name - **`Message:` 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 below ## Images in Format Parts Format 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: ```yaml Parts: Welcome: Message: - " Welcome back to MyServer {player}" - " Your return is appreciated!" Image_Head: "{player_name}" Image_Height: 10 ``` Example — static image from file: ```yaml Parts: Logo: Message: "Welcome to our server!" Image_File: "creeper-head.png" Image_Height: 8 ``` The `/chc a image ` command is for **one-time broadcast announcements only** — it cannot be used inside format files. ## Inline Player Heads and Sprites via MiniMessage (`` / ``) Foundation ships Adventure 5.0.0, which adds two standard MiniMessage tags that work anywhere a format `Message` (or rule rewrite) is parsed: `` and ``. 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: - `` 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. - Players need `chatcontrol.tag.action.head` to use `` themselves (see `Colors.hasPermissionForTag`). Same pattern applies to ``, ``, ``, etc. - Because these are real standard tags, an unknown-tag rule rewrite like `[head:player] -> ` works — the previously raised concern that `` "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`).