[Purdze]

terrain past the render distance. every chunk the client sees is kept as 32³ voxel sections at five levels of detail, saved to disk per server or world, meshed on a worker thread from models baked per block state, and drawn by the gpu which walks the section tree each frame, culls against a hi-z, picks the detail by screen size and asks for the meshes it lacks. pomme-only, under the distant terrain option

also in here from measuring the branch against master:

• streaming hitches fixed: chunk occlusion and the light engine on their own threads, uploads and chunk packets budgeted per frame (a chunk burst is split only across frames that owe no tick, so every packet is still handled before the tick after it), an o(world) unload removed. stream 1% lows at rd 32 went 27 -> 215 fps, at 64 2 -> 146
• vsync off presents immediately (immediate, then mailbox, then fifo)
• gpu time per pass in f3 and the harness frame_times step
• panics written into latest.log
• the server's view distance is taken as announced (an announcement equal to our request was dropped, so the slider fell back to 32 on a 128 server); the slider passes 32 only for a larger server view distance
• chunk mesher hides faces as shouldRenderFace decides (same-kind translucent blocks, partial shapes), removes the dots and lines ice and snow showed from above

tests: unit tests for the sections, mesher, node tree, face rule, section cache, tick scheduling, occlusion walker and light worker. world/distant_terrain, world/render_distance, blocks/face_culling and blocks/grass_occlusion in game, the last three match the 26.2 client. the chunk packet budget changes when packets and ticks are handled within a frame, so it needs a peel capture before merging

known gaps as TODOs in the code: generation beyond what's been seen, shader packs, dimensions without sky light