# Towards Friendly Mixed Initiative Procedural Content Generation: Three Pillars of Industry

arXiv: https://arxiv.org/abs/2005.09324 · HTML: https://mlsanity.com/paper/2005.09324/

## Key facts

- Cited by 5 papers in the map (data through 14 Oct 2026).
- First posted on arXiv 19 May 2020.

## Built on by (most cited first, 5 of 5)

- [Hierarchically Composing Level Generators for the Creation of Complex Structures](https://mlsanity.com/paper/2302.01561/) (2023)
- [Design-Driven Requirements for Computationally Co-Creative Game AI Design Tools](https://mlsanity.com/paper/2107.13738/) (2021)
- [Procedural Generation of 3D Maps with Snappable Meshes](https://mlsanity.com/paper/2108.00056/) (2021)
- [Optimists at Heart: Why Do We Research Game AI? (Extended Version)](https://mlsanity.com/paper/2206.03261/) (2022)
- [Heuristics for AI-driven Graphical Asset Generation Tools in Game Design and Development Pipelines: A User-Centred Approach](https://mlsanity.com/paper/2503.02703/) (2025)

## Abstract (arXiv)

While the games industry is moving towards procedural content generation (PCG) with tools available under popular platforms such as Unreal, Unity or Houdini, and video game titles like No Man's Sky and Horizon Zero Dawn taking advantage of PCG, the gap between academia and industry is as wide as it has ever been, in terms of communication and sharing methods. One of the authors, has worked on both sides of this gap and in an effort to shorten it and increase the synergy between the two sectors, has identified three design pillars for PCG using mixed-initiative interfaces. The three pillars are Respect Designer Control, Respect the Creative Process and Respect Existing Work Processes. Respecting designer control is about creating a tool that gives enough control to bring out the designer's vision. Respecting the creative process concerns itself with having a feedback loop that is short enough, that the creative process is not disturbed. Respecting existing work processes means that a PCG tool should plug in easily to existing asset pipelines. As academics and communicators, it is surprising that publications often do not describe ways for developers to use our work or lack considerations for how a piece of work might fit into existing content pipelines.
