Unreal Tournament Codexery

Maze

Every corridor is a choice; every turn, a gamble.

Maze

AS_Maze is an Assault map from the original Unreal Tournament (1999), developed by Epic Games. It presents a labyrinthine corridor structure with multiple branching pathways connecting the flag spawn to the objective, forcing attackers to choose between routes while defenders rotate to cover the most likely approach. The map's design philosophy centers on uncertainty and spatial disorientation: rather than a single wide avenue, the layout splits into several narrow passages that converge and diverge, making each run down the corridor a small tactical gamble for the flag carrier.

Map name
AS_Maze
Game
Unreal Tournament (1999)
Primary game mode
Assault
Developer
Epic Games
Layout type
Multi-path corridor / labyrinth
Naming convention
AS_ prefix denotes Assault mode

Lore & Background

In the Unreal Tournament setting, Assault maps are framed as high-stakes flag-capture operations. AS_Maze fits this template by presenting what reads as a subterranean or enclosed structure whose corridors have been carved into a deliberately confusing network. The architecture suggests either an old facility repurposed for military drills or a natural rock formation hollowed out over time—either way, the result is a space where line-of-sight is short and the geometry itself becomes an obstacle. The map's design leans into the idea that knowledge of the layout is a weapon. A defender who memorizes which branch leads to a dead end, or which corridor offers a flanking angle, gains a persistent advantage over an attacker who must read the space in real time. This makes AS_Maze a map that rewards memory and pattern recognition as much as raw aim. As with most UT1 Assault maps, the flag spawn sits in a relatively open area while the objective is tucked into a more confined space, creating a natural funnel that the maze's branching paths both protect and complicate.

In Their Own Story

The flag hums against the carrier's back as the corridor narrows. Left, the passage opens into a wider junction where the faint echo of footsteps bounces off stone. Right, the hallway pinches to a single-file squeeze, the ceiling low enough to force a crouch. Ahead, the path forks again—three mouths breathing cold air, each one potentially a dead end, each one potentially the way through. The carrier commits to the center route, boots crunching on gravel, and rounds the bend to find a defender already waiting, shotgun raised, grinning. The flag drops. The maze resets. And somewhere in the dark, the next carrier is already choosing a different path.

Reader's Guide

Visual theme: AS_Maze presents a stone-and-rock corridor aesthetic with a labyrinthine floor plan. The geometry is defined by narrow passages, branching junctions, and occasional wider chambers that serve as respite points. Lighting is generally dim, emphasizing the enclosed, subterranean feel. Key areas and sightlines: The flag spawn area is the most open zone on the map. From there, the path splits into multiple corridors of varying length and width. Chokepoints occur where passages narrow to single-file width, making them ideal for ambush. Wider junctions offer brief sightlines across to adjacent corridors, allowing defenders to peek and reposition. The objective area is more confined, creating a natural bottleneck. Best game modes: Assault is the intended mode, and the map's multi-path design creates genuine uncertainty about the attacker's route. It can also function in Free-For-All, where the branching corridors produce frequent close-quarters encounters. Design notes: The maze layout means no two runs are identical from a tactical standpoint. Players who memorize the optimal route gain a significant edge, making the map a test of spatial memory as much as reflexes. Rotating between two or three routes keeps defenders honest.

Did You Know?

More in Maps & Locations

Elsewhere in the Unreal Tournament universe

Spotted an error? Know more?

This is a living reference — every entry is fact-audited, and reader corrections feed straight into our audit queue. Suggest an edit · See this site's audit record

Comments

Loading…
Open in the interactive codex →