King Goku

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.

Create a browser-based interactive narrative game titled “King Goku — Prologue,” a dark Three.js visual novel / palace court drama set in an alternate ancient Israel around 1000 BCE. The player is Goku, an anointed/forgotten son whose face remains hidden behind a wooden box, and the story follows his rise from an unseen musical presence to new palace guard, battlefield legend, wilderness leader, and crowned king.

Use a fixed first-person/scene-like 3D palace hall backdrop: a very dark purple-black floor, tall simple cylindrical columns arranged along the hall, a distant dark back wall, fog, warm directional/hemisphere lighting, and two orange-gold torch lights glowing near the back. Keep the 3D environment minimal and atmospheric; the main gameplay is the UI overlay and text.

Build a choice-driven visual novel with 21 linear story chapters and branching choices that mostly reconverge. Start with Goku off-screen in the prologue after Israel’s Amalekite campaign: spoils have been taken, Agag is chained as a living trophy, Saul is unstable, Samuel is distant, David already serves Saul with a harp, and David and Michal are in love. The opening chapters cover the Amalek battle aftermath, Saul’s dark chamber and David’s harp, spoils and Agag’s chains, Michal and Merab’s court tension, Samuel’s absence, and mysterious nighttime harp music at the gate. Then let the player start Chapter 7, where Goku arrives as a new guard with a box over his face. Continue through Saul’s command, Goku’s confrontation with the giant Goliath, the one-elbow victory, Joab’s nonlethal spar, the “Saul has struck down his thousands, and Goku his ten thousands” song, the fracture between Michal and David, night music, Saul’s summons and javelin attack, flight into the wilderness, the gathering of 400 outcasts, cave years, and return and crowning.

Each scene displays a chapter title, speaker name, narrative text, and 1–4 large clickable choice buttons. Choices change relationship meters and move to the next scene. Include keyboard support: Space advances when a scene has an available advance behavior, and R restarts the story. Clicking a choice should trigger a subtle autoplay-safe Tone.js triangle-synth harp-like blip; initialize audio on the first click or keydown. Include Restart and Codex buttons in the top bar.

Track per-character meters from 0–100, clamped to that range, representing feelings toward Goku: Love, Hate, Care, Jealousy, and Mindbreak. Show a meter panel beneath the story with a card for every character and labeled horizontal bars plus numeric values. Include at minimum Saul, Ahinoam, Jonathan, Michal, Merab, Ish-bosheth, David, Samuel, Abner, Agag, Jesse, Eliab, Abinadab, Shammah, Joab, Goliath, and the 400 Outcasts. Use distinct bar colors: love pink/red, hate red-orange, care green/cyan, jealousy amber/red, and mindbreak purple/dark. Initialize the story with the shown relationship values, including Saul hate 12, care 18, jealousy 6, mindbreak 10; Jonathan care 22; Michal care 12; Ahinoam care 14; David care 6; Samuel care 8; Agag hate 15, and the other low values shown in the design.

Implement specific narrative effects: when Goku crosses into the courtyard in Chapter 7, apply a one-time instant-arrival spike across the cast before the scene renders—Saul jealousy +12, mindbreak +10, hate +4; Ahinoam care +6; Jonathan care +10/love +6; Michal love +14/care +8/jealousy +4; Merab love +6/jealousy +12/hate +2; Ish-bosheth jealousy +10/mindbreak +4; David jealousy +16/hate +2; Samuel care +4; Abner care +3/jealousy +2; Joab jealousy +8/hate +2. Also apply scene-enter effects such as the Chapter 13 ten-thousands song increasing Saul’s jealousy and mindbreak and later crowning effects increasing Jonathan/Michal/Outcasts’ love and care while pushing Saul’s jealousy, hate, and mindbreak.

The story tone should be dramatic, psychological, mythic, and occasionally romantic but PG-13: intense longing, blushing, jealousy, implied/brief kisses only, no explicit sexual content. Make the prose atmospheric and choice consequences emotionally legible. Goku is physically extraordinary but presented as gentle, naive, calm, protective, and reluctant to hurt people: he defeats Goliath with one clean elbow, wins Joab’s spar without unnecessary injury, survives Saul’s javelin because the weapon breaks on him, leads the 400 with rules and restraint, refuses to start civil war, and is ultimately crowned.

The main UI should be a nearly black translucent overlay with thin gray-purple borders, rounded panels, light lavender/white text, bold large headings, and warm accent colors. At the top show “King Goku — [current chapter]” on the left and Codex / Restart buttons on the right. Center or lower-center show the speaker, story text, choices, and a hint reading “Click a choice. Or press Space to advance when available.” Beneath it show “Meters (toward Goku — not present yet)” during the prologue. Make the interface responsive for desktop and mobile.

The Codex must open as a modal overlay over the dimmed game, matching the visible style: a large dark rounded rectangle, heading “Codex,” subtitle “Approx ages/heights are interpretive (ancient sources aren’t exact),” and a Close button. Inside, show the complete chapter plan and roster cards with name, role, approximate age, approximate height, upcoming story beats, and short descriptions. Include the characters’ stated details, especially Saul (king, mid-40s, about 6’2”), Jonathan, Michal, Merab, David, Samuel, Agag, Joab, Goliath, Goku (forgotten son/new guard, late teens, 5’9”), and The 400 (outcasts). Restart must return to the initial prologue node and restore initial meters. Avoid portraits, free-roam, combat controls, inventories, or invented mechanics; this is a text-and-choice narrative game over a simple 3D palace scene.