Badges
Decorations earned once and worn on the profile. Some stick for good, others are re-read on every render and vanish the day the condition lapses.
In short
What is earned, what is worn
A badge is a profile decoration, not a perk: it changes no statistic, it says where the player comes from. The game counts seventeen of them today, and >badges opens the list of the ones already earned.
Every badge carries a rank, and there are four of them from the rarest to the most common. Only three are filled today: the last rank exists in the code, but no decoration sits there yet.
Earning is not wearing. The profile only shows nine slots, and the player picks which ones: >badges equips and removes, the rest of the collection stays visible but off the shelf.
Two origins live side by side: fourteen badges are granted once and for all and never leave, while the three others are re-read on every render. Those follow an account state, and they switch themselves off as soon as that state changes.
Four ranks, from the rarest to the most common
A rank is not chosen: it is written into the badge's own code and decides its color and its emoji. The 17 existing decorations spread out like this.
Rank only changes the trim: a legendary badge grants nothing a rare one does not.
An empty rank stays on show here: it says what the code plans for, not what can be earned.
Granted once, or re-read every time
Origin decides how long a badge lives: fourteen decorations are written into the player's inventory and stay there, while the three others are written nowhere and have their presence recomputed every time the profile opens.
| Origin | What it carries | Re-read every time | Can be lost |
|---|---|---|---|
| The running subscription and the team status | ✓ | ✓ | |
| Events, moderation, accepted suggestions | · | · |
A dynamic badge follows its state with no delay: a subscription picked back up brings it straight back.
Nothing warns about the loss. The badge leaves the profile, and it leaves the slot it was sitting in too.
What the badges screen shows
>badges fits in one message: the strip of worn slots, the list of everything earned, and a menu to swap one for the other. The 9 slots are numbered, and an empty slot says so.
🎖️ Badges
- Header
The screen title and the player's avatar, set side by side.
- The worn ones
The top strip only shows equipped badges, in slot order.
- A filled slot
The slot number, the rank emoji, then the badge name.
- An empty slot
All 9 slots are always listed, filled or not: the strip keeps its height.
- The collection
Below the strip, everything earned, rank by rank, with a mark on the ones being worn.
- The menu
One menu both equips and removes: picking a badge already worn puts it away, picking another sets it down. It only ever offers earned badges, never the 17 of the catalogue.
- Collections
`>badges collections` opens the view by series and also shows what is still missing.
The screen does not refresh on its own: every choice sends the whole message back, up to date.
The 9 slots fill from the first to the last, and a gap is plugged before anything goes further.
The moves you can make, and the one you cannot
A badge goes through four moments: it is earned, it is equipped, it is removed, and sometimes it is lost. The first ones come from the player, the last one comes from the game.
- An account condition is enough, with nobody stepping in.
- Or a team decision drops it into the inventory.
- The slot is not picked: the first free one takes it.
- With a full shelf, nothing swaps itself out: something has to come off first.
- The badge is never lost, it only leaves the shelf.
- The slot goes back to being free and will serve the next badge equipped.
- Neither the command nor the menu can hold it back.
- No message announces the departure: the profile simply stops showing it.
A granted badge comes off and goes back on as often as you like: the move costs nothing and never wears out.
The full list
The 17 badges in the game have a list of their own, with each one's art and condition.