SpaceWalkerRS

Now that Gen2 is stable, I'm sure you're all itching to migrate your Gen1 mods to Gen2. Luckily we thought ahead a little bit and there's a relatively straightforward path for migrating Loom projects. However, for projects targeting Minecraft versions below 1.3 with both a client and server component, there is extra work needed.

The migration itself comes down to updating the build script and dependencies. If your project uses Feather mappings, they will have to be updated, which will likely be the most tedious part of the process. The first guide below will walk you through how this is done. If your project uses MCP mappings, follow the second guide below, which will skip over some unnecessary steps.

Migration for projects using Feather mappings

The basic premise is as follows: migrate your Gen1 project to the latest Feather gen1 builds, then update the build script for Gen2, et voila! your Gen1 project is now a Gen2 project.

SpaceWalkerRS

24w33a Redstone Experiments

24w33a introduces new experimental changes to redstone dust, aiming to fix some of the long standing issues with it, like the lag it causes and the unintuitive and unreliable way in which it updates.

The problems with redstone dust

The problems with redstone dust stem from its naive implementation. When a wire is updated, it checks what signal it receives from surrounding blocks. If that is different from its current signal strength, it updates it and then notifies neighboring blocks. This implementation is fine for individual wires, but when multiple wires are connected, its flaws become apparent: the wires power each other, but the signal degrades over distance. Thus when you remove the power source from a line of wires, the signal will die out completely. However, any individual wire does not have this context. It will only decrease its signal strength to match what it receives from neighboring wires, and that will repeat until all wires have depowered completely. This r