[Codex suggestion] Move render-layer remap out of in-world tick #14

Move render-layer remap out of in-world tick

ReshapedClient.refreshVariantRenderLayers() is now called from END_CLIENT_TICK after client.world is non-null, which means it remaps blocks via BlockRenderLayerMap.putBlock while a world is already loaded. Fabric’s BlockRenderLayerMap contract requires these mappings to be done before world load/rendering, so changing graphics mode in-game can trigger unsupported remaps that lead to renderer-dependent glitches or instability instead of a safe layer update.

Useful? React with 👍 / 👎.

Originally posted by @chatgpt-codex-connector[bot] in #13 (comment)