admin 41b515f474 fix: ground physics on real Terrain3D surface
Enable Terrain3D collision_mode=1 so the sculpted landscape provides real physical ground for player and NPCs. Disable GreyboxGround collision (layer/mask = 0) -- it is no longer the active physical floor.

NpcVisual no longer flattens nav waypoint Y to its current elevation. It now follows 3D path points and uses gravity (30 m/s^2) like the player, settling to terrain surface via is_on_floor() + Terrain3D collision. The flat NavigationMesh_greybox still provides correct lateral guidance; physics handles vertical grounding on slopes.

This fixes the player-walking-through-slopes bug and makes NPC movement follow actual terrain elevation for the village area (gentle slopes, ~2.4m noise amplitude). All 10 scenarios pass.
2026-07-07 16:56:15 +02:00
2026-07-07 16:12:13 +02:00
2026-07-07 16:09:37 +02:00

Documentation map

The project uses a small hierarchy so overlapping plans do not become competing sources of truth.

  1. PROJECT_CONTEXT.md is the canonical description of the vision, current implementation, target architecture, and active constraints.
  2. LEARNING_ROADMAP.md owns milestone order, architecture gates, reusable-system exit tests, and intentionally deferred work.
  3. BUILD_IN_PUBLIC_PLAN.md owns the scoped Jajce visual slice. It must respect the architecture gates in the learning roadmap.
  4. RESOURCE_NODE_MIGRATION.md is a focused migration plan. Phases 16 are complete; follow-up work should expand resource discovery without reintroducing abstract resource zones.
  5. ACTION_SYSTEM_ARCHITECTURE.md, ECONOMIC_EVENTS.md, FOOD_STORAGE_ARCHITECTURE.md, SIMULATION_DEFINITIONS.md, and SIMULATION_STATE_SCHEMA.md document the current data contracts.
  6. decisions/ contains durable architectural decisions, including consequences and revisit conditions.

When documents disagree:

  • code and tests describe current behavior;
  • the newest accepted decision record governs architecture;
  • PROJECT_CONTEXT.md governs product intent;
  • LEARNING_ROADMAP.md governs what should be built next;
  • focused plans govern only their stated scope.

Update the smallest relevant set of documents after a decision or milestone. Do not copy full status tables into every plan.

S
Description
No description provided
Readme 48 MiB
Languages
GDScript 86.6%
GDShader 9%
PowerShell 2.4%
Shell 2%