1.6
Compatibility
Changes
v1.6
Added
/ef splitβ splits a fused elytra back into the original elytra + chestplate. Lossless for fusions made on 1.6+. Older fusions fall back to a blank elytra + blank chestplate of the matching tier, with the enchantments moved to the chestplate.- Chat confirmation for
/ef splitwith clickable[Confirm] [Cancel]buttons and a 30s timeout. - Named elytras now carry their name into the fused result by default. Controlled by
fusion.name_mode(elytra,chestplate,preserve,config). - Per-tier toggle: set
enabled: falseon any material to remove its recipe without deleting the section. - Global particle toggle:
particles.enabled: false. - Per-tier particle opt-out: set
particle: "none"(or leave empty) to disable a tier's trail. - All player-facing messages moved to
messages:inconfig.yml. Supports&color codes and{placeholder}substitution. Empty string suppresses a line. - New permissions:
elytrafusion.use(default true) to fuse,elytrafusion.split(default true) to split. Useful with LuckPerms contexts if you want fusing restricted to certain worlds or ranks.
Changed
- Updating the jar no longer requires deleting
config.yml. Missing keys fall back to packaged defaults at runtime, your file is never modified. If your config is out of date, aconfig-latest.ymlreference is dropped next to it and the missing keys are listed in the console; if it's up to date, nothing extra is written. /ef reloadnow reloads the config, re-binds fallback defaults, and re-checks for missing keys./ef splitgives a different message depending on whether you're not holding an elytra at all vs. holding a plain (non-fused) one.
Fixed
- Invalid particle names no longer spam the console every tick. Warned once per unique bad value.
- Fusing a damaged elytra into a tier with lower
max_durability(e.g. into leather) no longer produces an already-broken item. - Fusing an already-fused elytra preserved the wrong snapshot.
/ef splitnow always returns the very first elytra and chestplate regardless of how many times it's been re-fused. - Update checker compared versions with
Double.parseDouble, so1.10looked older than1.5. Now compares numerically per dot-segment. - Tab completion crashed when
materials:was empty. - bStats chart NPE'd on elytras without a display name; switched to the internal tag so it's language-independent.
Upgrading
Replace the jar. Existing fused elytras and your config keep working. Check the console on first start β if anything new is available, it'll tell you which keys are missing and write a config-latest.yml you can copy from.
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:9eHBtsYI:fbaIrMVL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9eHBtsYI:fbaIrMVL"
}

