# PCGEx adds graph, path and spatial nodes to Unreal's PCG

> PCG Extended Toolkit is an Unreal Engine 5 plugin that extends Epic's Procedural Content Generation framework with graph construction, pathfinding, spatial queries, filters and asset management, with several companion plugins for ZoneGraph, constraint solving and cluster sketching. It suits a technical artist building procedural pipelines, and the plugin is tied to specific engine branches.

**PCGEx/PCGExtendedToolkit** —  The missing pieces for Unreal's PCG. Graph theory, advanced pathfinding, spatial ops, filtering, asset management, and more. 

- Repository: https://github.com/PCGEx/PCGExtendedToolkit
- Website: https://pcgex.gitbook.io/pcgex
- Stars: 707 · Forks: 102
- Language: C++
- License: MIT
- Published: 2026-10-21 · Updated: 2026-10-21 · Language: en
- Canonical page: https://hysenlabs.com/projects/pcgex-pcgextendedtoolkit

## What the plugin adds to Epic's PCG framework

PCGEx is described as a node and feature ecosystem for advanced PCG in Unreal Engine, covering graph theory, pathfinding, spatial ops, filtering, asset management and more, and the README frames it as a wide node ecosystem that extends Unreal Engine's PCG framework with structure, connectivity and spatial intelligence. The list of what that means in practice is more useful than the label. You can build graph networks from points and then pathfind through them, compose filters and heuristics as reusable sub-nodes, stage assets, sample across datasets, manipulate paths, and streamline the sorting, fusion, partitioning and attribute work that complex workflows demand. The primary language is C++ and the plugin ships as a .uplugin file with Config/, Content/, Resources/, Scripts/ and Source/ directories at the top level. The plugin describes itself as fully documented and production-ready, with the documentation hosted on GitBook and a Deep Wiki badge linked as a second reference.

## Branch discipline is the thing to understand first

The branches section in the README is a diff block, and it is unusual to see a project document its stability policy this way. The main branch compiles against the latest launcher engine binaries and is described as unstable. The 5.x branches compile against that version of the engine and are described as stable. And there is a FAB-5.x branch served to the Epic marketplace, with some features disabled, since it has no precompiled headers and no tooling or cherry-picking scripts, which means it can be unstable during submission windows. The note underneath is the one to hold on to, that PCGEx is actively maintained only for 5.7 and above. The support note says the plugin is actively developed for the latest 5.x version and that most updates are backported to 5.x-1 if Epic's APIs are not too widely diverging. In practice that means your engine version decides your branch, and an engine older than 5.7 is on a branch that receives no new work.

The policy is written as a diff:

```diff
- main
Compiles against latest launcher engine binaries
(this an unstable branch)

+ 5.x
Compiles against that version of the engine
(these are stable branches)

! `FAB-5.x`
Served to FAB and have some features disabled
(no PCHs, no tooling/cherry-picking scripts);
they can be unstable during submission windows.
```

## Three companion plugins for problems PCGEx does not solve alone

Under the PCGEx Pro umbrella sit a small ecosystem of more narrowly targeted plugins that build on the core one, and each maps to a distinct production problem. PCGEx with ZoneGraph generates ZoneGraph roads and polygons from clusters, which is how you get navigable street data out of point clouds rather than authoring it by hand. PCGEx with Valency is a constraint solving pipeline using wave function collapse and a free-form connector grammar, which is the approach for laying out things like road networks where every piece has to fit its neighbours. PCGEx with Cluster Sketch creates clusters by hand with per-element data layers, which is the tool for when the algorithm gets you most of the way and a human has to finish it. The pattern across the three is that each one is a bridge from a procedural result to something an engine subsystem can use, and each is a separate product rather than a mode of the core plugin.

## The third party geometry libraries are the dependency to read

The acknowledgements section names the third party libraries, and these are worth reading before you commit, because the two listed do real work inside the plugin. delaunator-cpp, a fast Delaunay triangulation implementation, covers the triangulation half of the geometry work, and the repository topics reflect that with delaunay, voronoi and minimum-spanning-tree among the tags. Clipper2, by AngusJohnson, is a modified C++ port at version 2.0.1, and it handles polygon clipping and offsetting, which is what makes the Voronoi and region work possible. A THIRD_PARTY_NOTICE.md file sits at the repository root, so the licensing terms for both are recorded there, and since the plugin is MIT and the project describes itself as free for personal and commercial use with attribution appreciated but not required, the third party terms are the part of the licence picture you need to check yourself. The acknowledgements also credit individual contributors for the areas they drove, including PCG framework guidance from Epic Games staff, Linux support, and macOS compatibility work.

## Distribution through source, Fabric and the marketplace

There are three ways to get the plugin, and they are not equivalent. The documentation includes a Getting Started section, an Installation page, and a link to Epic's FAB listing, which is the marketplace route and corresponds to the FAB-5.x branch with features disabled and no precompiled headers. The repository itself is the source route, where you would build the plugin against the engine version matching your chosen branch. The documentation also ships a node library overview and an example project, and there is a getting started path for the two. One detail that tells you the project expects a lot of reading is the AI assistants note, which points at an llms.txt and an llms-full.txt on the GitBook so a language model can consume the documentation. That is a deliberate choice by the maintainers and worth knowing about if you plan to work with the plugin through an assistant, because the same content is available in a form that is easier to keep accurate.

## Conclusion

Adopt PCGEx when your procedural content pipeline in Unreal Engine needs connected graph data, pathfinding or spatial reasoning that the built-in PCG framework does not provide, and when you can target one of the supported engine branches. Do not adopt it on a branch that is not maintained, since the project states it is actively maintained only for 5.7 and above while main is unstable. Verify first which engine version your project uses against the branch table, whether your build can come from source or from the marketplace listing, and that the third party library terms in THIRD_PARTY_NOTICE.md are acceptable for your project.

## FAQ

### What does PCGEx add to Unreal Engine's PCG framework?

It adds a node ecosystem covering graph theory, pathfinding, spatial queries, filtering, asset management and data work. You can build graph networks from points, pathfind through them, compose filters and heuristics as reusable sub-nodes, stage assets, sample across datasets and manipulate paths, alongside the sorting, fusion, partitioning and attribute handling that complex workflows need.

### Which Unreal Engine versions does PCGEx support?

The badge covers 5.8 and 5.7 and earlier versions down to 5.3, but the branch notes say PCGEx is actively maintained only for 5.7 and above. The main branch compiles against the latest launcher engine binaries and is unstable, the 5.x branches are the stable ones, and FAB-5.x is served to the marketplace with some features disabled.

### What do the PCGEx Pro companion plugins do?

PCGEx with ZoneGraph generates ZoneGraph roads and polygons from clusters, PCGEx with Valency provides a constraint solving pipeline using wave function collapse and a free-form connector grammar, and PCGEx with Cluster Sketch creates clusters by hand with per-element data layers.

### What third party libraries does PCGEx depend on?

Two are named in the acknowledgements, delaunator-cpp for fast Delaunay triangulation and a modified C++ port of Clipper2 at version 2.0.1 by AngusJohnson for polygon clipping and offsetting. Their terms are recorded in the THIRD_PARTY_NOTICE.md file at the repository root, separately from the plugin's own MIT licence.

## Sources

- [License: MIT](https://github.com/PCGEx/PCGExtendedToolkit/blob/main/LICENSE)
- [PCGEx/PCGExtendedToolkit on GitHub](https://github.com/PCGEx/PCGExtendedToolkit)
- [Project website](https://pcgex.gitbook.io/pcgex)
- [README](https://github.com/PCGEx/PCGExtendedToolkit/blob/main/README.md)
- [Releases](https://github.com/PCGEx/PCGExtendedToolkit/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/pcgex-pcgextendedtoolkit