All versions
1.3.0
Release
FunTalismans 1.3.02 months ago 1,313
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
Platforms
Paper
Purpur
Required content
Any compatible version
Changes
Changelog - FunTalismans
[v1.3.0] – Talisman Improvements
Added
- Added configurable effects when consuming talisman totems.
- Added automatic custom totem animations using each talisman's CustomModelData.
- Added PacketEvents integration for more reliable totem pop detection.
- Added improved handling for stackable talismans across plugin reloads.
- Expanded the internal system to support future talisman mechanics and abilities.
Fixed
- Fixed critical potion effect conflicts between talisman effects and stronger vanilla potion effects.
- Fixed cases where potion effects could remain active after temporary effects expired or the talisman was removed.
- Fixed passive talisman effects persisting after rapidly consuming or switching talisman totems.
- Fixed effect cleanup and restoration issues that could cause duplicated or persistent effects.
- Improved talisman updating and item data consistency after reloads.
Improved
- Improved compatibility between talisman effects and vanilla Minecraft potion mechanics.
- Improved custom totem animation handling without modifying the player's real inventory.
- Improved compatibility with newer Minecraft server versions.
- Improved general stability and internal effect handling.
Important
- PacketEvents is now required as a dependency for FunTalismans.
- Make sure PacketEvents is installed and updated before starting the server with FunTalismans v1.3.0.
- It is highly recommended to create a backup of your current FunTalismans folder and configuration files before updating.
- Replace the old plugin files with the new v1.3.0 files and review any updated configuration options before starting the server.
- A full server restart is recommended after updating. Avoid using plugin managers or hot-reload tools when replacing the FunTalismans
.jar.
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:cKbB623O"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NBxMOPrc:cKbB623O"
}

