Tags
Creators
Details
Licensed MIT
Published 3 months ago
All versions
v1.8.0+1.21.1
Release
NeoOrigins v1.8.0 (MC 1.21.1)3 months ago 126
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
NeoOrigins v1.8.0
-
Fix origin selection GUI not opening on dedicated servers (#16)
- The origin/layer/power registries are server-side only reload listeners. On dedicated servers, clients had empty data, causing the selection screen to immediately close — even via
/origin guior Orb of Origin. - Server now syncs the full registry to clients on login and before any screen open via a new
SyncOriginRegistryPayloadnetwork packet.
- The origin/layer/power registries are server-side only reload listeners. On dedicated servers, clients had empty data, causing the selection screen to immediately close — even via
-
Configurable power overrides via TOML config
- Every built-in power's numeric parameters are now directly editable in
config/neoorigins-common.tomlunder[power_overrides.*]sections. - Cooldowns, ranges, damage values, scaling, armor, health, knockback resistance, summon counts — all exposed per-power with their current defaults.
- Only values you change from their defaults are applied as overrides, so datapacks still work normally for untouched fields.
- Overrides take effect on
/reloador server restart. - Example: to make Abyssal reflect 50% damage instead of 30%, just edit
[power_overrides.abyssal_thorns_aura] return_ratio = 0.5
- Every built-in power's numeric parameters are now directly editable in
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:EDhdFJ85"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RUtQ9kfe:EDhdFJ85"
}


