Tags
Creators
Details
2.0.0-RC3
Compatibility
Changes
This is the third release candidate for version 2.0.0, focusing on bug fixes, API, and other improvements since RC2.
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.
All features except chatting were moved to separate modules that can be downloaded from the Plugins GitHub page.
What’s new
- API: Introduced a Resource API so developers can provide a module that offers a database, sync, and/or cache connection, which can be used by plugin and other modules.
- API: Introduced an API for modules to easily notify about updates. Now, it is an internal system that shouldn't be implemented by each module separately.
- Added new synchronization system, supports not only proxy servers, but also Bukkit and its forks.
- Added chat history clear synchronization.
What changed
- API: Updated dependencies.
- API: Introduced the FUTURE version, in addition to UNSUPPORTED, to correctly mark future versions, as Mojang has decided to release more updates to the game.
- API: Event system now allows listening to the abstract parent class instead of a specific one.
- Rewrote chat synchronization on Velocity.
Fixes
- The plugin is now compiled in Java 17 to support legacy versions.
- Fixed an error that occurred when both players were in different worlds and we tried to measure the distance.
- Fixed ConcurrentModificationException when clearing chat history.
Full Changelog: https://github.com/whereareiam/Socialismus/compare/2.0.0-RC2...2.0.0-RC3
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:lPuYhzVK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aeIrNw73:lPuYhzVK"
}

