HomeJavaModsEffectification [Effect Unification]
Effectification [Effect Unification]
ModsJava

Effectification [Effect Unification]

by UtherHel · on Modrinth

A compatibility mod that unifies similar status effects from different mods to prevent duplication and improve cross-mod compatibility.

⬇ Download on Modrinth

Effectification

A compatibility mod that unifies similar status effects from different mods by replacing source effects with target effects, preventing duplication and improving cross-mod compatibility.

Version 2.0.0 – Now with full Fabric support alongside Forge!

Platform Support

Key Features

How It Works

Status effects work through boolean checks (entity.hasEffect(EFFECT)). Effectification unifies similar effects by:

  1. Unified Storage: All source effects are stored as the target effect internally
  2. Transparent Lookup (Bidirectional mode): entity.hasEffect(source) → automatically redirects to target → returns true if target exists
  3. Single Instance: Only one effect instance exists (the target), but all source variants can detect it (in bidirectional mode)
  4. No Duplication: Multiple bleeding effects from different mods become one unified bleeding effect

Bidirectional vs Unidirectional

Bidirectional (default):

Unidirectional:

Supported Mods (Out-of-the-box)

Note: Pre-configured mappings are included only in the Forge version. Fabric users start with an empty config because most target mods in the default mappings are not available on Fabric. You can add your own mappings for Fabric-compatible mods via the in-game GUI or config file.

Configuration

In-Game GUI (NEW in 2.0.0!)

Configuration GUI

Edit effect mappings directly in-game with the built-in configuration GUI powered by fzzyconfig.

Configuration Files

Main Config: config/effectification/effectification.toml

Configuration Features

Example 1: Wildcard Pattern with Exclusions
[[mappings]]
sourceEffect = "*:bleeding* !*:bleeding_immunity !*:bleeding_resistance"
targetEffect = "majruszsdifficulty:bleeding, attributeslib:bleeding"
amplifierMultiplier = 1.0
onlyVisualChange = false
unidirectional = false

What happens:

Example 2: Stun Effect Unification
[[mappings]]
sourceEffect = "cataclysm:stun"
targetEffect = "relics:stun, more_rpg_classes:stun"
amplifierMultiplier = 1.0
onlyVisualChange = false
unidirectional = false

What happens:

Example 3: Bleeding Effect with Fallbacks
[[mappings]]
sourceEffect = "relics:bleeding"
targetEffect = "majruszsdifficulty:bleeding, attributeslib:bleeding, valoria:bleeding"
amplifierMultiplier = 1.0
onlyVisualChange = false
unidirectional = false

What happens:

Example 4: Unidirectional Mode (Prevent Overlapping Visuals)
[[mappings]]
sourceEffect = "cataclysm:stun"
targetEffect = "alexscaves:stunned"
amplifierMultiplier = 1.0
onlyVisualChange = false
unidirectional = true

What happens:

Example 5: Advanced Stun Unification (Combining All Features)
[[mappings]]
sourceEffect = "*:stun* !*:stun*_resistance !*:stun*_immunity"
targetEffect = "relics:stun, alexscaves:stunned"
amplifierMultiplier = 1.0
onlyVisualChange = false
unidirectional = false
extraApplyEffectTick = "alexscaves:stunned"
discardEffectTick = "*:stun* !*:stun*_immunity !*:stun*_resistance !relics:stun !alexscaves:stunned"

What happens:

Example 6: Visual-Only Rename
[[mappings]]
sourceEffect = "some_mod:custom_effect"
targetEffect = "minecraft:regeneration"
amplifierMultiplier = 1.0
onlyVisualChange = true
unidirectional = false

What happens:

Quick facts

Install steps are the general flow for this file type — How to install Minecraft Java mods & modpacks walks through it step by step.

Verified by MCModsHub

These come from our own check of the pack file, not from the source page.

Explore more