Tags
Creators
Details
Licensed MIT
Published 3 months ago
All versions
v2.0.26+26.1
Release
NeoOrigins v2.0.26 (MC 26.1.x)2 months ago 10
Compatibility
Minecraft: Java Edition
26.1.x
Platform
NeoForge
Supported environments
Client and server
Changes
v2.0.26: Compat Expansion — Power Aliases, Effect Amplifier, Attribute Normalization
Features:
- 22 well-known Origins built-in power aliases (carnivore, cat_vision, fall_immunity, launch_into_air, light_armor, nine_lives, no_shield, vegetarian, weak_arms, etc.)
- New item tag: neoorigins:meat_foods for carnivore diet restriction
- modify_status_effect_amplifier Route B handler — boosts effect amplifiers (fixes 25 Chimaera powers)
- modify_falling Route B handler — gravity reduction + safe fall distance
- 12 new condition/action types: status_effect, air, power, replaceable, actor_condition, choice, mount, passenger_action, spawn_effect_cloud, offset, add_xp, crafting_table
- origins:shaking Route B handler (freeze-tick visual)
- apoli:overlay Route B no-op handler (counts toward power ratio)
- Hidden flag for resource bars (hud_render.should_render support)
Fixes:
- conditioned_attribute: attribute field nested inside "modifier" object now parsed correctly (fixes 57 Origins++ powers)
- Attribute name normalization: try raw name, then with/without "generic." prefix (fixes 70 powers on 1.21.1)
- origins:advancement condition support
- spawn_effect_cloud: effect field as JSON object with nested fields
- Suppress "Unknown power type" warnings for Route B types in Route A log
- Substitute origins:temporary_cobweb with minecraft:cobweb in set_block action
- on_block: handle in_tag and and/or nested block_condition combinators
- block_in_radius: fix missing neoorigins: prefix in switch case
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:Ly9LIv3B"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RUtQ9kfe:Ly9LIv3B"
}


