Create: Connected (Fly Port)

Bug-fix release, driven by player reports and a round of in-game testing. Two crashes and one completely broken block are fixed here — everyone should update.

Posted with the permission of hlysine, the original author. This is still not his release — please report issues on the port's tracker, not on the original mod's.

Requirements

• Minecraft 26.2, Fabric Loader
• Create Fly 6.0.9-1 (26.2-rc-2-6.0.9-1)
• Java 25

Fixed

Hovering an Inventory Bridge crashed the client

Hovering an item compiles its ponder scenes, and one of the Inventory Bridge's scenes stored the side of each item filter as a number. Create Fly reads that side as a direction name and has no fallback, so the game crashed from anywhere that drew the tooltip — the creative inventory, JEI, a chest. This had been there since the port's first release. Every ponder structure was then checked for the same pattern, and for anything else Create Fly reads without a fallback; nothing else was found.

Breaking part of a Fluid Vessel boiler crashed the server

Breaking one vessel of a working boiler re-forms the multiblock around a new controller, and the boiler then checks the pipe organ advancement. That check assumed every vessel carries an advancement tracker. In Create Fly only a block a player placed by hand has one, so a controller placed by the vessel item's multi-placement, a deployer or a schematicannon crashed the next tick. Create Fly's own boiler checks for this; ours now does too.

The Kinetic Battery neither charged nor discharged, and Crank Wheels provided no capacity

Every Connected block registers its stress values as it is created, and the stress config is built from them. The port built that config before the blocks registered, so it came out empty: no Connected block had any stress impact or capacity. The battery charges by its stress impact and discharges by providing capacity, both zero, so it did nothing; the crank wheels could not move any load.

The same mistake left the per-block feature toggles out of the config entirely, so nothing could be switched off.

Existing config files are repaired automatically on the next launch — nobody needs to delete theirs.

Item Silos lost their contents when broken

Breaking a silo dropped nothing, and placing a silo back in the same spot made the items reappear. Minecraft 26.2 removes a block entity before the block's removal hook runs, and the port kept the drop-and-split logic in that hook, where the block entity is already gone. The multiblock was never split, so the silo remembered the broken part's items. The logic now runs where Create Fly runs it for its own vault.

Linked transmitters were lost when broken

The same cause: breaking a linked button, lever or analog lever never gave the Linked Transmitter back, and a linked lever broken while on left its frequency powered.

Extending a 3×3 silo could dupe blocks and leave L-shaped layers

Placing a silo onto the end of a larger one fills a whole layer. The check for how many blocks that needs, and whether they fit, looked at the wrong layer — a leftover from Create's horizontal vault. So part of a layer could be placed for free, and obstructions were ignored, leaving incomplete, L-shaped layers. This one is also in the original mod (hlysine/create_connected#222).

Known issues

Large Item Silos have been reported to split into 1×3×1 columns after their chunk reloads. It could not be reproduced on this build. If you see it, please open an issue and mention whether the silo crosses a chunk border (F3 + G shows them).

Thanks

To the players who reported the silo problems in detail and to the in-game testing that turned up the boiler crash — the kind of bug that only shows when someone breaks a machine that was working.