Tags
Creators
Details
2.0.0-RC6
Compatibility
Changes
This is the sixth release candidate for version 2.0.0, focusing on bug fixes, API, requirements, and compatibility improvements since RC5.
You can use Socialismus on your server now, as it has been considered stable since RC2. However, it will remain as RC until we migrate all features from the legacy version.
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
- Requirements: Added support for trigger-based and message-based requirements.
- Cache: Added a local cache service with TTL support and periodic cleanup.
- Compatibility: Added support for newer Minecraft versions, including the new version format used after 1.21.11.
What changed
- API: Introduced type-safe custom player data storage.
- API: Introduced a dedicated chat rendering and placeholder resolution system. BREAKING
- API: Migrated the requirement registry to use namespaced
RequirementKeys and unified requirement registration. BREAKING - API: Replaced
Playerreferences withActorin command handling. BREAKING - API: Added a platform-agnostic
playSoundmethod toSocialismusPlayer. - API: Added a scope parameter to serialize methods.
- API: Added
SocialismusPlayerAdapterand synced player serialization support.
Fixes
- Platform: Fixed Paper and Bukkit integrity checks, including version detection, compatibility warnings, and Paper-specific environment checks.
- Reload: Re-register integrations in the serializer engine on reload so integrations continue working correctly.
- Synchronization: Synchronize only global chats.
- Logging: Improved logging for selected chat and format.
Full Changelog: https://github.com/whereareiam/Socialismus/compare/2.0.0-RC5...2.0.0-RC6
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:ws8fvbVO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aeIrNw73:ws8fvbVO"
}

