Community

Feedback, announcements, Discord, events, referrals, voting and the handbook.

Feedback and global coins #

Feedback and global coins:

  • /feedbacks lists open forms. Anyone can browse, but only signed-in, verified players (Minecraft account linked, email confirmed) can respond, once per form.
  • Staff build forms (Feedback, permission feedback.manage). Question types: short or long text, 1–5 rating, single or multiple choice, and yes/no. Each form can have open and close dates, a response limit, and a draft or open status.
  • On the responses page, staff can read each answer and see average ratings.
  • Rewards need coins.grant. A form can pay global coins automatically on submit, staff can reward individual responses, and staff can give or take coins on a player's page.
  • Global coins are one network-wide balance with a full transaction history, shown on the player's portal account. Players are told in-game when they receive coins.
  • In-game: /coins shows the balance. Stores call GlobalCoins_Spend(player, amount, reason, "console command with {player}"). The command only runs after the panel has taken the coins, and the spend is atomic (POST /server/coins), so the same coins can't be spent twice.

Announcements and news #

Community > Announcements and news (/announcements, permission announcements.manage): write something once and pick where it goes. One table (announcements) with a type, so both share the editor, scheduling and sending (App\Services\AnnouncementPublisher):

  • Announcement: short and urgent. It can be pinned as a banner at the top of portal pages (or, with "Show to: Staff panel", a banner for staff only that goes nowhere else), has a banner colour and an optional end date, after which it stops showing everywhere.
  • News: an article, kept for good. Pinning keeps it at the top of the news.

Each has a title, a short summary (used in lists, the banner, chat, Discord and search engines; without one, the start of the text), the text in Markdown, a category, up to 10 tags, a header picture and an author ("Shown as written by", or the staff member's name). Add a picture to the text uploads it and puts ![name](url) where the cursor is. Pictures are stored under public/news-images/ (no storage link needed) and deleted with the post.

When: publish now, schedule for later, or save as a draft (only staff see it). Preview opens the article as players will see it in a new tab without saving. Staff with the permission can also open drafts and scheduled posts at /news/{slug}.

Where it goes (checkboxes):

  • Player portal: /news (cards, filter by type and category, 12 a page) and /news/{slug}. Temporary accounts can read it. Players hide a banner with Hide; the browser remembers that in a cookie, so it works for guests too.
  • Public website: pushed to the main website with everything else (see Main website); the site has /news, /news/{slug} and the Atom feed /feed.xml. When the website is set up, in-game and Discord links go to the website's page, and the portal's page names it as the canonical address.
  • In-game chat: once, when it goes live, to the players online on every server or the game modes and servers picked under "In-game: which servers". It goes through the action queue the servers poll (a broadcast with a news part); core/Http/QueueSync.sk shows the title, summary and a clickable link in each player's language (msg.news.*). On an edit, "Broadcast it in-game again" sends it once more. Players can type /news for the latest five.
  • Discord: once, when it goes live, as an embed (title linked, summary, picture, category, author, orange for announcements and blue for news) to every webhook in Settings > Discord that takes Announcements or News articles. Sent by the queue with 3 tries; the message ids are kept, so saving an edit updates the messages (or posts it again, or leaves them), and deleting the post deletes them. Send / Re-send to Discord on the list posts it again. If a message was deleted in Discord, an edit posts a new one.

Scheduled posts go out within a minute of their time (network:publish-announcements, Tasks). Every create, edit, delete, picture upload and Discord re-send is in the audit log (announcement.*). Updates log is separate: it's the changelog of what changed in the game, per server. In-game broadcast is a one-off chat, title or action bar message.

Site icon: upload a PNG/ICO/WEBP in Settings; it is used as the favicon and in the header. Settings saved under a different APP_KEY no longer break the page ("The MAC is invalid"): they show as unreadable and can be entered again.

Feedback forms #

Feedback forms. Questions are added and removed on the page (one row at a time, nothing to save first). Rewards are a list: global coins, set a per-player global value (only values that exist and are per-player), and/or a badge. Responses can also be rewarded later with coins and a badge.

Join webhooks #

Join webhooks. Tick Player joins or New players on a Discord webhook (Settings → Discord webhooks), and word the messages under Join messages with {player}, {server} and {online}. One player shows at most once every 5 minutes, so moving between servers isn't a new join.

Discord #

Discord (Settings → Discord). The bot is an interactions endpoint, so no bot process needs to run. Set the application's Interactions Endpoint URL to /api/v1/discord/interactions, fill in the IDs and keys, then Register bot commands (or php artisan discord:register). Register again whenever commands are added. Setting it up in the Discord developer portal (discord.com/developers/applications → your application): copy the Application ID and Public Key from General Information into Settings → Discord, and the Token from Bot (Reset Token) into Bot token; put the server's ID in Server (guild) ID so commands show up straight away (without it they're global and take up to an hour). On General Information, set Interactions Endpoint URL to https://<your panel>/api/v1/discord/interactions and save: Discord checks it right away, so the panel must be reachable over public HTTPS with the public key already saved (Settings → Discord lists the latest requests and why any were refused). Invite the bot with OAuth2 → URL Generator, scopes bot and applications.commands (add Manage Roles if you use the linked or Premium roles), then press Register bot commands. Players can also use Link with Discord on the portal (OAuth). Linking can give a Discord role, and Premium players can get one too (see Discord Premium roles).

Command Who What it does
/link, /unlink everyone /link gives a code to type in-game with /discord <code>
/profile [user] [player] everyone A Discord user who has linked, a Minecraft username, or yourself. Public profiles only
/online everyone How many are playing, per server
/servers everyone Every enabled server, up or down, and who is on it (first 20 names each)
/balance linked Your global coin balance (only you see it)
/vote everyone Vote links; linked players also see their streak and when each site is ready again
/leaderboard <board> everyone Top 10 of a public, enabled leaderboard (names are suggested as you type)
/boss <name> everyone A boss from the boss lookup (names are suggested as you type): health, damage, armour, speed and size, special attacks in words, how it's summoned, the dungeons it appears in and its rewards with chances, linking to its part of /bosses on the portal. Bosses hidden from the lookup aren't found (see Network gameplay → Bosses, "Boss lookup")
/report <category> <reason> [player] linked Files a report like the portal does (source "discord"). Same limits: no reporting yourself, at most 5 waiting
/punish <type> <player> <reason> [duration] staff Kick, warning, mute or ban. Duration for bans and mutes: 30m, 12h, 7d, 2w or permanent (the default). Needs punishments.kick, .warn, .mute or .ban
/unpunish <ban|mute> <player> [reason] staff Lifts the active ban or mute. Needs punishments.revoke
/history <player> staff The latest 10 punishments, active ones marked. Needs punishments.view
/lookup <player> staff Online or last seen, rank, first join, linked Discord, active punishments, open reports. Needs players.view

Staff commands act as a panel account: the asker's Discord must be linked to a Minecraft account, and that account must belong to an active staff account (its Minecraft UUID, or the portal account that player uses), whose role has the permission. Punishments and lifts are recorded and audit-logged exactly as from the panel, under that staff member's name. Replies to staff commands, /balance, /vote and /report are only shown to the person who asked. Discord hides staff commands from members without Kick Members by default; change who sees them under Server Settings → Integrations. Panel sign-in protections such as two-factor don't apply in Discord, so keep staff Discord accounts secured.

Discord notices to players #

Discord notices to players (Settings → Discord → Notices sent to players). The bot DMs players who linked Discord when:

  • someone messages them (portal chat or in-game /msg), at most once per sender every 10 minutes;
  • they get a ban, mute, kick or warning, or one is lifted;
  • staff change their rank, settings, global coins, badges, pets, saved data or a player value;
  • staff take down one of their marketplace listings;
  • their staff application is accepted or rejected.

Staff tick which kinds go out (all are on by default). Players can turn off Discord: new messages and Discord: account notices in their portal settings. The bot can only DM someone who shares a server with it and allows DMs. If a DM fails, the bot pings the player in the fallback channel instead, when you set one (the bot needs to be able to send messages there). The last 10 deliveries and their results are shown under the settings. Notices are sent by the queue worker, so queue:work must be running.

Staff request alerts #

When a player sends something for staff to handle, staff hear about it straight away (App\Services\StaffRequestAlerts). It covers every kind of request:

  • Player reports (staff with reports.view)
  • Appeals (appeals.manage)
  • Staff applications (applications.manage)
  • Job change requests (jobs.requests)
  • New crews to approve (crews.manage)
  • Age verification applications (age.manage; only that one is waiting, never the player's name or details)
  • Feedback form responses (feedback.manage)
  • Program applications (programs.manage)

Each one goes to:

  • The staff Discord channel: every webhook with Staff requests ticked (Settings > Discord webhooks). The older New player reports and Age verification events still work on their own.
  • Discord DMs: the bot DMs each active staff member whose role has that permission and whose account is linked to a Minecraft account with Discord linked. Needs the bot token (Settings > Discord bot).
  • In game and on the portal: the same staff get a staff notice (&6&lSTAFF), in chat if they're online and in their portal notifications, with a link to the staff page. Staff notices can't be muted.

Settings > Staff request alerts chooses which kinds are on and where they go (all on by default). A notice that can't be sent never stops the request itself.

Discord Premium roles #

Discord Premium roles (Settings → Discord, settings.manage; App\Services\DiscordRoles, job SyncDiscordRoles). Players with Player Premium get the Role for Premium players on the Discord account they linked, and members of a Crew: Premium crew get the Role for members of Crew: Premium crews. Both are optional and use the bot token and Server (guild) ID above. Leave a role ID empty to turn that role off; anyone who had it from the panel loses it at the next check.

Setting up in Discord:

  1. Add the bot to your server (OAuth2 → URL Generator, scope bot) with the Manage Roles permission.
  2. Create the Premium role (and the Crew: Premium role, if you want one). In Server Settings → Roles, drag the bot's own role above them; a bot can only give roles below its highest role.
  3. Turn on Developer Mode (User Settings → Advanced), right-click the server for its ID and each role for its ID, and paste them into Settings → Discord.

When roles change:

  • Premium given, extended, taken away or refunded (anything that goes through PremiumService::refresh): that player's role is checked straight away.
  • Crew: Premium set, bought, extended or ended, and a player joining, leaving or being removed from a crew, or the crew disbanding.
  • Linking Discord gives the roles; unlinking (portal or /unlink) takes them off that Discord account. Linking a different account moves them.
  • Saving a different role or server ID moves everyone over at once: the old role is taken off and the new one given.
  • Premium that runs out on its own: task discord-premium-roles (php artisan discord:premium-roles, every 15 minutes) finds linked players whose roles don't match their Premium.
  • Task discord-premium-roles-all (discord:premium-roles --all, daily at 04:30) and the Sync Premium roles now button check everyone who has or should have a role. That fixes roles added or removed by hand in Discord, and gives roles to players who have since joined the Discord server. The button is in the audit log (settings.discord_roles_sync).

The panel keeps which role it last gave each player (players.discord_premium_role and discord_crew_role, as guild:role), so it only calls Discord when something changed. Calls go through the queue worker (queue:work --queue=urgent,default). A rate limit (HTTP 429) waits as long as Discord asks and tries again; Discord being down is retried 3 times, for up to 6 hours. A linked player who isn't in the Discord server is fine: they get no role (players.discord_not_in_guild_at is set) and are tried again by the daily check, the button, or when they link again. Setup problems such as Missing Permissions (no Manage Roles, or the bot's role is below the Premium role) or Unknown Role aren't retried; they're shown with the last 25 role changes under Premium roles on Settings → Discord. Changes to the Discord settings are audit-logged (settings.discord) with which fields changed and, for IDs, the old and new values; secrets only say they changed. The older Role for linked players is separate and works as before.

Updates log #

Updates log (public at /updates-log; staff at /manage/updates, permission updates.manage). Each post has a title, type (New, Improved, Fixed, Balance, Event, Maintenance), the text, a date and time, and what it applies to: tick whole categories (server groups), single servers, or nothing for every server. Posts can be drafts, or scheduled for later. Players filter the page by game mode and type. Each post goes to Discord webhooks that have Updates log posts ticked (Settings → Discord webhooks), so a channel can get only updates. Scheduled posts are sent when their time comes (the publish-updates task).

Referrals #

Players bring friends with a code (Community → Referrals, permission referrals.manage; players see theirs in-game and under You → Refer a friend on the portal).

  • In-game (network/Economy/Referrals.sk): /refer (aliases /referral, /referrals) shows the player's own code (6 letters and numbers, made the first time and kept), how it works and how many friends they've brought. A new player types /refer <code>.
  • Who can use a code: only players who first joined within a set number of days (7 by default), once each, never their own or that of someone who joined with theirs, and (on by default) not from an IP address the code's owner has used, so alts don't count.
  • When the referrer is rewarded: once the new player has played a set number of minutes since using the code (60 by default), optionally after some days and once they've linked their account on the portal. Checked every minute (task referrals); the rewards are given the next time the referrer is online, and they're told in chat. A referral is rejected if the new player is banned first, or when the referrer has reached the most rewarded referrals (0 = no limit).
  • Rewards use the shared reward list (global coins, badges, global values, console commands, custom items) for the referrer, and optionally for the new player straight away.
  • Staff see every referral with its status, approve one now (skipping the conditions) or reject it, and the top referrers. Changes are in the audit log.
  • API: POST /api/v1/server/referrals (info, use). Tables referrals, players.referral_code.

Player handbook #

/handbook (alias /guide) in-game and Help → Handbook on the portal: how to play, a page per system, in sections (getting started, the Pit, Survival, Tag, progress, money, friends and crews, cosmetics, events, account, rules) plus All commands.

  • Written with the panel. The pages are in app/Support/Handbook.php, so deploying the panel updates every server's /handbook within a minute (its version comes with the group sync). php artisan handbook:scan lists every player command in the scripts into config/handbook_commands.php, and All commands is built from that and the panel's global commands. HandbookTest fails when a player command has no page (or isn't in Handbook::INTERNAL for staff-only ones), so a new system ships with its page.
  • Only what's there. Each server tells the panel which script folders it has (pit, tag, survival...), and pages can also need a game rule (marketplace, jobs, pets, envoys) or classes being on. The portal shows every page, marked with the game mode it's for.
  • Staff changes (Community → Player handbook, permission handbook.manage): change any page's or section's words, hide pages or sections, add pages of your own. Words left as written keep updating with the panel; changed ones stay. Every save is in the audit log.
  • Languages. Translate it under Cosmetics and text → Translations, page "Player handbook". Players get their language; anything not translated yet is English.
  • In-game (network/Panel/Handbook.sk): on modern servers /handbook opens a book: the contents, then a book per section whose first page lists its pages (click to turn to one), each page's commands clickable into the chat box. The panel lays the text out over book pages so nothing runs off the bottom. 1.8 (Pit) can't open books, so it's clickable chat there, like /quests; /handbook chat gives the chat version anywhere. /handbook <section> [page] and /handbook search <words> work in chat. Links are sent in both the 1.8 and the 1.21.5+ chat format. New players are pointed at /guide once, 20 seconds after their first join. The last copy is kept if the panel is down.
  • API: GET /api/v1/server/handbook?uuid=&folders=.

Voting #

Players vote for the network on server lists, like Top Eagler Servers, and get rewards (Community → Voting, permission votes.manage). Every server, Pit included.

  • Vote sites. Staff add each list: its name, the vote link players open ({player} is filled in for lists that take the name in the link), how often a player can vote there (default every 24 hours), and how a vote is confirmed. Clicking the link doesn't count: only a vote the list confirms does, and each player is rewarded once per site until its wait time is up. Votes before then are recorded as "too soon".
  • Confirming votes, one per site:
    • Votifier (Top Eagler Servers and most lists; Top Eagler Servers has no vote check API or postback, only Votifier). The panel runs its own listener: php artisan votes:listen on the panel's server (default port 8192, set on the Voting page). Keep it running with a process manager (systemd, Supervisor, NSSM on Windows) and open the port. On the list, enter the panel's host and port, plus the token (v2 / NuVotifier) or public key (v1) from the Voting page, and the site's "Votifier service name" must match the name the list sends. Votes from unknown service names are listed on the Voting page so staff can fill the name in.
    • Callback link. For lists that call a webhook: each site gets a secret link /api/v1/votes/<id>/<secret>?username=<name> (GET or POST; username, player, user, name and a few others work). "Make a new callback link" changes the secret.
    • Vote check. For lists with a "has this player voted?" API: a check link ({player}, {uuid}) and the text that means yes (default 1), plus an optional claim link. The panel asks when the player types /vote.
  • Rewards. One list for every vote (a site can have its own instead): network currency, badges and global values are given straight away; in-game money, XP, items, console commands ({player}), custom items and messages ({player}, {site}) wait until the player is on a server — handed over at once if they're online, otherwise when they next join. Streak rewards (optional): days in a row with a vote on any site, e.g. "day 7, every 7"; given with the first vote of the day. "Send a test vote" on the Voting page acts like a real confirmed vote.
  • Announcements. Optional in-game broadcast for every vote ({player}, {site}), and the Discord webhook event "Player votes".
  • Top voters this month (on unless staff turn it off): on the Voting page, in /vote, on the portal, the main website and WordPress.
  • Players. /vote (network/Economy/Vote.sk) lists each site as a clickable link (tellraw, so it works on 1.8), whether they can vote again yet, their streak and the top voters. The portal's Vote page (/account/vote) has the links and their vote history. The main website gets a Vote page with the links (pushed with the rest), and WordPress has [neutine_votes top="yes"] (GET /api/v1/site/votes).
  • Wiring. POST /api/v1/server/votes (list, claim); the panel tells the player's server with profile_update {votes: 1} (Portal.sk calls Vote_Arrived). Tables vote_sites, votes; settings votes.config, votes.votifier_*.

Quizzes #

Quizzes (Community → Quizzes, /manage/quizzes, permission quizzes.manage; network/Chat/Quiz.sk). Every so often a question is asked in chat; players answer in chat and win rewards. Off by default: tick "Quizzes on" under Settings. "Ask now" asks one straight away, even while they're off.

  • Questions. The question (one line, & colours work), one or more accepted answers (capitals, colours and spaces at the ends don't matter) and optionally 2 to 6 choices for multiple choice, shown as A) B) C)...; players can type the letter or the choice. Each question says who wins: only the first correct answer across the whole network, or everyone who answers correctly in time, optionally only the first N. Questions can be turned off, ordered, and copied or imported as JSON (kind quiz-question).
  • Settings. How often (minutes from the start of the last quiz), seconds to answer, random (never the same twice in a row) or in order, and where: ticked categories and single servers, or every server when nothing is ticked. Only online servers get the question.
  • Rewards. The same reward rows as elsewhere: network currency, badges, per-player global values and blessings are given by the panel; in-game money, XP, items, console commands ({player}), custom items and messages ({player}) are handed over on the server the player answered on. Questions use the rewards set on the Quizzes page unless they have their own.
  • In game. The question, the choices, who wins and the rewards are shown in chat. A message that is a correct answer is hidden from chat (so it can't be copied) and sent to the panel, which decides who wins, so "only the first" holds across servers. The winner is told what they got; when the quiz is won, has all its winners or the time is up, every server shows the answer and the winners.
  • Wiring. The network:quizzes task (every minute) asks a quiz when it's due and closes old ones; it sends queue action quiz ({event: start} and {event: end}) to the chosen servers. POST /api/v1/server/quiz (answer, result). Answers are accepted for 15 seconds after the time limit, for servers that got the question late. Tables quiz_questions, quizzes, quiz_winners; setting quizzes.config. Changes are in the audit log as quizzes.*.

Staff applications #

Staff applications (Administration → Staff applications, needs applications.manage): staff add positions (Helper, Builder...) with a description, requirements and their own form (the same question types as feedback forms), open or closed. Players apply on the portal at /apply (they need a linked Minecraft account); one application per position at a time, and after a rejection they wait the position's "days before applying again". Staff review each one (waiting, being reviewed, accepted, not this time) with a note the player sees and private staff notes; the player is told in-game. A position can give a staff role on acceptance, but only when the reviewer can manage staff. Applications keep the questions as they were asked, so editing a form later never changes them.

Programs #

Programs (Community → Programs, /manage/programs, permission programs.manage; App\Services\ProgramService): programs players apply to join, like a YouTuber, Streamer or Builder program. Players see the open ones on the portal under Help → Programs (/programs).

  • Setting one up (Add a program): a name, what it is and the requirements players read (Markdown), the form (the same question rows as staff applications and feedback forms), and open or closed. Optionally:
    • Automatic requirements: the same conditions as discount codes (level, playtime, days since joining, age verified, Discord linked, votes, badges...), all or any one of them. Players can only send the form once they meet them; the application page warns staff if an applicant no longer does.
    • A rank and a role given on acceptance. Only staff with ranks.manage choose the rank, and only staff with staff.manage choose the role. The role is only given when the reviewer can manage staff and the player's portal account has no role yet (an account has one role, so staff keep theirs; the decision message says when it wasn't given).
    • A profile tag (e.g. YouTuber), shown on members' public profiles.
    • Members' perks: recurring perks, the same as a rank's or role's (Players → Perks; see Perks on the Players and the portal page). Only staff with perks.manage change them; others see them read-only.
  • Applying: players need a linked Minecraft account; one open application per program, and after a rejection they wait the program's "days before applying again". Every new application tells staff (Staff request alerts, kind Program applications).
  • Reviewing (the program's page, or Applications on the Programs page): waiting, being reviewed, accepted or not this time, with a note the player sees and private staff notes; the player is told in game. Accepting makes them a member, gives the rank and role, and gives any perks due straight away.
  • Members (the program's page): who's in, since when and who added them, and past members. Remove (with an optional reason) takes back the rank and role joining gave (the rank stays if another program they're in gave it too), stops the program's perks and tells the player; what they were given stays. A program with members can't be deleted.

Creating, editing, deciding, adding and removing members are all in the audit log.

Link reminder (Settings → Link reminder): a message with & colours ({player}, {portal}) and an optional clickable line, shown to players who haven't linked their Minecraft account to the portal, a set number of seconds after joining and then every N minutes (0 = once). It stops as soon as they link. A staff account given the player's Minecraft UUID (on its invitation or the Staff page) counts as linked too. Servers only remind players the panel has said aren't linked: if the panel couldn't be reached when they joined, there's no reminder that visit.

Events #

Events (Community → Events): a start and end time, the categories or servers it runs on, what to do (any quest objective, requirements included, or nothing at all: just play there while it's on), rewards (optionally only for the first N players) and a blacklist of usernames. Progress counts only during the event and only on its servers. Players see events with /events and on /events on the website, and are told 5 minutes before, at the start and at the end.

Main website #

Administration > Website (website.manage) runs the main site (laravel-app/neutine-site): its address and push secret, name, logo, accent colour, home page sections, banner, footer links and pages (Markdown). It's pushed to the site's /api/sync, signed with HMAC-SHA256 over timestamp.body, on each save, whenever updates, partners, events or store products change, and hourly (website:push). Only updates from the last N days are sent (30 by default). Announcements and news ticked for the website are sent too (all live ones, up to 200), and a push follows each one published, edited or deleted. To serve neutine.net from this site instead of WordPress, point the domain at laravel-app/neutine-site (its README has the set-up), set its address under Administration > Website and press Push now; old WordPress post addresses can be redirected to /news/{slug} in the web server. Player stats, leaderboards and status the site reads live with a site.read token (/api/v1/site/players/{name}/stats, .../history, stat-leaderboards).

Partners #

/partners lists the network's partners for anyone, signed in or not. It is linked from the footer and from Community in the player menu. Visitors can filter by tag, and only tags on a visible partner are offered.

Community > Partners (partners.manage, owners only until you add it to a role) adds, edits, reorders, hides and deletes partners. Manage tags there adds, renames, colours and deletes the tags. Deleting a tag takes it off its partners and leaves the partners alone. Every change goes in the audit log as partners.*.

Each partner has a name, a description (plain text), an optional logo, any number of links up to 12, a Discord invite and tags. Links must be http or https, Discord invites must be discord.gg or discord.com/invite, and logos are PNG, JPG, GIF or WebP up to 1 MB, never SVG. Logos are saved in public/branding/partners, so include that folder when moving the panel to another machine.

Repeating announcements #

In-game broadcast > repeating announcements (broadcasts.send) sets up messages that go out on a timer, in chat, as a title or on the action bar. Each can be turned off for chosen categories and servers; ticking a category also covers servers added to it later. The network:repeat-broadcasts task checks every minute and sends them as ordinary broadcast queue actions, so servers need no script update and cron must be running.

Servers that are offline or disabled are skipped and don't catch up later. Queue rows from these are deleted after 7 days by network:prune, and they stay out of the Recent announcements list.

Rewards #

Rewards (Community → Rewards, /manage/rewards, permission rewards.manage; network/Social/Inbox.sk). Send rewards to players' /inbox: global coins, a badge, a per-player global value, a console command, a custom item or a blessing (for its usual length or a number of minutes), with a title and an optional message. Who gets it: one player, a list of players (one per line or separated by commas), everyone who has played on a server, everyone who has played in a category, or everyone, optionally only players who linked their portal account, have Premium, are online now, or were seen in the last so many days. Who gets it is worked out when it's sent: players who join later don't. Where: any server, any server of one category, or one server; elsewhere the reward shows in the inbox with where to claim it. Optionally it expires after some days. Players click it in /inbox to claim it; it's given then, on the server they're on (commands and items run there), once. Online players are told straight away, others when they next join. Each reward's page shows who has claimed it, where and what they got, and Cancel reward takes it out of the inboxes of those who haven't. Sending and cancelling are in the audit log.

Rewards for linking an account (same page). When on, a player who links their Minecraft account to the portal with /link gets these rewards in their inbox, once per player ever: unlinking and linking again gives nothing more. Accounts staff link by hand don't get it.