2.1.13
Compatibility
Required content
Changes
This build contain new configuration values! https://github.com/ScapeCodes/SupremeTags/commit/b505f4e134278b570aec83ef880af26b3d54574c
- This build massively reduces the jar file size, allowing the plugin to rely on the server to load certain dependencies.
- Implemented XSeries to combat backwards compatibility on Materials & Sounds.
Updated to 1.21.10
Added confirmation Menus for editor delete.
Added development structure to the plugin (OP dev alert join message & dev build in jar file)
Added sound settings in config.yml for many actions. (Drag and drop config update)
Added %current% placeholder to editor messages. (returns the current value before a new one is set)
Added Rarity to be editable in editor menus.
Added tag-removed in messages.yml.
Added "cancel" function in editor event chat.
Added Tag Actions Menu toggle in config menu.
Added head-UUID & skull-TEXTURE_URL as material types.
Optimized unlocked tags count schedular.
Fixed basehead-BASE64 from not working.
Fixed Tag Effects not re-applying on respawn due to dying.
Fixed Tag Effects not re-applying when consuming milk.
Fixed NullPointerException to built-in %tag% placeholder in messages.
Fixed main thread staling/crash issue.
Fixed error found in debug command.
Fixed %tag% placeholder error in messages.
Fixed issues in config menu.
Fixed ingame editor issues.
Fixed some lores in editor menu displaying wrong.
Fixed players tag is getting reset on rejoin.
Fixed sounds on lower versions.
Fixed automatic material pulling without needing to change configs for lower versions. (some may still need configuration, use: material:id for lower versions)
Fixed config menus for lower versions.
Fixed replacement error on success message & others.
Fixed customModelData check error on custom items.
Fixed miniMessage from not working.
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:mzraaPLu:c1Af563d"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mzraaPLu:c1Af563d"
}

