Skip to content

Port to Minecraft 26.1.1#21

Open
Tkain wants to merge 9 commits intovectorwing:26.1from
Tkain:26.1.1
Open

Port to Minecraft 26.1.1#21
Tkain wants to merge 9 commits intovectorwing:26.1from
Tkain:26.1.1

Conversation

@Tkain
Copy link
Copy Markdown

@Tkain Tkain commented Apr 3, 2026

This PR ports The Block Box to Minecraft 26.1.1.

I started this assuming this was going to be simple. It was not. I hope I don't regret having done this.

Here's a list of the major differences between the mod as it is and this port, most of them technical:

  • Copper bars have been removed since they were introduced to vanilla Minecraft post-1.21.1.
    • Is it worth incorporating copper bars' original appearance somehow? Maybe as a built-in resource pack or new item entirely?
  • Model datagen has been completely rewritten to account for NeoForge's adoption of vanilla's model generation.
    • I tried to adhere to the mod's current generated models and naming conventions as best as I could, but the limitations of vanilla's model generators mean that some file names have changed (ex. hanging_brazier -> brazier_hanging).
  • NeoForge's SWORD_DIG item ability was removed post-1.21.1, so palisade sharpening now checks whether an item falls under the #minecraft:sword tag instead.
  • The mod's one new damage tag is now datagenned because I ran into datagen errors using it as-is.

All the minor datagen output changes mean this PR changes a lot of files, so I'd recommend reviewing the changes per-commit instead of all at once. I tried to cordon most of the datagen output changes to their own commit and also tried to avoid having multiple commits touch the same file where possible. Let me know if you have any questions or would like to make any changes.

Tkain added 9 commits March 30, 2026 19:17
This commit changes the project's build scripts to target Minecraft 26.1 (instead of 1.21.1). No mod code has been changed, so this won't compile as-is.
This does not include data generation, so the mod still doesn't compile yet. Additionally, there are a few ambiguities I've left as TODOs.
I had to totally rewrite the mod's model data providers since 26.1 NeoForge uses vanilla's model generators instead of its own. I tried to introduce as few changes as possible, but some generated file names have changed due to technical limitations.

As part of this, I also decided to leverage Minecraft's BlockFamily class to eliminate some boilerplate code. This can also be used for recipe generation, but I decided not to mess with more than I already had to.
This includes removing unused resource files and renaming the brazier template to be in line with its post-port naming scheme.
Everything just works this time since 26.1.1 is just a hotfix. Also includes updates to datagen, Gradle, NeoForge, and JEI.
@vectorwing
Copy link
Copy Markdown
Owner

Oh wow! This is quite a surprise to see! 😄

First off, thank you for the sheer effort put into this. Right now I'm working away on a minor release for Farmer's Delight, so my review may take a few days to do, considering it's a version port. I may do it in multiple passes to catch everything. Also, I have yet to read up on all the changes leading up to 26.1, as I was gonna do it during a future FD port, so this might cause my reviews to take longer still.

That said, I will need to make a 26.1 branch for this PR to land on. Assuming you departed from 1.21.1's latest, it should be the same diff. I'll let you know once I do that.

@vectorwing
Copy link
Copy Markdown
Owner

Copper bars have been removed since they were introduced to vanilla Minecraft post-1.21.1.
Is it worth incorporating copper bars' original appearance somehow? Maybe as a built-in resource pack or new item entirely?

I thought about this during the Copper Age announcement, and my plan was to keep my bars under a different name, rather than remove them.

Maybe "Copper Lattice" could work? I could then have freedom to name my custom-appearance bars however I want, and keep "Bars" to the recolored vanilla ones.

@vectorwing vectorwing changed the base branch from 1.21.1 to 26.1 April 3, 2026 05:08
@vectorwing
Copy link
Copy Markdown
Owner

Alright, branch 26.1 created. I pointed the PR to it, and the diff size is the same.

I can get back to this PR in the next few days to review it properly, once I'm done with the other mod. Thanks once again for the port! ^^

@Tkain
Copy link
Copy Markdown
Author

Tkain commented Apr 3, 2026

Not a problem, take as long as you need. Thanks for making your mods in the first place!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants