Tags
Creators
Details
Licensed MIT
Published 4 months ago
Updated 2 months ago
All versions
1.6.0
Release
Effective Instruments 1.6.02 months ago 1,267
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
[1.6.0] - 2026-07-01
Added
- Datapack-driven aura data. Aura presets, instrument→aura mappings, and
durability metadata now load from datapacks
(
data/<namespace>/effectiveinstruments/aura/{presets,instrument_map,mobile_instrument_map,durability}/) via a reload listener that re-runs on server start and every/reload. The mod ships its defaults as a generated datapack; modpacks can add or override any of it. Legacyconfig/effective_instruments/files still layer on top as overrides (gated byallowConfigOverrides). - Client preset sync (
SyncAuraDataS2CPacket). Remote clients receive the server's preset registry + mappings so the selector overlay works on dedicated/LAN servers. Sent on login and after every server reload (viaOnDatapackSyncEvent). Wire protocol bumped to 5 — pre-1.6.0 clients cannot populate a datapack-driven registry, so the handshake mismatch is intentional. IAuraPerformerseam (PlayerPerformer) — groundwork for non-player performers; player behavior is unchanged.
Fixed
- Malformed datapack JSON (bad field type, invalid effect id) is now isolated per entry and can no longer abort world load or leave the aura registry half-cleared; the registry is swapped in transactionally.
- The reload listener no longer reads SERVER config before it loads (regression of the 1.4.9 split); pre-config reads route through safe accessors.
- Effect cleanup no longer strips beacon / other-mod effects that merely share an aura's amplifier and ambient flag — it now matches on the recorded expiry.
- Vanilla
/reloadre-syncs presets to clients (previously only login and the EI commands did). - Mobile autoplay auras now activate in every dimension (discovery scan was overworld-only) and are cleared from the active set on logout.
- Server authority: stationary aura selection requires a held tracked instrument, and the mobile screen-open path requires the claimed instrument to actually be held — closing two client-trusted-state holes.
- Spectators, snow golems, ambient creatures, and neutral mobs are no longer hit by offensive auras under the default config.
- Per-note aura application is throttled, and mobile aura radius is capped to the mobile tier's bound.
- Packets now declare their network direction; a
.gitattributesnormalizes line endings (gradlewstays LF).
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:2XrWINxz:rpfhGgM2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2XrWINxz:rpfhGgM2"
}

