Tags
Creators
Details
2.4.3+26.1.x
Compatibility
Changes
IMPORTANT:
ā ļø Back up your world before updating!! Things should work as expected but with any major version update it's important to back up your world just in case.
āļø New
- Updated to 26.1.x | Thank you cputnam for helping port the mod!
š ļø Fixes
- Added two migration solutions for old worlds with legacy crate networks which should fix some major pain points with crate networks
- Crate networks are stored per-dimension, and now follow proper a proper namespaced dimension directory structure for .dat files
- Fixed small desync bug on Crate Station readout when adding new crates to a network
- New network .dat files now have top level format, network_uuid and dimension information for easier debugging and error-proofing
- Fixed some smaller edge case networking issues
Existing World Migration Info
TLDR: You can just load your old world and play, and crate networks should heal themselves. If you run into issues, keep reading below:
- legacy networks get updated to the correct format and data over time by being in a loaded chunk (the mod checks a certain amount of networks every 25 seconds if there are legacy .dat files present in the world), but you can trigger this manually:
/basicstorage migrate info- shows you the coordinates of the closest 3 legacy networks to your location. Moving/teleporting there and using "/basicstorage migrate run" will update the networks as long as the chunks are loaded/basicstorage migrate run- this manually triggers the migration behaviour that runs automatically every 25 seconds, but tries to execute it for every network on file in small batches. If your network doesn't seem to be getting updated, move near it and run this command. None of this is a perfect solution, and some old crate networks may be stale/invalid/unfixable. If this is the case, check the UUID of the network from "/basicstorage migrate info" and delete that file in your world/data/basicstorage/networks directory. You'll also find archived copies of migrated networks in world/data/basicstorage/legacy_migrated_network_copies. Once you've done that, break and replace the blocks to build a fresh network.
Important Caveat: Old network data didn't have a dimension defined, so the coordinates given by "/basicstorage migrate info" may point to any dimension. If you can't find blocks from this mod at the coordinates in your current dimension, try the others first before deleting the data file.
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:NMOanmPo:JodO2jco"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NMOanmPo:JodO2jco"
}

