Tags
Creators
Details
Licensed MIT
Published 3 months ago
All versions
v1.12.0+26.1
Release
NeoOrigins v1.12.0 (MC 26.1.x)3 months ago 36
Compatibility
Minecraft: Java Edition
26.1.x
Platform
NeoForge
Supported environments
Client and server
Changes
v1.12.0
Fixes
- Wall climbing now actually works. The power has been converted from an active toggle to a passive ability (matching upstream origins:climbing): no more skill-slot binding or toggle-on required. Holding jump against a wall propels you upward; releasing jump slow-falls/grips. Previously the power only clamped downward velocity — you could never climb up.
- Mage origins and monster_tamer can now be disabled via config. The config keys for air_mage, darkness_mage, earth_mage, fire_mage, gravity_mage, water_mage and monster_tamer were missing from the ModConfigSpec declaration, so NightConfig silently stripped any false value on save. (#21)
Datapack compatibility (Origins/Apoli)
- Support canonical Apoli field names: entity_action_lost / entity_action_removed / removed_action for onRevoked hooks, and respawn_entity_action / respawn_action for onRespawn hooks.
- entity_action_chosen now works in action_on_callback powers.
- Accept bare-namespace power type aliases where upstream Origins uses them.
- Clearer registry-mismatch / unknown-type warnings when a datapack references something this build does not recognise.
Performance
- Per-player resolved power cache in ActiveOriginService. The active power set is now rebuilt only on real state changes (origin change, datapack reload, dimension change, config reload) rather than every tick. Cuts steady-state per-player iteration cost substantially on servers with many powers or frequently-iterated queries.
Builds
Shipped for:
- Minecraft 1.21.1 (NeoForge)
- Minecraft 26.1.x (NeoForge)
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:OTleT8kQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RUtQ9kfe:OTleT8kQ"
}


