Last Stand

Cinevva's analyzer read this game's design doc and its source, then wrote the brief below. "Make your own" hands it to the game creator as your opening message, so you start from a real spec rather than a one-line idea.

Rebuild a game titled “Last Stand,” a tense 3D fortress-defense command simulation. The game has a dark, polished medieval strategy UI and an isometric/top-down Three.js battlefield view rather than direct character control. The player is an abstract commander: there is no controllable avatar, movement, aiming, or attack mode; the commander manages defensive positions, gate pressure, repairs, and limited resources while an automated siege unfolds.

Start with a full-screen main menu on a dark navy/charcoal radial-gradient background, centered in a rounded translucent panel. Show the title “☠ LAST STAND” in large, widely spaced gold lettering and the subtitle “A desperate fortress defence — one commander, one fortress, no reinforcements.” Present three selectable fortress cards in a responsive grid (one column on narrow screens):
- SMALL CASTLE: “One gate. Compact courtyard. A single point of failure.” One gate, 18 starting defenders. This is selected by default.
- LARGE FORTRESS: “Four gates. The commander must divide limited forces.” Four gates, 30 starting defenders.
- ALAMO-STYLE FORT: “A surrounded compound with buildings and no safe direction.” Four gates, 22 starting defenders.
Selected cards have a gold outline and warmer background. Include a large gold/brown “BEGIN LAST STAND” button, a “🏅 Badges” button, and an “⚔ Attack — Coming Soon” button. The attack button only displays a short “Only Last Stand is playable in this first version.” toast. Include the note “1 in-game minute = 20 real seconds. Hold for 90 minutes.”

When a map is selected and started, hide the menu and show a full-window 3D battlefield. Use a fixed elevated perspective camera positioned around (0,23,22) looking at the fortress center, with a 42-degree perspective view. Render soft shadows, fog, a hemisphere light, and warm directional sunlight. The ground is a large flat plane: green-gray for Small Castle/Large Fortress and dusty brown for the Alamo-style fort. Build the fort from simple gray stone walls forming a square enclosure, a muted tan courtyard floor, and gold gate markers. Small Castle is compact (roughly size 9) with one gate centered on the north wall. Large Fortress is larger (roughly size 13), has gates centered on all four sides, plus simple low internal cross-walls. Alamo-style is medium sized (roughly size 11), has four gates on north/east/south/west and four blocky tan compound buildings inside the walls. Add several small low stone defensive-position blocks around the interior. Use low-poly medieval castle assets where available: gray stone wall pieces, narrow gate pieces, siege towers outside the fort, and stylized medieval soldier models. Siege towers should appear outside the perimeter; defenders are small idle medieval figures placed around the gate positions. The camera should remain an observer/commander view with no player movement.

The game simulation begins with these map values: Small Castle starts with 18 defenders and 130 resources; Large Fortress starts with 30 defenders and 170 resources; Alamo-style Fort starts with 22 defenders and 145 resources. Every real second advances simulation time by 1/20 of an in-game minute, so the target is 90 in-game minutes. The simulation periodically evaluates each gate, automatically concentrates enemy pressure on one gate at a time, moves the visible defender groups toward their assigned gate, and produces toast notifications such as “Enemy concentrating at Gate 1,” “2 defenders lost,” and “[gate] breached — commander falling back.” Pressure rises at the selected gate and decays elsewhere. Gate hit points begin at 100; pressure damages the focused gate based on pressure versus available defenders. As time and pressure rise, defenders are randomly lost. A gate breaches below 35 HP, increasing retreat/adaptation behavior. The overall fortress percentage is the average gate HP. The player loses if defenders reach zero or fortress strength reaches 4% or less. The player wins only by surviving to 90 in-game minutes, with a result alert saying “IMPOSSIBLE HOLD — 90 minutes survived.” On defeat, show “THE FORTRESS HAS FALLEN. Survived [minutes] in-game minutes.” Return to the menu after the result.

Overlay a compact commander HUD. At the top, use a dark translucent rounded stat bar with gold labels and bright values for: SURVIVAL TIME (“0 / 90 MIN” through “90 / 90 MIN”), DEFENDERS, FORTRESS (percentage), RESOURCES, and PRESSURE. Pressure displays LOW below 12, RISING below 28, otherwise CRITICAL. Include buttons for “🗺 MAP,” pause (Ⅱ, changing to ▶ while paused), and a bottom action panel with “🔧 Repair Gate,” “🪵 Barricade,” “🧱 Fortify Wall,” a speed toggle initially “1×,” and “Menu.” Near the bottom center show a pill-shaped hint such as “Commander focus: Gate 1 · holding line” or “North Gate breached · FALL BACK.” Toast notifications appear near the top center in a dark pill with gold border.

The commander’s current focus is automatically selected by the simulation according to gate damage, pressure, random tactical variation, and prior adaptation; show the focused gate in the HUD hint. Make the actions apply only to the currently focused gate: Repair Gate costs 18 resources, restores up to 18 HP, reduces pressure by 8, and marks the gate reinforced; Barricade costs 24, reduces pressure by 18 and restores up to 6 HP; Fortify Wall costs 30 and restores up to 28 HP while marking the gate reinforced. If resources are insufficient, show “Not enough resources.” Resources also slowly drain during the siege. Pause freezes simulation and changes the icon to a play triangle; the speed button toggles between 1× and 4× and displays a testing/fast-forward toast. Menu disposes the active scene and returns to fortress selection.

The MAP button opens a centered “TACTICAL MAP — COMMANDER VIEW” modal over a darkened screen. Draw a simple 2D schematic on a dark canvas: a tan square perimeter, yellow square gate/fortification markers with gate labels, blue defender dots, red enemy dots outside connected to gates by red lines, and an orange warning symbol near critically damaged gates. Include a legend for Defenders, Enemy, Gate / fortification, critical, and movement, plus a Close button.

Include a Badges screen accessible from the menu, using the same dark panel style. List locked/unlocked badges with trophy/lock icons and descriptions, persisted in local storage: “First Line” (survive 10 in-game minutes), “Holding the Wall” (30), “Against All Odds” (60), “IMPOSSIBLE” (survive all 90), “Encircled but Alive” (all gates breached), “Never Surrender” (continue after more than two retreats), and “Last Defender” (only one defensive group remaining / two or fewer defenders). The badge screen header should indicate “🛡️ DEFENCE — COMING SOON   ⚔️ ATTACK — COMING SOON” and provide a BACK button.

Use a restrained, readable visual style: charcoal/navy overlays (#12161d range), slate borders, pale gray text, warm gold for titles, gate markers and emphasis, red for breached/critical states, blue for defenders, and muted stone/tan/brown world materials. Make controls large enough for touch, responsive on mobile, and preserve the single-screen HUD layout. Avoid inventing combat controls, reinforcements, player weapons, or additional playable modes: this first version is specifically an automated last-stand defense with commander interventions and three fortress layouts.