Links
Tags
Creators
Details
Licensed MPL-2.0
Published 6 months ago
Updated 3 weeks ago
All versions
26.1.2.7
Beta
Nanite Library Neoforge 26.1.2.73 weeks ago 431
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
Platform
NeoForge
Supported environments
Client and server
Changes
[26.1.2.7]
Added
NetworkRegistry#versioned(String)andNetworkRegistry#optional()to set a packet's network version and optionality on NeoForge- Both are no-ops on Fabric as it has no version negotiation and never refuses connections over missing packets
Config#restoreFromDisk()andConfigManager#restoreSyncedConfigs()to drop values synced from a server
Changed
- Fabric registries are now deferred until
initialize()is called, matching NeoForge'sDeferredRegister - Registering an entry after its registry has been initialized now throws on both platforms instead of silently doing nothing
- Accessing a Fabric registry entry before its registry is initialized now throws with the entry's id
- Common configs now load as soon as they're registered, and reload when a server starts
- Registering a config after its type has loaded now loads it immediately instead of throwing
- Server configs on NeoForge now load before the world loads, matching Fabric
- The config sync packet is now optional, so clients with the library can join servers without it (and vice versa)
- The config sync packet no longer sends comments and supports much larger configs (256K characters, up from 32K)
ConfigValue#setnow saves the config file- Config files now keep values in the order they're declared
CreativeModeTabBuilder#populateFromRegistrynow reads the registry's entries when the tab is populated instead of when it's called
Deprecated
ExecutionTargetand theNetworkRegistryoverloads that take one, handlers always run on the main thread
Fixed
- Dedicated Fabric servers loading client-only networking classes when packets were registered
NetworkRegistry#playBidirectionalcrashing on NeoForge due to the payload being registered twicePlatform#sendPacketToAllPlayersdoing nothing on NeoForgePlatformClient#registerResourcePackReloadListenersnever registering the listeners on NeoForge- Server configs never loading on Fabric
- Sending an optional packet to a side without it throwing on NeoForge
- Values synced from a server sticking around after disconnecting, and being able to be written to disk
- Config keys removed from the file keeping their old value on reload
- Duplicate config keys silently replacing each other, they now throw
CreativeModeTabBuildercrashing when no icon was setLazy#invalidateholding onto the old value
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:xSlNcCOe:mGVaNjJK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xSlNcCOe:mGVaNjJK"
}

