# About Procedural Architect Procedural Architect is a collection of Unreal Engine tools focused on being **easy to use at a basic level**, while remaining **powerful and adaptable** for production scale projects. ## Core Design Philosophy * **Simple by Default**: Tools are designed so that they are inherently useful directly out of the box, regardless of skillset or experience level * **Power and Extensibility**: Advanced customization is available, but always optional. All tools are designed to be easily adaptable to different use cases * **Designed to Scale:** Tools are designed with real world production in mind, considering iteration time, large worlds, and long-term maintainability * **Full User Control:** Tools are designed so they never sacrifice designer/artist control, while providing easier tools that leverage PCG capabilities * **Consistent Conventions & Patterns:** Tools follow consistent structure, naming and extension patterns. What you learn using one tool should usually transfer to the others. ## Who Is This For Procedural Architect Tools are intended for: * **Level Designers and Environment Artists** who want fast, reliable procedural tools without sacrificing designer control * **Technical Artists** who want a functional tool framework that can be easily extended * **Indie Teams** building production-scale environments * **Developers** who value clarity and structure in procedural systems **You do *****NOT***** need to be a PCG user** to use Procedural Architect tools. A core pillar is that all tools are inherently useful, before customization. However **if you ARE a PCG user**, the systems are designed to easily support advanced use cases and customization. All tools also come with templates and examples for new PCG users who want to explore these advanced features without needing to be an expert. ## A Growing Tool Suite Procedural Architect is not a single asset, but a suite of tools that all follow a shared design philosophy. All tools are built as independent plugins, but designed and build around the same design philosophy, conventions, and documentation structure. More info in the Shared Concepts section --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://better-faster-tech.gitbook.io/procedural-architect/procedural-architect/about-procedural-architect.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.