# Messages

> Troubleshooting join/quit/kick/death/timed messages and broadcast conditions

- Skill: `kangarko/messages` (Agent Skill)
- Install (CLI): `npx skillmds@latest add kangarko/messages`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kangarko/messages/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/messages

---


# Messages Troubleshooting

## Common Mistakes

- **First-join detection trick: `{statistic_PLAY_ONE_MINUTE} == 0`** — misleading statistic name. It actually counts TICKS played, not minutes. Value 0 = never played before
- **Entity names changed in MC 1.20.5+** — `LIGHTNING_BOLT`, `TNT`, `END_CRYSTAL` (was `LIGHTNING`, `PRIMED_TNT`, `ENDER_CRYSTAL`). Death message `require cause` patterns must match the current MC version's names
- **`{killer}` is null for environmental deaths** — use `require killer` condition to guard against null. Commands with `{killer}` silently skip when null
- **`Stop_On_First_Match` ordering matters** — first matching message group stops all further groups. Place most specific groups (first-join, VIP) ABOVE default groups
- **Duplicate messages with permission-based groups (fallback path bug)** — when using `require sender perm` to create per-rank groups (premium, vip, default) and a player has inherited permissions matching multiple groups, `Stop_On_First_Match` correctly skips that player in subsequent groups' main loop. However, the sender-fallback path (`if !pickedMessage && wrappedSender != null`) can re-fire for later groups because it didn't check `messageReceivers`. **Fixed in PR #3513** — the fallback now checks `messageReceivers` when `Stop_On_First_Match` is active. If users report this on older versions, tell them to update.