PlexKillstreaks v2.0.0 - Modern Minecraft Update

A major compatibility and stability update! PlexKillstreaks now supports newer Minecraft Paper versions while keeping the features, configurations, and player data from previous releases.

What's New?

Modern Minecraft Compatibility

• Added verified startup compatibility with Paper 26.1.1, 26.1.2, 26.2, and 26.3.
• Retained compatibility with the tested Paper 1.21.4 build.
• Updated optional PlaceholderAPI compatibility to 2.12.3.
• Maintained Java 21 bytecode compatibility across the supported builds.

Note: Paper 26.1+ requires Java 25 to run, even though PlexKillstreaks itself uses Java 21 bytecode.

Bug Fixes & Improvements

• Fixed PlaceholderAPI expansions not persisting correctly after /papi reload.
• Improved configuration reload handling. Invalid or unreadable configurations no longer replace active settings.
• Improved SQLite database initialization with safer transactional validation.
• Fixed malformed streak values potentially being interpreted as valid data.
• Improved build reliability and dependency management.

Backward Compatibility

• Existing player killstreaks and leaderboard records are preserved.
• Previous configuration files continue to work without regeneration.
• All eight PlaceholderAPI placeholders remain supported.
• Existing commands, permissions, milestones, rewards, anti-farming, and leaderboard functionality remain unchanged.
• No manual database migration is required.

Testing & Verification

• 90 automated tests passed with zero failures.
• Successful startup smoke tests on five Paper builds.
• Verified plugin loading, commands, configuration reload, and shutdown.
• Verified PlaceholderAPI registration and reload behavior on Paper 26.3.
• GitHub Actions build passed.

Full multiplayer PvP testing was not completed across every listed version.

How to Update

1. Stop your Minecraft server.
2. Back up your plugins/PlexKillstreaks/ folder.
3. Replace the previous JAR with PlexKillstreaks-2.0.0.jar.
4. Keep your existing config.yml and data.db.
5. Restart your server.

No configuration reset or data wipe is needed.

GitHub Repository | Report Issues