Skip to content

26.3 - #16

Open
robotum1 wants to merge 15 commits into
MeteorDevelopment:26.2from
robotum1:26.3
Open

26.3#16
robotum1 wants to merge 15 commits into
MeteorDevelopment:26.2from
robotum1:26.3

Conversation

@robotum1

Copy link
Copy Markdown

Port of the fork to Minecraft 26.3.

Built the same way as the other version branches: cabaletta/baritone's 26.3 branch (which has the 26.3 fixes from cabaletta#5130) with the Meteor changes commit on top. The only conflict was mod_version, which is now 26.3-SNAPSHOT.

There's no 26.3 branch here yet, so this targets 26.2, but it shouldn't be merged into it. It would be best to create a 26.3 branch from this PR's head, or to retarget the PR once that branch exists.

Tested on 26.3 together with Meteor: it loads into a singleplayer world with no mixin errors, and the world cache initializes.

Todarac and others added 15 commits August 31, 2026 16:37
PR cabaletta#5058 sourced ServerLevelStub's RegistryAccess from client.level so that
modded loot tables would resolve. However, loot tables are populated only by
the ReloadableServerRegistries reload performed in load(); a client
RegistryAccess never receives them. In game (client.level != null) every loot
table lookup therefore threw, and the catch (Throwable) widened by that same
PR silently swallowed it, leaving an empty drops list. The visible effect was
that #mine stopped picking up items entirely.

Revert that half so drops resolve again. The widened catch is kept, so modded
blocks whose tables are absent degrade to no known drops instead of crashing,
which preserves what cabaletta#5058 set out to fix.

Reported-by: ZacSharp
Co-Authored-By: Claude <noreply@anthropic.com>
The 26.1 and 26.2 branches both carried mod_version 1.18.0, which would
collide on the v1.18.0 tag and produce identical artifact names for two
distinct builds. 26.1 keeps 1.18.0; 26.2 moves to 1.19.0, matching the
one-version-per-branch scheme used by every previous release.

Co-Authored-By: Claude <noreply@anthropic.com>
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.

5 participants