Overview
Perlin Worms is a procedural generation method that turns seeds, rules, noise, or constraints into repeatable generated content. It is useful when generated content needs repeatability plus controllable variation.
CoreSource checked
Perlin Worms
Perlin Worms uses rules, noise, or constraints to synthesize repeatable generated content.
Quick Facts
Compact metadata for implementation and discovery.
- Category
- Procedural Generation
- Difficulty
- Intermediate
- Family
- Procedural Generation
- Tier
- Core
- Status
- Verified
- Review
- Source Checked
- Sources
- 2
- Formulas
- 1
- Relationships
- 1
- Code example
- Ready
- Visualization
- Ready
Core Concepts
seeded randomnesslocal ruleconstraint propagationseedrule systemgenerated structure
Quick facts
Complexity
Runtime and memory behavior at a glance.
Best
O(n)
Average
O(n)
Worst
O(n^2)
Space
O(n)
When to Use
- Use Perlin Worms when its rules can express the desired structure without heavy manual cleanup.
- Use it when generated output can be validated for playability, connectivity, or constraints.
When Not to Use
- Avoid when the rule set cannot express the needed design constraints.
- Avoid when generated output must be hand-authored or exactly reproducible without a seed.
What It Does
- Expands rules or random choices into structure
- Maintains constraints or local patterns
- Returns generated content from repeatable inputs
Use Cases
- Game content generation
- Terrain creation
- Pattern synthesis
Inputs
- Seed
- Rules or constraints
- Generation parameters
Outputs
- Generated terrain, layout, pattern, or content
Key Formulas (1)
Worm step
positionnext = position + direction(noise(position)) · stepsize
position_next = position + direction(noise(position)) * step_sizeAdvances a tunnel or vein path through a noise-guided direction field.
Pseudocode
- 1.Initialize the seed, rules, and generation state
- 2.Apply the method's local rule, random choice, or constraint
- 3.Update generated structure
- 4.Repeat until completion
- 5.Return the generated content
Canonical Example
- Input
- seed = 42, rules = small rule set
- Output
- generated layout or pattern
- Explanation
- Perlin Worms expands deterministic rules and random choices into generated content.
Implementation Notes
- Keep seeds and rule versions in generated artifacts.
- Add validation passes for connectivity, bounds, and required content constraints.
Common Pitfalls
- Changing rule order can create large output changes from small parameter edits.
- Not validating generated content can leave unreachable or unusable regions.
Interactive Mechanism Walkthrough
Spatial Primitive & Sweep-Line CanvasShow the generated structure growing or resolving from seed values and rules.
Step 1 of 5: Initialize the seed, rules, and generation state
procedural-generationNotes
Perlin Worms operates in O(n) time and O(n) space within the Procedural Generation family. Key governing relation: position_next = position + direction(noise(position)) * step_size. Often compared with Perlin Noise and Wave Function Collapse.
Sources (2)
What each reference supports for this entry.
Perlin Image Synthesizer
PaperOriginal Perlin noise reference supporting coherent procedural paths and noise-driven structures.
Open sourceTexturing and Modeling: A Procedural Approach
BookProcedural texturing reference supporting Perlin Worms noise, tiling, terrain, growth, or pattern-generation mechanism.
Explore Next
Good next jumps from the relationship graph, ranked for useful discovery.
Relationships
View full relationship pageConceptual neighborPerlin Noise
Perlin Worms and Perlin Noise address nearby procedural generation problems but make different implementation tradeoffs.
Related Algorithms
Tags
Procedural Generation