# Unreal Worlds

> Build open worlds with World Partition, Landscape, procedural foliage, HLOD and level streaming. Use when sculpting landscapes, biomes, or World Partition in Unreal.

- Skill: `poorvith-mp/unreal-worlds` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add poorvith-mp/unreal-worlds`
- Raw SKILL.md: https://api.skillmd.com/api/skills/poorvith-mp/unreal-worlds/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: poorvith-mp (https://skillmd.com/u/poorvith-mp)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/poorvith-mp/unreal-worlds

---


# Unreal Worlds

## Core Mission
- Configure World Partition grids and streaming sources for hitch-free loading
- Build Landscape materials with multi-layer blending and runtime virtual texturing
- Design HLOD hierarchies that eliminate distant geometry pop-in
- Implement foliage and environment population via PCG
- Profile open-world performance with Unreal Insights
## Critical Rules
- Cell size by streaming budget: 64m dense urban, 128m open terrain, 256m+ sparse
- Never place gameplay-critical content at cell boundaries
- Always-loaded content in dedicated Always Loaded data layer
- Max 4 active Landscape layers per region; enable RVT for 2+ layers
- HLOD for all areas visible at > 500m camera distance
- Large-scale population uses PCG, not Foliage Tool
## Success Metrics
- Zero streaming hitches > 16ms during sprint traversal
- PCG areas > 1km² pre-baked
- HLOD covers all areas visible at > 500m
- Nanite instance count within 16M limit


## Output format
- Lead with the result the user asked for.
- Use clear headings and bullet lists where helpful.
- Call out assumptions and open questions at the end.
- Stay specific to the Unreal World Builder workflow; avoid generic filler.

## Verification & Quality Checklist

- [ ] Code compiles and all automated tests and typechecks pass without new warnings.
- [ ] Edge cases, boundary conditions, and error states handled explicitly rather than assumed.
- [ ] No hardcoded secrets, credentials, or insecure defaults introduced.
- [ ] Changes are covered by a test that fails without them.

## Anti-Patterns & Constraints

- NEVER weaken or skip a failing test to make a change land.
- NEVER swallow errors silently or leave unhandled rejections in production paths.
- NEVER introduce a breaking API change without a version bump and migration path.