Tags
Creators
Details
v2.2.5+1.21.1
Compatibility
Changes
NeoOrigins 2.2.5
Adds a Build A Spell integration, two new powers, an expanded client-config surface for the HUD ability display, an array-form authoring fix, and a new Minecraft 26.2 build alongside 26.1.x and 1.21.1.
New Powers & Systems
- Build A Spell integration —
neoorigins:cast_spell: casts an inline, effect-first Build A Spell spell on activation. Mod-gated viarequired_mods; cost is charged on the NeoOrigins power, bypassing BaS mana. attract_mobs: pulls nearby mobs toward the holder (newAvoidEntityGoalMixin).prevent_item_damage: stops items losing durability under the power's conditions.tame_targetaction verb: tames the entity on the other side of an interaction.
Pack Author Features
- Action/condition fields now accept an object or an array (implicit "all-of") — a bare array previously silently no-opped.
summon_miniongains attribute & enchantment fields for summoned minions.disable_hotkeyprecedence clarified over a power's own bind.
Client Configuration
- Expanded HUD ability-display options (cooldown-countdown opacity, default origin sort), documented in the new
CLIENT_CONFIG.md.
Bug Fixes
- Oceanic conduit/apex powers are usable on land again — they were water-gated by vanilla
conduit_power; rebuilt on land-usable effects.
Minecraft 26.2 Support
- A native MC 26.2 jar joins the release (NeoForge, Java 25), alongside the 26.1.x and 1.21.1 jars.
- Note: a few soft-dependency integrations (JEI, Jade, FTB) aren't on the 26.2 build yet, pending those mods' 26.2 releases — core + Build A Spell are fully present. 26.1.x and 1.21.1 are unaffected.
Localization & Docs
- All 12 locale files updated;
ACTIONS/API/CONDITIONS/POWER_TYPES/CLIENT_CONFIGdocs and the power/action + web-editor schemas regenerated.
Optional dependencies
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:RUtQ9kfe:IbAhEnug"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RUtQ9kfe:IbAhEnug"
}




