Matching versions and migration
Mod version shipped with FlammiCraft: 1.17.0-1.21.1
Channel Blocks in LBR 1.15.0
Existing Channel Blocks and item stacks load as polished andesite. Saving the world writes the replacement blocks and stacks to disk. Saved chip programs retain their channel values, and the affected ports stay inactive. Use the editor to switch them to direct chip sides.
TD integration migration
Prepared versions: LBR 1.11.0-1.21.1, TDUtilities 1.15.0, TDCreate 1.47.0, TDMeka 2.11.0, TDAE2Additions 1.39.0, TDPlanter 3.31.0 and TDEnderPipes 0.41.0. Install only mods whose other features you need. Standalone LBR requires Tesseract and GuideME; optional readers appear with their target mods. LBR and the combined set require NeoForge 21.1.256 or newer, without a runtime upper bound. Minecraft 1.21.1 and Java 21 remain.
- Stop client and dedicated server fully. Back up the world and local exports
under
little_big_redstone/microchips; use a copied world for acceptance. - Replace the installed versions of the participating seven projects together. Keep only one version of each mod and retain its separate dependencies.
- Restart fully. A resource reload cannot replace the restart.
- Load original LBR programs, inspect components/notes, save and reload. New chips start large; old chips retain their dimensions and offer expansion in the editor. Camera zoom and GUI scale never change stored board dimensions.
- Test Survival costs, group moves, floppy insertion, multiplayer conflicts, readers, Create displays/RGB and EnderPipes, each across save/reload. Exercise local export/import through the floppy menu. Test Aeronautics separately with a real installation, assembly and disassembly.
Old TD integration IDs are intentionally not migrated. This affects former TD readers, network blocks/items and programs referencing them. Rebuild required circuits using the new namespace. Original LBR IDs remain. EnderPipes keeps its own IDs and saved bundles.
Unreadable chips stay locked and retain their original RejectedMicrochipData.
Breaking one yields a recovery chip carrying the block-entity data. This is
preservation, not an automatic converter. Keep that chip and the original
backup. Determine missing types/versions before targeted recovery on a copy.
Replacing the JAR with an old version does not undo new world/program changes.
Server limits use little_big_redstone-server.toml; personal display settings
use little_big_redstone-client.toml. Old TDUtilities network settings are not
automatically transferred; compare any custom budgets with the new sections.
Automated checks and builds do not replace practical acceptance. The assistant has not installed these artifacts, restarted Minecraft or performed gameplay checks. Release markers remain owned by the deployment workflow.