26.2 update

[Big-Iron-Cheems]

Type of change

• Bug fix
• New feature

Description

Future 26.2 update.

Related issues

None.

How Has This Been Tested?

Builds and runs fine on 26.2, might still have some bugs we missed.

Checklist:

• My code follows the style guidelines of this project.
• I have added comments to my code in more complex areas.
• I have tested the code in both development and production environments.

[Big-Iron-Cheems]

@Sonorya issue should be fixed, I tried ESP Shader mode locally and it works.

[Groov21]

• Armour Hud Element is detached from placement box (affects Combat Hud too)
• Ambience Module renders clouds when End Sky setting is selected Solved in a40415e
• Light Overlay module only renders lines when looking through a block or entity when the See through blocks setting is off

[Sonorya]

@Big-Iron-Cheems How many time it's take before final merge ? Other question is there a pull request of a pre release of baritone ?

[Watchedfungus88]

Wireframe ESP renders stale/incorrect entity animations on 26.2

Tested against the current head of this PR (e8330f5b).

Observed behavior

With ESP set to Wireframe, moving players can render poses that do not match their actual animation: heads and limbs shake, body/head orientation can appear backward while running forward, and players can briefly show actions they are not performing. The same scene renders correctly with Shader/Glow ESP.

Steps to reproduce

1. Build and run the 26.2 update branch.
2. Enable ESP for players and set Mode to Wireframe.
3. Observe several players while they run, turn, crouch, or use items.
4. Compare their pose with Shader or Glow mode.

Source-level cause

In WireframeEntityRenderer.InterceptingStorage.submitModel, the intercepted model is rendered directly:

model.renderToBuffer(poseStack, vertexConsumer, lightCoords, overlayCoords, tintedColor);

The normal Minecraft 26.2 ModelFeatureRenderer path calls model.setupAnim(state) immediately before renderToBuffer. Because the Wireframe interceptor bypasses that processing step, model parts can retain stale/default transforms from another render.

The minimum fix is:

model.setupAnim(state);
model.renderToBuffer(poseStack, vertexConsumer, lightCoords, overlayCoords, tintedColor);

It is also safest to reset the custom vertex consumer partial-quad index before submitting each entity. Reusing the fully extracted render state from LevelRenderState.entityRenderStates makes Wireframe match the canonical vanilla pose exactly, but the missing setupAnim call is the direct regression.