Tags
Creators
Details
All versions
2.4.0-b2
Beta
NeoForge 26.1.2 2.4.0-b2last month 37
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Changes
This is an unstable mod release - use at your own risk!
For Developers
- Added Cnfg Enum support (More info: https://wiki.soncresity.industries/sies/develop/unstable-releases#cnfg-enum-support)
- [NeoForge] RegistryUtils are finally coming to NeoForge! (More info: https://wiki.soncresity.industries/sies/develop/unstable-releases#registry-utils)
- [Fabric] Using RegistryUtils to register blocks and items now returns a Supplier instead of the object itself. To access the object, call
get()on the returned Supplier. This was changed for parity with NeoForge. - More methods have been added to the RegistryUtils class to make registering easier. (More info: https://wiki.soncresity.industries/sies/develop/unstable-releases#registry-utils)
- Improved Cnfg value validation (More info: https://wiki.soncresity.industries/sies/develop/unstable-releases#cnfg-improvements-and-fixes)
- Incorrect types of cnfg values will now get parsed to the correct type if possible (Numbers -> Strings, Double -> Float, Float -> Integer (decimal point is dropped)) (More info: https://wiki.soncresity.industries/sies/develop/unstable-releases#cnfg-improvements-and-fixes)
- Fixed an issue where accessing Cnfg values not registered in any schema would silently return nothing. In this case, the default value is now returned. (More info: https://wiki.soncresity.industries/sies/develop/unstable-releases#cnfg-improvements-and-fixes)
- Fixed an issue where NeoForge 1.21.10+ worlds couldn't be loaded in a development environment.
Note: When the fully stable version of this mod is released, the changelog from all previous unstable versions will be merged.
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:VaZKU13m:C35nXq79"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VaZKU13m:C35nXq79"
}

