BungeMessages

Added

• /bmsgs list is paged. Listing every message printed all 50 at once and pushed the rest of the chat off the screen; it now shows ten per page, with list-page-size to change that.
• /bmsgs get <key> shows a single message without listing everything.
• Tab completion for the subcommands, and for the message keys after get.
• A settings section: inject-translations, intercept-hardcoded, restore-on-disable, metrics, debug and list-page-size.
• Separate permissions per subcommand (bungeemessages.use, .reload, .info, .list), with bungeemessages.admin still covering all of them.
• {2} in plugin.info, the number of translation keys actually injected.
• Anonymous usage statistics through bStats, switchable in the config.

Changed

• Config updates are merged instead of ignored. New options are written into your existing config.yml on first start, and your own texts are left untouched. A config from an older version previously just lacked the new keys.
• BungeeCord's original messages are handed back when the plugin unloads. Before, an unload left the proxy speaking the plugin's texts until the next restart.
• The plugin is split into packages by responsibility instead of one class.
• The login handler calls getReason and setReason directly instead of looking them up by reflection on every event.
• The message table is now searched for up the class hierarchy, so proxy forks that subclass the server class are handled.
• The "Login timed out" rule is checked before the shorter "Timed out" rule, so the more specific match wins regardless of casing.

Fixed

• One bad message could silence all the others. A text containing a brace that is not a {0} style placeholder, such as {name}, made MessageFormat throw, and that aborted the whole injection: all 44 translated messages fell back to BungeeCord's defaults with only a stack trace in the console. Now the offending key alone is skipped, and the console names it.
• A config.yml with no messages section loaded silently. The check for it could never fire, because a missing section reads back as an empty one rather than as nothing, so the plugin started with zero messages and said nothing.