Tags
Creators
Details
2.0.0-RC2
Compatibility
Changes
This is the second release candidate for version 2.0.0, focusing on bug fixes, dependency refresh, and refinements since RC1.
The core architecture remains modular, with only basic chat, the module loader, and developer API in the plugin jar. Download individual feature modules (jar files) into your modules directory as needed.
From this version on, Socialismus 2.0.0 is considered stable for production servers, some modules can already be used with it, but it will still be in RC as not all functionality has been transferred from the legacy version
The plugin is now divided into three platforms:
- VELOCITY: Compatible with versions 1.16 - 1.21 using Java 17.
- BUKKIT: Compatible with versions 1.16 - 1.21 using Java 17. It lacks the optimizations from Paper, so using the PAPER version is highly recommended if possible.
- PAPER: Compatible with versions 1.20 - 1.21 using Java 21.
The documentation has been moved to the GitHub Wiki and will be completed before the official release. In the meantime, you can contact me for assistance via Discord.
What’s new
- Automatic PlayerName Placeholder:
{playerName}is now replaced by default in all serializers without manual handling.
What changed:
- Javadocs: Improved code documentation for both old and new API.
- Code Revision: Improve code readability and performance.
Fixes
- Concurrent Deletion Crash: Prevented
ConcurrentModificationExceptionwhen multiple messages are scheduled for deletion. - JarFile URI Handling: Wrapped plugin jar paths in
File.fromURIto robustly support special characters.
New Contributors
- @tech-6 (#56)
Full Changelog: https://github.com/whereareiam/Socialismus/compare/2.0.0-RC1...2.0.0-RC2
Supplementary resources
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:aeIrNw73:LKzh7lfa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aeIrNw73:LKzh7lfa"
}

