[PORT] - Add Minecraft 26.2 target - #426
Merged
Merged
Conversation
kr1viah
requested changes
Aug 2, 2026
kr1viah
approved these changes
Aug 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds 26.2 as a seventh Stonecutter target. Also carries three fixes for bugs that already existed on main and got in the way.
Behaviour change worth reading before merging. On 26.2,
/ssbabove 15 now gives a command block instead of a container. 26.2 validates container contents strictly, so overstacked slots are silently replaced by EMPTY and you get an empty barrel. Overstacking is how the >15 range worked, and Mojang closed it. Below 26.2 nothing changes.Commits, oldest first:
splitEnvironmentSourceSets()the processor ran twice and wroteMETA-INF/kr1v/index.jsonat the same jar path both times. Loom <=1.16 silently dropped one, so our shipped 1.21.x jars have only ever contained the client half. Loom 1.17 hard-fails instead, which is how it surfaced. Every malilib-api usage is client side, so scoping the processor there fixes it at the source. Upstream issue: Multiple source sets not supported by annotation processor kr1viah/malilib-api#3build_reusable.ymlstill installed Java 21 whilepublish.ymlwas already on 25. The 26.x targets compile with--release 25.CUSTOM_DATA, which is item level data.BLOCK_ENTITY_DATAis what gets copied into the block entity on placement, so every /ssb command block has been outputting 0. Affects all seven versions, fixed on all seven.Tested in game on 26.2, 26.1.2 and 1.21.4 (ssb across all versions): mod loads, airplace outline renders in the right place, config menu and macro editor, macros run, //rstack, //colorcode, /ssb across the range.
One thing that is not new but was never written down anywhere: a command block only keeps its SuccessCount if you place it in creative with permission level 2. Vanilla restriction on command block data, applies on every version.
Important
Here's an attachement that contains the diff file to apply to the wiki :
diff.txt