Repository navigation
Conversation
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>
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
5 participants
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.
cabaletta's
26.3branch (cabaletta#5130) with the Meteor changes commit cherry-picked on top, same layout as the26.2and26.1branches here. The only conflict wasmod_version, now26.3-SNAPSHOT.Opened against
26.2because there is no26.3branch in this repo yet; feel free to retarget once it exists.Built with
./gradlew build, published to mavenLocal and tested in a 26.3 dev client together with the meteor-client 26.3 update (PR follows): Baritone loads, the mixin audit passes, and it initialises in a world and saves its cache.