Construction Wands Revived
- By
Construction Wands make building easier! (A new take on the Builder's Wand) ported 1.21.1 NeoForge
Curse Maven Snippet
What's new
## 4.0.0 — Minecraft 26.3 / NeoForge
Port to Minecraft 26.3, branched from the 26.2 tree. Carries the same fixes as 4.0.3 on
26.2 (modded blocks that store data on the item, block entity data preserved on placement,
redrawn golden wand).
### Build
- Minecraft `26.3`, NeoForge `26.3.0.0-beta` (declared range: `[26.3.0.0-beta,26.4.0)`).
- **Build system migrated from NeoGradle to ModDevGradle `2.0.147`.** NeoGradle `7.1.38`,
the newest release, cannot build 26.3: its `neoFormRecompile` step fails while recompiling
decompiled *vanilla* source (`net/minecraft/core/HolderSet.java`). ModDevGradle uses
NeoForm Runtime and the artifacts NeoForge already publishes, so that step never runs.
The previous build script is kept as `build.gradle.neogradle.bak`.
### Ported
- **Minecraft 26.3 replaced GLFW with SDL.** `org.lwjgl.glfw` is no longer on the classpath
(`lwjgl-sdl` is), so the keybinds now use Mojang's own `InputConstants` key codes instead
of raw `GLFW.GLFW_KEY_*` constants. Same default keys.
- **Recipes and advancements are now reloadable datapack registries.** `RecipeProvider` takes
a `BootstrapContext` pair instead of a `PackOutput`, `RecipeProvider.Runner` is gone, and
`AdvancementProvider` is a `SingleRegistryBootstrap<Advancement>` built from
`AdvancementSubProvider.Factory` list. Data generation is wired through a
`RegistrySetBuilder` handed to `DatapackBuiltinEntriesProvider.forReloadableLayer`.
- `RecipeProvider` exposes a `HolderGetter<Item>` (`items`) instead of the full
`HolderLookup.Provider`, and `ItemPredicate.Builder#of` takes that getter.
- `Player#drop` now requires a `Prediction`; the undo history drops server-side.
- `BundleContents#itemCopyStream` was renamed to `itemCopies`.
- `FriendlyByteBuf`'s `read/writeBlockHitResult` helpers are gone; the preview packet uses
`BlockHitResult.STREAM_CODEC`.
### Recipe viewer
JEI has no 26.3 build (`jei-26.3-neoforge` is not on the maven), so the item descriptions
are provided through **Reliable Recipe Viewer** instead, which does ship for 26.3.
`RrvIntegration` registers exactly the same texts the JEI plugin did — wand stats, core
descriptions and the Void Sack entry — translated from JEI's `addIngredientInfo` to RRV's
info recipes, rebuilt on every client reload so they follow keybind and config changes.
It is an optional client-side dependency: `ClientHandler` only touches the integration
behind `ModList.isLoaded("rrv")`, so nothing is loaded when RRV is absent.
The JEI plugin is **not deleted** — it stays in `src/disabled-integrations/`, and its
dependency lines in `build.gradle` and `neoforge.mods.toml` are commented out rather than
removed, ready to switch back on when JEI ships for 26.3. Both viewers can coexist then.
RRV is pulled from the Modrinth maven (`maven.modrinth:rrv:8.10.5+26.3-neoforge`) because
`maven.cassian.cc` has not published 8.10.5 yet, and 8.10.5 is the first release with 26.3
support.
### Removed (temporarily)
| Integration | Mod | Reason |
|---|---|---|
| Recipe descriptions | JEI | no 26.3 build; covered by Reliable Recipe Viewer in the meantime |
Sophisticated Backpacks and Sophisticated Core moved from `implementation` to `compileOnly`.
Their published builds declare `minecraft 26.2 or above, and below 26.3`, so FML refuses to
start a dev run with them on the runtime classpath. The integration still compiles and the
published jar is unchanged — those mods were never bundled, and `ContainerRegistrar` already
guards the handler behind `ModList.isLoaded("sophisticatedbackpacks")`. Switch them back to
`implementation` once a 26.3 build ships.
Everything 26.2 already had parked in `src/disabled-integrations/` stays parked. The JEI
plugin joins it there, and its dependency lines in `build.gradle` and `neoforge.mods.toml`
are commented out, ready to switch back on when JEI ships for 26.3.
---
This mod has no additional files