1.2.0
Compatibility
Changes
Changelog - FunTalismans
[v1.2.0] – Major Systems, WorldGuard & Resource Pack Update
[!IMPORTANT] UPDATE INSTRUCTIONS:
- Stop the server.
- Create a backup of your existing
/plugins/FunTalismans/folder.- Replace the old plugin
.jarwith the new version.- Start the server once to generate the updated configuration files.
- Merge your custom talismans, rarities and messages into the new files.
- Update the optional FunTalismans Resource Pack if you use Custom Model Data models.
New Features
-
Global WorldGuard Integration
- Added a simplified global WorldGuard flag system for all talismans.
- Added
fun-talismans-passiveto control passive talisman effects inside regions. - Added
fun-talismans-useas the shared use-control flag for talisman systems. - Added configurable WorldGuard flag names in
config.conf. - Added a cleaner alternative to managing many individual talisman flags.
Example:
/rg flag <region> fun-talismans-passive deny /rg flag <region> fun-talismans-use deny -
Expanded Passive Talisman Support
- Talismans can now provide passive effects from:
- Main hand.
- Offhand.
- Helmet, chestplate, leggings and boots.
- Any armor slot.
- Both hands.
- Any equipped slot.
- Player inventory and hotbar.
- Talismans can now provide passive effects from:
-
Optional Resource Pack
- Added support for the official FunTalismans Resource Pack.
- Added custom totem models through Custom Model Data.
- Added compatibility for Minecraft clients from 1.21.1 to 1.21.11.
- Added legacy Custom Model Data support for 1.21.1–1.21.3.
- Added modern item-definition support for 1.21.4+.
- Added optimized model size for first person, third person, ground and GUI views.
-
Improved Talisman and Sphere Definitions
- Added updated talismans and spheres ready for use.
- Added normalized player-head texture support.
- Player-head textures now support:
- Minecraft texture URLs.
- Base64 values with the
base64:prefix. - Raw Base64 texture values.
- Improved compatibility for custom talisman names, lore and Russian display text.
-
Configuration Guide Improvements
- Updated the talisman configuration guide with valid examples.
- Added clearer documentation for attributes, effects, slots, textures, NBT and item properties.
- Added examples for inventory passive talismans.
- Added WorldGuard global flag examples.
- Removed outdated or unsupported configuration options from the guide.
Improvements
-
Passive Effect Performance
- Improved passive-effect refresh queues to avoid large updates in a single tick.
- Added configurable per-tick limits for passive refreshes.
- Added movement refresh coalescing to reduce unnecessary checks during continuous movement.
- Added periodic reconciliation for passive effects changed by other plugins or commands.
-
Live Update System
- Improved live updates for talismans already loaded on the server.
- Updates are processed gradually through configurable per-tick limits.
- Improved updates for:
- Player inventories and equipped items.
- Dropped talismans near online players.
- Item Frames and Glow Item Frames.
- Open chests, barrels and shulker boxes.
- Loaded chunks.
-
WorldGuard Performance
- Added short-term caching for WorldGuard flag decisions.
- Reduced repeated region checks while players move.
- Added configurable cache lifetime and maximum cache entries.
-
Update Prioritization
- Player-visible talismans are prioritized before background chunk scanning.
- Nearby dropped talismans and Item Frames are refreshed first.
- Open containers receive priority updates.
- Large update jobs now use bounded queues to protect MSPT.
-
Configuration Cleanup
- Improved comments for server owners.
- Removed internal development notes from public configuration files.
- Added clearer descriptions for performance settings.
- Added safer defaults for large servers.
Fixes
-
Reload Stability
- Improved reload behavior when talisman definitions, textures, names, lore, attributes or effects are changed.
- Improved refresh handling for existing talismans after configuration changes.
- Reduced the possibility of outdated item data remaining after a reload.
-
WorldGuard Flag Management
- Added a global flag approach for passive effects and talisman systems.
- Improved configuration clarity for servers with many talismans.
-
Resource Pack Compatibility
- Added separate model handling for legacy and modern Minecraft item formats.
- Improved custom totem model display size across supported client versions.
-
Release Build
- Fixed the ProGuard version mismatch that could prevent obfuscated release builds from being generated.
- Improved release validation for protected plugin JAR files.
Commands
/ftalismans give <player> <id> [amount]
/ftalismans reload
/ftalismans forceupdate
Available aliases:
/ft
/talisman
/tali
/talismans
Permissions:
funtalismans.give
funtalismans.reload
funtalismans.update
Notes
- Use
/ftalismans reloadafter normal configuration changes. - Use
/ftalismans forceupdateto queue a wider refresh for loaded talismans. - Restart the server only when changing the custom WorldGuard flag names in
config.conf. - WorldGuard and PlaceholderAPI remain optional integrations.
- Create a backup before replacing custom configuration files.
FunTalismans v1.2.0 delivers a safer, cleaner and more scalable foundation for RPG progression, custom combat, collectible equipment and passive talisman systems.
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:ndeRLRGp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NBxMOPrc:ndeRLRGp"
}

