Tags
Creators
Details
1.1
Compatibility
Changes
What's new in version 1.1?
I probably missed some stuff, so just take a look at GitHub if you're interested
Performance, Core & Dependencies
- more performance and stability improvements
- reworked start and disable methods
- fixed update checker / improved it
- implemented HikariCP connection pool and try-with-resources (should be a much more stable connection now)
- added some more dependencies and shading
Design & Configuration
- updated description in plugin.yml
- updated config.yml design (added lobby & map locations header)
- small design changes
- added [Paintball] prefix to more places
- changed some spanish things to english
Code Cleanups & Refactoring
- cleanup of old update checker
- removed unused imports
- resolved nullability warnings and redundant boxing
- converted PaintballAPI to static utility class
- resolved nullability and redundant casting in hologram management
- stored configuration section in variable to resolve nullability warning in cargarPartidas
- replaced single-iteration while loop and simplified boolean logic
- used UUID instead of name
Bug Fixes & Safety Improvements
- added null check for paintball command registration (more cosmetic than useful)
- used safe removeIf to prevent suspicious list modification in loop
- used safe removeIf to prevent suspicious list modification in removerConfigPlayerregisterPlayers
- added a lot of null checks
- handled mkdirs return value when creating players folder
- used native getInt with default values to resolve potential NPE in cargarJugadores
- fixed arena not working properly sometimes
Logging & Deprecations
- used robust logging in config updater
- removed legacy automatic configuration updater, will later be replaced with a modern one
- replaced printStackTrace with robust logging in a lot of places
- fixed some deprecations
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:c7PiXtN1:JGykuoyl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:c7PiXtN1:JGykuoyl"
}

