1.9 KiB
Environment depth and traversal backlog
Deferred by the user on September 9 while Control, combat presentation, and the agreed milestone sequence continue. This is not implemented terrain behavior.
Visual direction from the supplied reference: a broad, deeply cut forested valley, layered ridgelines and distant mountains, rocky slopes/cliffs, and large coherent patches of different tree species/colors. The important change is landform scale and depth, with vegetation following the terrain rather than disguising a flat plane.
Plan a versioned terrain pass using combined low-frequency landform noise, height maps, ridged detail, slope masks, and biome transitions. Review a few fixed seed vistas before tuning resource density. Preserve existing worlds/layouts or introduce a new generator version; do not silently alter explored terrain.
Jumping must enable traversal: jump over fallen trees, rocks, fences, and gaps; jump onto steps, ledges, and elevated surfaces. Define collision, obstacle height, slope limits, grounded state, head clearance, and reachable ledge heights together. Share authoritative collision and terrain queries with mob/projectile movement. Mobs need a path around obstacles or an authored traversal capability; they must not pass through scenery that blocks players. Keep collision boundaries continuous across chunks. Caves, overhangs, and stacked spaces remain a later generator scope.
Acceptance: recognizable valley/ridge vistas; routes across elevation changes; jumps that clear low obstacles and fail against tall ones; authoritative landing; consistent player/mob/projectile collision; no resource or structure displacement after eviction/restart; measured terrain/vegetation rendering cost on target devices.
Milestone 4.5 still comes next: rigs, equipment attachments, animations, and sound. Schedule this terrain/traversal pass explicitly when revisiting the milestone plan.