Repository navigation
NullBrand 2.0.1
NullBrand 2.0.1
A corrective update to 2.0.0 covering branding state, permissions, configuration safety and platform integration. Existing profiles, animations, favicons, counts and configuration keys remain available.
What's Changed
- Upgrade to stable Velocity 4.2.0 and Paper 26.3 build 194 APIs; update SnakeYAML 2.0 to 2.7, privately relocated with license attribution.
- Implement API reload; avoid idle animation work, repeated engine allocations and accumulating logger handlers. No load-test performance claim is made.
Bug Fixes
- Restore ping cooldown recovery and bound its cache to 16,384 IPs; rejected attempts no longer extend the cooldown.
- Correct maintenance profile selection, atomic toggling, static/per-profile fake counts, explicit disabled overrides and numeric overflow.
- Fix truncated hex input, mixed legacy/MiniMessage formatting and named colors on Paper/Velocity.
- Isolate platform-specific listeners, process Paper pings once, and fix displayed counts and player-count hover text.
- Preserve the working configuration when reload parsing fails.
Security Improvements
- Individual management permissions no longer grant administrator access; platform entry points honor independent permissions.
- Use safe YAML construction, reject duplicate keys/object tags, limit aliases/input size, and omit configuration contents from parse errors.
- Restrict favicon paths/symlinks to the favicon directory; validate the 1 MiB limit, PNG format and 64×64 dimensions before decoding. Image I/O stays outside ping events.
Compatibility
- Minecraft Java 26.3 verified through representative status pings on Paper 26.3/194, Velocity 4.2.0/30 and BungeeCord 2104. Tests covered MOTD, hover, favicon, counts, maintenance and reload recovery, plus 10 passing regression tests.
- Current Paper/Velocity hosts require Java 25. BungeeCord was tested on Java 21 and 25. Plugin bytecode remains Java 17.
- MiniMessage is supported on Paper/Velocity; BungeeCord uses legacy/hex formatting. Legacy Spigot adapters remain, but plain Spigot was not runtime-tested.
Installation / Updating
Stop the host, back up the plugin/configuration, replace the old JAR with NullBrand-2.0.1.jar, and restart. No configuration migration is required. Review individually assigned management permissions. Runtime overrides reset on successful reload as before. Install the shaded release JAR, not a -plain.jar or source archive, and verify its SHA-256 file.
Known Limitations
Maintenance changes branding; it does not deny logins. The ping limiter skips branding during cooldown; it is not network flood protection. Online-mode authentication, sustained load, older hosts, plain Spigot, Folia and Waterfall were not tested. Waterfall is discontinued; no 26.3 support is claimed for it.