Skip to content

Update to 26.1.1#70

Open
f-gillmann wants to merge 1 commit into
AtlasEngineCa:masterfrom
f-gillmann:feat/minestom-26.1.1
Open

Update to 26.1.1#70
f-gillmann wants to merge 1 commit into
AtlasEngineCa:masterfrom
f-gillmann:feat/minestom-26.1.1

Conversation

@f-gillmann
Copy link
Copy Markdown

Overview

This updates to Minestom 2026.05.17c-26.1.1 and fixes issues with rendering on the new 26.1 client.

Updates

  1. minecraft:special -> player_head has no implicit transforms anymore.
    The transformations for some special item models have been extracted to item models as of 26.1 Snapshot 11.
    Emote bones are thus rendered inverted and shifted (see image below) because the template relied on these defaults before this update.
    image

  2. UV bounds are now validated on the client.
    Client now throws Cannot compute translucency out of bounds: [14, -15, 26, 2] in 64x32 image from NativeImage.computeTransparency as of 26.1 Snapshot 7.
    The bake of magma_cream fails and the model becomes a bunch of missing textures.
    image

Minestom

Pulls in Minestom API changes:

  • Pos.fromPoint(p) -> p.asPos()
  • Instance.setTimeRate(0) -> Instance.clock(WorldClock.OVERWORLD).pause()
  • Viewable.sendPacketsToViewers and Entity.getViewers overrides widened to match the new upstream ? extends generic bounds.

Images

Before (Minestom bumped to 26.1) After
image image
image image

Notes

The changes about the transformation likely need to be put into the changelog when a release is drafted. c:

- player_head item: add `transformation` (180° X rotation + [0.5, 0, 0.5] translation)
  to every entry of the template's items/player_head.json.
  26.1 client no longer applies a default for minecraft:special player_head.
  Without the explicit transform, emote bones render inverted and shifted.
- ModelParser.convertUV: clamp output components to [0, 16].
  26.1 client runs NativeImage.computeTransparency
  (render-pass auto-classification, 26.1 Snapshot 7)
  which rejects out-of-bounds UVs that 1.21.11 silently accepted.
- update from Pos.fromPoint() to Point.asPos() and from setTimeRate to WorldClock.pause()
- follow widened Viewable/Entity generic bounds in Minestom
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.

1 participant