| name | godot-procedural-generation |
| description | Expert blueprint for procedural content generation (dungeons, terrain, loot, levels) using FastNoiseLite, random walks, BSP trees, Wave Function Collapse, and seeded randomization. Use when creating roguelikes, sandbox games, or dynamic content. Keywords procedural, generation, FastNoiseLite, Perlin noise, BSP, drunkard walk, Wave Function Collapse, seeding. |
Procedural Generation
Seeded algorithms, noise functions, and constraint propagation define replayable content generation. Do not paste inline algorithm tutorials โ load the MANDATORY scripts below.
NEVER Do in Procedural Generation
- NEVER generate chunks on the Main Thread โ Proc-gen is CPU intensive and causes frame-rate spikes. Use
WorkerThreadPool or a background Thread to keep the UI responsive.
- NEVER query
FastNoiseLite every frame โ Sampling noise per frame (especially in _process) is a massive waste. Generate your map into an Image or Array once and sample from memory [NoiseSampling].
- NEVER use
randi() for reproducible seeds โ Always store and reuse a specific seed within your random number generator (RandomNumberGenerator.new()) to ensure consistent world generation.
- NEVER use pure randomness for object placement โ Pure random (white noise) causes clumping and overlapping. Use Poisson Disk Sampling or Jittered Grids for natural-looking distributions.
- NEVER forget to bound your loops โ Procedural loops (like WFC or Cellular Automata) can easily enter infinite states if constraints are impossible. Always include a
max_iterations safety break.
- NEVER instantiate nodes directly from proc-gen threads โ You cannot touch the SceneTree from a worker thread. Generate the data in the thread, then notify the Main Thread to handle
add_child().
- NEVER use complex WFC for simple layouts โ Wave Function Collapse is powerful but overkill for simple paths. Use Drunkard's Walk or BSP for lightweight structured layouts.
- NEVER rely on
TileMap.set_cell() for large-scale updates โ Updating 10,000 cells individually is slow. Prepare a TileMapPattern and use set_pattern() or set_cells_terrain_connect() for batch updates.
- NEVER forget to bake Navigation at the end โ Procedurally generated worlds need their navmeshes rebaked at runtime or the AI will walk into walls.
- NEVER ignore data serialization โ If you generate a world, you must be able to save the seed and any player modifications. Don't try to save the entire raw chunk state if avoidable.
Golden Path (MANDATORY)
Every generator starts here โ seed isolation, async data, main-thread commit:
- Seed & RNG โ MANDATORY proc_gen_seed_history.gd: one
RandomNumberGenerator per level/chunk; persist seed + state for shareable runs.
- Async chunks โ MANDATORY multi_threaded_chunk_gen.gd:
WorkerThreadPool.add_task โ compute data off-thread โ call_deferred("_finalize_chunk") for SceneTree/node work.
- Validate โ bake nav โ after tiles/meshes land on the main thread, rebake
NavigationRegion (see godot-navigation-pathfinding).
var rng := RandomNumberGenerator.new()
func begin_generation(run_seed: int) -> void:
rng.seed = run_seed
WorkerThreadPool.add_task(_build_data.bind(run_seed))
func _build_data(seed: int) -> Dictionary:
var local_rng := RandomNumberGenerator.new()
local_rng.seed = seed
var noise := FastNoiseLite.new()
noise.seed = seed
return {"heights": noise.get_image(64, 64)}
func _ready() -> void:
# Worker returns here โ safe for nodes
pass
func _finalize_from_worker(data: Dictionary) -> void:
# add_child / set_pattern / create_trimesh_collision โ main thread only
pass
Do NOT Load the full scripts/ folder. Open only the script that matches your algorithm row below.
Algorithm Decision Tree
Routing hints: Simple path โ drunkard; rectangular rooms โ BSP; constraint tiles โ WFC lite; open-world chunks โ noise + multi_threaded_chunk_gen.gd. For roguelike run orchestration, hand off to godot-genre-roguelike.
Available Scripts
Core (always start here)
2D layout & placement
Noise & 3D
Expert Procedural Patterns
1. 3D Terrain via ArrayMesh (Marching Cubes)
For voxel-like or smooth organic terrain, use ArrayMesh to generate geometry from code.
- Logic: Calculate vertices, normals, and indices in a worker thread.
- Commit: Use
add_surface_from_arrays(Mesh.PRIMITIVE_TRIANGLES, arrays) to create the mesh.
- Performance: Use
create_trimesh_collision() only for the current chunk to keep physics updates fast.
2. Graph-Based Dungeon Logic
Don't generate your dungeon geometry first. Build a logical graph using AStar2D.
- Vertices: Represent "Rooms".
- Edges: Represent "Hallways" or "Doors".
- Benefit: You can easily run validation (is every room reachable?) before spawning a single mesh.
Deep dive (load on demand)
Drunkard walk, noise biomes, BSP, loot tables, WFC loops โ references/algorithm-recipes.md.
Reference
Progressive disclosure: open Official Documentation links only when researching a specific API; load Related Skills when routing to a peer domain โ do not preload the whole lattice.
Official Documentation
- FastNoiseLite โ seed, frequency, noise type, and
get_image()/get_noise_2d() for heightmaps and biome masks.
- Random number generation โ why per-generator
RandomNumberGenerator seeds beat global randi() for shareable runs.
- RandomNumberGenerator โ
seed/state APIs for deterministic sequences and undoable RNG history.
- Using multiple threads โ offload chunk/WFC work without freezing the main loop.
- Thread-safe APIs โ which Godot APIs workers may call; SceneTree/node creation stays on the main thread.
- WorkerThreadPool โ
add_task + call_deferred finalize pattern for async chunk generation.
- Using ArrayMesh โ commit vertex/normal/index arrays for marching-cubes and infinite terrain meshes.
- Using SurfaceTool โ incremental vertex building and normal generation for runtime planes.
- Using TileMaps โ TileMapLayer/pattern batch writes after BSP, CA, WFC, or drunkard-walk grids.
- Using GridMaps โ modular 3D cell placement backend for dungeon/terrain generators.
- Navigation introduction (3D) โ rebake NavigationRegion meshes after procedural geometry lands.
- AStar2D โ room/hallway graph validation before spawning tiles or meshes.
Related Skills
Prerequisites
- godot-project-foundations โ scenes, resources, and import basics before generators emit TileMaps, GridMaps, or ArrayMeshes.
- godot-gdscript-mastery โ typed arrays,
call_deferred, and WorkerThreadPool task patterns used across every generator script.
- godot-resource-data-patterns โ Resource-backed tile libraries, adjacency rules, and seed configs instead of hard-coded magic tables.
Complements
Downstream / consumers
- godot-genre-roguelike โ run-based dungeon crawlers that consume BSP/WFC/drunkard generators and seeded RNG.
- godot-genre-sandbox โ voxel/chunk worlds and cellular-automata sandboxes built on infinite terrain and CA scripts.
- godot-genre-open-world โ chunk streaming and floating-origin layers that wrap multi-threaded chunk gen.
Master
- godot-master โ library router and mirrored module entry for cross-skill discovery.