Terrain atlas breaks at mipmap 4 unless lower value or "quad":1 is added on block definition

Since the latest update, the RenderDragon engine experiences a major texture bleeding and mipmap filtering glitch during terrain atlas compilation, specifically affecting resource packs with extensive terrain definitions.

When "num_mip_levels" is set to 4, the engine fails to properly filter and isolate textures at a distance. This causes visible black or transparent lines to stretch horizontally/sideways across the blocks when looking at them from afar.

This rendering bug selectively breaks animated textures—most noticeably vanilla water and lava—as well as other animated blocks like magma or custom blocks where new animations have been implemented. The glitch happens internally within the atlas processing without any actual changes being made to the block models or configurations themselves.

The engine only recovers from this visual corruption if "num_mip_levels" is lowered to 2 or less (which prevents the high-tier mipmap scaling failure), or if the explicit mapping property '"quad": 1' is manually injected into the texture definitions within 'terrain_texture.json' to force correct atlas registration and boundary clipping.