Frames Map 3D

v0.0.0-beta.2 — Fix: 3D rendering never triggered

Fix

• The 3D mesh was never requested or built: the mixin that swaps the flat vanilla map for the 3D mesh only asked the server for terrain data once a mesh already existed — an impossible bootstrap (it never asked because it never had one, and never had one because it never asked). Framed maps always showed the normal flat texture. Now the request/refresh always happens when a frame wants 3D rendering; the flat draw is only skipped once a mesh is actually ready to replace it, so the map shows its usual 2D texture while the first capture is in flight and switches to 3D as soon as it's available.

JAR: frames_map_3d-1.21.1-neoforge-21.1.249-0.0.0-beta.2.jar

Tag: 1.21.1-neoforge-beta.2