Tags
Creators
Details
v2.0.0+26.1
Compatibility
Changes
NeoOrigins 2.0.0
A ground-up V2 rewrite focused on data-driven authoring, cleaner internals, and a big content pass across every built-in origin and class.
Pack-author docs: https://cyberday1.github.io/NeoOrigins/
Highlights:
- Two-layer selection: 46 origins x 20 classes
- All 17 classes rebalanced to 4-5 passive powers each (zero keybind slots)
- 3 new classes: Fisher, Mason, Paladin
- 88 legacy PowerType classes consolidated to ~60 composable types
- New canonical V2 forms: persistent_effect, condition_passive, action_on_event, active_ability
- 10+ new DSL conditions (night, thundering, has_effect, climbing, near_block, out_of_combat, moon_phase, exposed_to_sun)
- New 'dash' DSL action with variable strength
- Orb of Origin: XP-gated re-pick consumable
- Origin spawn anchors with ocean-floor + water-surface fallbacks
- Advancement-based origin upgrades
Aquatic overhaul:
- 'Dries Out of Water' system with global config-driven drain rate
- 'Pescivore' fish-only diet with cooked-equivalent stats for raw fish
- 'Deep Current' aquatic speed across all aquatic origins
- Bubble HUD hidden + water-fog removed for aquatic kits
Fixes:
- Hunger cost on active abilities actually deducts (was silently dropped pre-2.0)
- ModifyDamagePower direction:out fires vs mob victims
- exposed_to_sun covers the full day
- Action handlers no longer leak on respawn / login / origin-swap
- Mob-summon ownership stable cross-dimension and relog
- Stable attribute modifier IDs (no stacking on relog)
And near-uncountable small and large bugs that came up during playtesting both V1 and V2.
Huge thanks to NyxBorne, Soul, and Jams.
Targets: MC 26.1 / Java 25 / NeoForge 27.x and MC 1.21.1 / Java 21 / NeoForge 21.1.x.
Report bugs: https://github.com/CyberDay1/NeoOrigins/issues
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:575nrmXR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RUtQ9kfe:575nrmXR"
}


