DungeonArchitectBasic

Build dungeon layouts directly in the Unreal Editor, then use the saved geometry and runtime actors in your game. Configure seeded rooms, corridors and multiple floors, with your own meshes, materials and room actors.

Upgrade note: terminals no longer bind E/W/S/arrow keys automatically. Connect your input actions to Interact and Select Previous/Next Floor. Add DABInteractionComponent to replicated player pawns for remote-client terminal commands. Get Current Stop Index returns -1 while moving; handle this as an in-transit state.

Choose instanced geometry for an editable dungeon actor or generate a persistent merged Static Mesh asset. Add ceilings, windows, corner pillars, point lights, automatic doors and elevator connections as your layout needs them.

FEATURES

- Seeded room and corridor generation with optional loops and multiple floors.

- Hierarchical Instanced Static Mesh output or a saved merged Static Mesh, with optional Nanite settings for the merged asset.

- Custom floor, wall, ceiling, door, pillar, elevator platform and terminal meshes, with bounds alignment and axis controls.

- Optional runtime doors with opening modes, auto-close delay, window frames and sound.

- Multi-stop elevators and terminals, including aligned elevator towers and optional pawn-overlap auto-call.

- Callable terminal interaction functions for your own input actions, UI or interaction system.

- Replicated pawn interaction component for server-validated multiplayer terminal requests.

- Current-level generation and clearing with Undo, locked-level protection and preservation of existing Player Starts.

- Optional actor spawning in rooms, materials, windows, pillars and lighting.

WORKFLOW

Open Dungeon Architect Basic from the Window menu or Dungeon toolbar button, choose your settings and generate. Inspect the result, save your level and generated mesh assets, and connect your player's input to the terminal interaction functions.

Layout generation runs in the editor. Doors, elevators and terminals run in gameplay. The plugin does not include a player character, input mappings or a finished UMG interface; use the documented entry points to connect your project. Custom mesh collision, navigation and character traversal should be configured and tested in your game.