All versions
1.1.0
Release
Potion Effects Set 1.1.025 minutes ago 0
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Changelog
[1.1.0]
Added
- Per-player client tooltip settings in
config/neopoteffectset-client.toml:COMPACT(hold Shift to expand),FULLandHIDDEN.DETAILEDremains a legacy alias forFULL. - Individual switches for passive, on-hit, on-hurt and set tooltip categories and equipped-piece counts.
- Real vanilla or mod-provided potion-effect icons, green names for beneficial effects and red names for harmful effects.
- English and Spanish translations for tooltip labels, triggered effects, equipment slots and set tiers.
- A separate client-only tooltip rules snapshot synchronized from the server on login and datapack reload.
- Focused NeoForge GameTests and a CircleCI workflow for the port.
Improved
- Matching of set bonuses to the equipment slots of their actual pieces, including Curios slot aliases and duplicate accessories.
- Passive-effect and combat handling, including zero-chance cases and avoiding unnecessary per-tick equipment scans when no passive rules apply.
- Validation of malformed datapack data, numeric/NBT values and network payload limits.
- Removal of a duplicate login synchronization hook while preserving authoritative server rules.
- Deduplication of identical potion effects and set definitions from overlapping datapacks without merging entries with distinct parameters or set tiers.
- Native NeoForge 1.21.1 tooltip and networking integration; datapack
nbtmatchers use the itemcustom_datacomponent.
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:wFekTIKV:NTTMRJIp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wFekTIKV:NTTMRJIp"
}

