Skip to content

Manual Cherry-pick needed: cfa70fac4eec2f803088bbeeffce4ce5101be740 - #231

Closed
github-actions[bot] wants to merge 119 commits into
1.26.1from
1.26.2
Closed

Manual Cherry-pick needed: cfa70fac4eec2f803088bbeeffce4ce5101be740#231
github-actions[bot] wants to merge 119 commits into
1.26.1from
1.26.2

Conversation

@github-actions

Copy link
Copy Markdown

Cherry-pick of cfa70fa from 1.26.2 to 1.26.1 failed due to conflicts.

PTOM76 and others added 30 commits June 22, 2026 11:13
Fabric's menu API refuses to open a menu whose type is an ExtendedMenuType
unless the MenuProvider also implements
net.fabricmc.fabric.api.menu.v1.ExtendedMenuProvider. Our own
core.mc261.ExtendedMenuProvider does not, so every extended menu registered
through ExtendedScreenHandlerTypeBuilder threw IllegalArgumentException on
open and the screen silently never appeared.

Route both openExtendedMenu overloads through a new @ExpectPlatform
MenuOpener. The Fabric implementation wraps the provider in one that does
implement Fabric's interface; NeoForge keeps the previous behaviour.
CompatibleArmorMaterial#build passes 0 as the durability multiplier, so
humanoidArmor sets a max damage of 0 on every armor item built through
CompatibleArmorItem. Vanilla damages every worn piece when the player is hit,
so a single hit destroys the whole set at once, and the durability bar reads
empty until it does.

The multiplier cannot be recovered from the material: it reports an absolute
durability per slot, while vanilla multiplies one shared value by a per slot
constant, so no single multiplier reproduces all four. Apply the material's own
value per item after humanoidArmor has run instead, and leave build alone since
it is already deprecated.
@PTOM76 PTOM76 closed this Aug 27, 2026
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