Tags
Creators
Details
Licensed MIT
Published 3 months ago
All versions
v2.0.27+1.21.1
Release
NeoOrigins v2.0.27 (MC 1.21.1)2 months ago 646
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
v2.0.27: Warper Portal Fix, Sleep Compat, Spawn Translation
Features:
- : self-reference resolution in origins:multiple powers — sibling sub-power references (:_subkey) now correctly resolve to their synthetic IDs in both Route A and Route B expansion
- origins:modify_player_spawn Route A translation — maps dimension/biome/structure fields to native LocationCondition (18 Origins++ powers: Warper End spawn, Nether spawns, fortress/mineshaft/village structure spawns, biome spawns)
- origins:command condition now returns the command's integer result and evaluates comparison/compare_to fields (was always returning true)
- origins:prevent_sleep now supports block_condition field — height-gated sleep restrictions work correctly (Spirit Ram high_sleep: sleep only above Y 70)
- Coffin compat: sleep prevention only blocks vanilla beds — modded sleep blocks (Vampirism coffins, etc.) pass through so vampires can skip the day
Fixes:
- Warper portality power fully functional: portal placement, entity detection, cross-portal teleportation, particle effects, and cleanup all working
- Spirit Ram / origins with conditioned sleep now correctly allow sleeping when block_condition is not met
- Vampirism coffin interaction no longer crashes the server (Failed to encode packet clientbound/minecraft:system_chat) or corrupts singleplayer worlds
- Connection null guard on sleep prevention event for modded block edge cases
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:s3usDfJ4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RUtQ9kfe:s3usDfJ4"
}


