Neo Origins

A hotfix for a startup crash on 26.1 and 26.2. A recent NeoForge update moved the code that our ignore_fluid power attaches itself to. When that attachment point isn't where the mod expects it, the game refuses to start rather than carry on without the power, so servers on a current NeoForge failed during boot with an error that gave no hint of the real cause (#131). Both 26.x jars are fixed. It isn't a 2.2.26 regression: the same code shipped in 2.2.25 and earlier, and every one of those builds fails the same way on a current NeoForge. Minecraft 1.21.1 was never in reach of it, and is republished unchanged so the three versions stay on one number.

Supports: Minecraft 26.1.x (Java 25) · Minecraft 26.2 (Java 25) · Minecraft 1.21.1 (Java 21)

• 26.1 and 26.2 servers start again on current NeoForge (#131). At NeoForge 26.2.0.69, backported to 26.1.2.100, the block scan our ignore_fluid power wraps moved out of EntityFluidInteraction.update(Entity, boolean) and into a new overload beside it. The old signature stayed, so nothing looked missing, but the attachment point had gone with the body, and startup failed with a "Scanned 0 target(s)" line. The power now attaches to whichever of the two overloads holds the scan, so one build works on both sides of the change; what it does once attached is unchanged. Supported-NeoForge floors are deliberately left where they were. Confirmed against a stock dedicated server at the newest NeoForge on each line.

• The in-game creators' numeric fields survive current NeoForge (26.2). NeoForge removed a text-field helper at 26.2.0.52 that the origin and mob creators used on every field taking a number, so on anything newer, opening a tab with one on it would have thrown. Those fields filter their own input now. Minecraft 26.1 never lost the method and is unchanged.