Tags
Creators
Details
1.0.2
Compatibility
Changes
PlexVariables v1.0.2 - Modern Paper Compatibility
PlexVariables is now compatible with newer Minecraft Paper versions, including Paper 26.3!
This update focuses on modern server compatibility, safer configuration reloads, and improved reliability while preserving all existing variable functionality.
Modern Paper Compatibility
Successfully tested on:
- Paper 1.21.1
- Paper 1.21.4
- Paper 1.21.11
- Paper 26.1.1 (alpha build)
- Paper 26.1.2
- Paper 26.2
- Paper 26.3
Tested with PlaceholderAPI 2.12.3.
The plugin retains Java 21-compatible bytecode. Paper 26.x servers require Java 25 to run.
Fixes & Improvements
- Improved YAML parsing with clearer file, line, and column error messages.
- Fixed malformed variable definitions potentially causing incomplete configuration reloads.
- Improved reload rollback to preserve working variables, settings, and messages when validation fails.
- Improved error handling when configuration reload callbacks fail.
- Resolved a Gradle resource-processing deprecation warning.
- Updated documentation and modern Paper installation guidance.
Backward Compatibility
All existing functionality remains available:
- Static, conditional, expression, and stored variables
- Existing PlaceholderAPI identifiers
- YAML variable configurations
- SQLite player and global data
- Commands and permissions
- Public developer API v1
No database migration or configuration reset is required.
Testing
- 133 automated tests passed with zero failures.
- Runtime checks completed across seven Paper builds.
- Verified variable resolution, PlaceholderAPI integration, configuration reloads, persistent storage, developer API access, and plugin lifecycle handling.
Updating
- Stop your server.
- Back up
plugins/PlexVariables/. - Replace the previous JAR with
PlexVariables-1.0.2.jar. - Keep your existing YAML files and
data.db. - Restart your server.
Make sure you are running the appropriate Java version and have PlaceholderAPI installed.
Developed by Plex Studios
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:WVhy7qA1:jtXt96XU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WVhy7qA1:jtXt96XU"
}

