Mailboxes

Mailboxes 1.5.1 For a server running v1.4.0, this is a drop-in upgrade covering 1.5.0 and 1.5.1, with no data migration. Several crashes and silent misconfigurations are fixed, and the plugin now checks config.yml every time it starts. Usage reporting now also sends a random server ID, and Minecraft 26.3 is supported. After the first start, check the console for warnings about config.yml: any invalid values listed there were replaced with defaults. Changes Configuration · On every start the plugin checks config.yml. A whole-number option set below 1 or to something that isn't a number, and a true/false option set to anything else, is replaced with its default, and a console warning names the option, the old value and the new one. For example, maxMessageIDNumber: 0 used to break the first /m send (#111). · /m config set now accepts only true or false (any case) for true/false options. Before, values like yes or 1 were saved as false while reporting success (#111). Fixes · New mailboxes no longer get a mailbox ID that is already in use. If random picks keep hitting taken IDs, the lowest free ID is used; if every ID is taken, the player is told to contact an administrator instead of an ID being reused (#121). · /m open with an ID that isn't a number now shows an "Invalid message ID" message instead of throwing an error (#115). Compatibility · Added support for Minecraft 26.3. Supported versions are 1.19.4, 1.21.11, 26.2 and 26.3 (#125, #116). Usage reporting · If usage reporting is on, the first start adds a random server-id: line, with a comment explaining it, to the end of plugins/trace/config.yml, and every usage event carries that ID so servers can be counted rather than raw events. The rest of the file is left as it is, and all plugins on the server that report to trace share the one ID. It identifies no person, account or IP address; delete the line to get a new one. If reporting is off, no ID is created, written or sent. (#122, #124) · Every event, including command events, now carries the plugin version (#118). · plugins/trace/config.yml accepts an optional tags: block added to every event from plugins on the server; for example, ci: "true" on a test server (#117). · The bundled usage-reporting client is updated to 0.6.1, and the usage-reporting details link in the startup message and config comments now points to https://danielstephenson.dev/usage-reporting. Existing config files are not rewritten. Included releases: 1.5.0 and 1.5.1 Download: https://github.com/Dans-Plugins/Mailboxes/releases/downlo… Full release notes: https://github.com/Dans-Plugins/Mailboxes/releases/tag/v1…

Mailboxes 1.4.0 A server on v1.3.0 can drop this build in without touching its data or existing configuration. Two things are new and visible: players get a /m stats command, and the plugin now reports anonymous usage events (plugin name, version, command names) to the author's trace server, on by default, with the switch written into config.yml on first start. Several long-standing crashes and message ID collisions are also fixed. Changes New commands · Added /m stats, which shows a player their total, active, archived and unread message counts. Guarded by the new mailboxes.stats permission, which defaults to allowed, and listed in /m help and tab completion. (#88) Usage reporting · The plugin sends a small event at startup and on each command use to https://trace.danielstephenson.dev. Nothing about players or the server is included; sending happens off the main thread and is dropped silently if the server is unreachable. (#105) · Reporting can be turned off per plugin with usage-reporting.enabled: false in config.yml, for every trace-reporting plugin on the server with enabled: false in plugins/trace/config.yml (created on first start), or for the whole process with TRACE_USAGE_REPORTING=off or DO_NOT_TRACK=1. The console states at every start whether reporting is on and, if not, why. (#105, #107) · An existing config.yml that lacks the usage-reporting block is rewritten on startup so the opt-out is visible on disk. (#107) Fixes · /m delete and /m archive no longer throw when given a non-numeric ID or when the player has no mailbox; they report the problem instead. (#90) · New messages no longer reuse the ID of an archived message, which could previously make an archived message unreachable or shadow a new one. (#97) · When random ID draws keep colliding, the plugin now sweeps for the lowest free ID instead of handing out one that is already taken. If every ID up to maxMessageIDNumber is in use, message creation is refused with a console error and the sender is told the message could not be created. (#100) · /m config set now rejects non-numeric, zero and negative values for maxMessageIDNumber, maxMailboxIDNumber and maxAttachmentStackSize instead of storing them; a zero or negative maxMessageIDNumber previously broke all message creation. (#102) · Help and usage text now shows the required (ID) argument for /m open, /m delete and /m archive, the accepted /m list types, double quotes around the message in /m send, and the correct /m config set usage. (#97) Upgrade notes · Usage reporting is on by default. If you do not want it, set usage-reporting.enabled: false in plugins/Mailboxes/config.yml, or set enabled: false in plugins/trace/config.yml to turn it off for every plugin that reports to trace. Both files are created or updated on first start of this version. · mailboxes.stats defaults to allowed. If you manage permissions with an explicit allow-list, add it for players who should see /m stats. Download: https://github.com/Dans-Plugins/Mailboxes/releases/downlo… Full release notes: https://github.com/Dans-Plugins/Mailboxes/releases/tag/v1…

This release focuses on usability and polish, making Mailboxes faster to use and easier to navigate. Highlights · Tab Completion for Commands & Arguments Commands are now easier and faster to use with intelligent tab completion. · Paginated /m list Command Large mailbox lists are now split into pages with clickable navigation. · Enhanced Mailbox UI Message IDs are now clickable, with added action buttons for quicker interaction directly from the UI. Full Changelog View the full diff between v1.2.0 and v1.3.0

What's Changed · Architecture refactor: Moved away from the Singleton pattern to improve flexibility, testability, and long-term maintainability. · New feature: Added support for item attachments in mail messages, allowing mail to include items directly. Full Changelog v1.1...v1.2.0

Changes in Mailboxes v1.1 · Added an API call to the external API. · Informed players how many unread messages they have, not just that they have some. · Fixed archived and unread messages not getting listed simplistically like active messages when specified in the /m list command. · Fixed messages getting cut off if an apostrophe was used. Players will now be required to designate messages between double quotes.