Tags
Creators
Details
4.0.0
Compatibility
Changes
This release provides several changes and improvements for the code itself and plugin's performance, as well many more details.
This version also make changes to the current menus' configurations, it is recommended to make backups before updating to prevent data-corruption or errors due to missing-fields.
Full release changelog and changes-registry: https://github.com/aivruu/teams/releases/latest
Features
- Implemented update-checker and notifier for player about new plugin releases.
- Remade configuration-system to improve reload-process and reduce methods in some classes, all configuration-containers were encapsulated into a single-class
ConfigurationManager,
Changes
- Some classes were renamed to a more-appropriate name according to their package (Major).
- Removed some enum-constants from
ModificationContextas they are no longer used (Major). - Now
handleClickLogic(...)method will return a value-object with information about the clicked-item (only if item is valid, or is notAIR), this also reuses theItemMetafor the item (to avoid repeated-creation when calls to super-class and implementations) (Major). - Removed deprecated-methods for
PlayerAggregateRootclass (Major). - Removed
TagModifierServiceand adaptTagModificationProcessorfor changes, and input-processing, and move most-logic to processor's implementation (Major). - Reused
ItemStackreferences when a menu-item will be used through multiple-slots. - Included more-abstractions, and define duplicated-logic into utility-classes for menu-items and reduce boilerplate-code on menus-implementations.
- Re-structured infrastructure-logic, common-logic between infrastructure-implementations was moved into abstractions depending on infrastructure-type.
- Tried to improve readability by using switch-block in
InfrastructureRepositoryController#selectAndInitialize. - Now when retrieving a repository's information (if the interface-contract permits it), a "viewer" collection will be returned instead of original cache-collection to avoid possible non-desired data-management by thirds.
- Now tag's information only will be saved if they were modified.
- ...
Fixes
- Exception due to access to a placeholder-hook's implementation when soft-dependency is not available.
- Exception when saving player's information due to a incorrect null-check for
selected-tagfield (for JSON infrastructure) .
Optional dependencies
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:RKRkter9:PMAr0g9s"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RKRkter9:PMAr0g9s"
}

