All versions
1.1.0
Release
FunTalismans 1.1.010 months ago 1,034
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Changes
Changelog - FunTalisman
[v1.1.0] – Stability & Update Improvements
[!IMPORTANT] CRITICAL UPDATE INSTRUCTIONS: To ensure full compatibility with the new item synchronization system, a clean installation is mandatory:
- Stop the server.
- Delete the entire
/plugins/FunTalisman/folder.- Reinstall the plugin by replacing the old
.jarfile.- Start the server to generate the updated configuration files.
Fixes
- Reload System: Resolved an issue where
/talisman reloadfailed to update the stats of existing talismans already present in the world. - Total Synchronization: The reload process now fully refreshes all talismans located in:
- Player inventories.
- Ender Chests.
- Containers (Chests, Barrels, Shulkers).
- Temporary inventories (Crafting tables, anvils, etc.).
- Data Consistency: Ensured that NBT data and attributes remain correctly linked after modifications to the configuration files.
New Features
- Default Configuration: The
talismans.conffile now comes pre-loaded with a total of 15 unique talismans (including the Sphere and Totem series), fully configured and ready for use. - New Subcommand:
/talisman forceupdate- Manually forces a global refresh of every talisman instance across the server.
Improvements
- General Stability: Minor internal code fixes to improve performance when scanning multiple inventories.
- Data Handling: Improved update logic to prevent talismans from retaining outdated data or "ghost" attributes.
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:NBxMOPrc:O6v67EaK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NBxMOPrc:O6v67EaK"
}

