💬 PolaroidChat
A chat plugin for Paper 1.21+. It gives players a nick, a colour, channels to talk in, and a menu to set it all from — and gives you every word, item and colour of that in a config file.
Where to go
Setting it up
| Page | What is in it |
|---|---|
| Install | Getting it running, what each file is for, where data is stored |
| Permissions | Every node, and the tier system that grants slots by rank |
What players do
| Page | What is in it |
|---|---|
| Commands | Every command and its alias |
| Colours & nicks | The four palettes, custom colours, history |
| Channels | The four channels, and the ones players make themselves |
| Writing a message | Emoji, sprites, mentions, and sharing an item in chat |
Changing how it looks
| Page | What is in it |
|---|---|
| Chat formats | How a message is built, per rank |
| Menus | The menu files and the templates they cut items from |
| Messages | The language files and the Polaroid style |
The rest
| Page | What is in it |
|---|---|
| Staff tools | Announcements, the private-message spy, clearing chat |
| For developers | Placeholders, the API, events, supported item plugins |
The five-minute version
- Drop the jar in
plugins/, start the server once. - Give players
polaroidchat.menuandpolaroidchat.colors.hex. - Have them run
/chat.
Everything else is optional. The defaults work.
How the config is arranged
Two ideas run through every file, and knowing them makes the rest read quickly.
A shape is written once. Where several entries would say the same thing — the five ways a
notification can reach a player, every interactive keyword, every history list, every colour
swatch — the shape is written once and each entry names only its difference. In config.yml
those blocks are notifications, interactive.defaults and history.defaults; in the menus it
is menus/templates.yml.
Every word a player reads is in a file. Nothing is hardcoded, including the prefix. If you can see it in game, you can change it without touching the jar.