Every road path search — highway, branch, county — now goes through one function instead of three direct GetPointPath calls. The function body is exactly the call it replaced, so behaviour is unchanged. This exists so the next commit's pathfinding change can be judged on its own: if the generated map changes after this point, it was the heuristic, not a refactor slip. Routing is untouched: which towns connect, loop order, Prim's daisy-chain, tier assignment and the abandon protocol all deal only in town positions and never touch the grid. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| Scenes | ||
| Scripts | ||
| README.md | ||
/Tools
Offline developer utilities. Nothing here ships. These generate the source data that /Server
and /Client later consume, which keeps world-generation logic out of the shipped client.
The 2D world generator
Script: Tools/Scripts/MapGenerator.cs · Scenes: Tools/Scenes/MapPreview.tscn and
Scenes/MapCaptureTool.tscn
Builds the topographical and logistical foundation of the island before any 3D exists.
- Resolution is config-driven, from
ServerConfig.json'sMapProfile:4K/6K/8K/10K→ 4096 / 6144 / 8192 / 10240. Shipped default is 8K. 1 pixel = 1 in-game metre = 1 voxel footprint. (TheMapSizefield initialiser in the script says 4096, but it is overwritten from config before use.) - Topography: FastNoiseLite plus distance-falloff maths for a guaranteed mainland island, a mountain spine, dynamic temperature-driven sea level, and an impact crater pushed into the northern coast (carved at 80 % of its radius so a landbridge always survives).
- Logistics:
AStarGrid2Dpathfinding producing a looping continental highway, a branch to the mountain hub, and county roads daisy-chained outward with Prim's algorithm. Paths are decimated (Ramer–Douglas–Peucker) then smoothed (4 Chaikin passes). - Zoning: biome mapping and tiered town/POI placement by slope, temperature and proximity.
⚠️ A* is the known bottleneck
The grid is one node per pixel — 67 million nodes at 8K — and the weight-setup pass walks every
one of them. A full generation can stall long enough that runs get abandoned. await yields are
sprinkled through the road stage, but they cannot interrupt a single engine-side GetPointPath call,
so they only help between paths. Expect a regeneration to take minutes, or to need abandoning.
Outputs — written to user://, not into the project
| File | What it is |
|---|---|
MapData_Seed_<seed>.dat |
The binary blueprint the server reads (~512 MB at 8K) |
Map_Seed_<seed>.png |
Visual snapshot of the map, for reviewing and picking seeds |
On Linux: ~/.local/share/godot/app_userdata/islaApocolypse/.
Running it
Open Tools/Scenes/MapPreview.tscn and press F6. It is also the project's main scene, so
pressing F5 anywhere runs this — which is why F5 regenerates your world instead of starting the
game. Use Scenes/MapCaptureTool.tscn when you specifically want the full-resolution PNG.
Rules
- No client dependencies. Nothing here may reference UI, player controllers or shaders in
/Client. - Data out, nothing in. Tools emit
.dat/.png/.json; they never write to a live server save. - No magic numbers. Distances and radii scale off
MapSizeor the derivedscaleFactor, so the generator behaves the same at every profile.