NeroDecor

Minecraft 26.3 support. No gameplay, id, tag or config change.

Added

• Minecraft 26.3 as a new Stonecutter node on every loader — NeoForge 26.3.0.7-beta, Forge 26.3-66.0.2 and Fabric (fabric-api 0.161.0+26.3, NeoForm 26.3-1) — built alongside 26.1.2 and 26.2, so every release now ships nine loader × version jars.

Changed

• VS Code run/debug configurations (.vscode/launch.json, .vscode/tasks.json) gain the three 26.3 cells; the "Build all" task now builds all nine.
• CI (multiloader.yml, publish.yml) builds, attaches and publishes the 26.3 jars.
• Requires Neroland Core 1.13.0 (was 1.9.0) — the first Core release with a 26.3 build. The loader range still derives from the pin ([${nerolandcore_version},2.0)).
• JEI pins moved to the newest published builds on each Minecraft version: 29.40.0.101 (26.1.2), 30.35.0.223 (26.2) and 31.3.0.18 (26.3). Compile-time API only — JEI remains a soft dependency and the shipped jar gains no hard requirement.

26.3 port notes

• Build: the shared common/ Java source is now preprocessed by Stonecutter for every non-active node (stonecutterProcessCommon), so common code can carry //? if >=26.3 { blocks, and common/src/main/resources-<mc> overlay folders are merged over the shared resources for matching nodes (mergeCommonResources). The active node still compiles the raw common/ folder.
• Build plugins aligned with Neroland Core: ModDevGradle 2.0.147 (the older 2.0.141 cannot set up NeoForge 26.3), ForgeGradle 7.0.40, Stonecutter 0.9.8.
• NeoForge metadata: the deprecated logoFile property is replaced by iconFile on 26.2+ (the logo is a square 256x256 PNG) while 26.1.2, whose FML only understands the old key, still gets logoFile — the key is chosen per cell when the manifest is expanded. This clears NeoForge 26.2+'s dev-only "uses the deprecated logoFile property" warning screen. The Forge manifest is unchanged: logoFile is still the only key Forge supports.