LAST LINE GK

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 mobile-friendly 3D goalkeeper football game titled “LAST LINE GK.” Use a portrait-first, full-screen Three.js-style presentation with a dark navy background/fog and a simple low-poly 3D football pitch viewed from a high, slightly elevated camera behind/above midfield, looking toward the goalkeeper’s goal at the far end. Keep the camera centered on the goal but subtly follow the goalkeeper horizontally. The pitch is a dark green rectangular field (about 34 by 22 world units) with thin pale field markings: boundary, halfway line, and center circle. At the far end, build a white/silver goal with two posts, a crossbar, and a faint transparent wireframe net. Light the scene with bright soft directional and hemisphere lighting, shadows, and a cool blue rim light.

The player controls a blue-shirted goalkeeper standing just in front of the goal line. Give the keeper a simple stylized low-poly humanoid model: blue capsule-like torso, tan spherical head, blue arms, black lower legs. Place simplified outfield players around the pitch: eight blue home players and eight red/pink away players, each with capsule body, tan head, and black legs. They are decorative/ambient AI players that slowly drift toward broad role-based positions; they do not need complex ball possession. Place a white ball in front of the goal/attacking area. Away shots are automatically launched at intervals while play is active: a shot begins near the midfield/attacking side and travels toward a random target in the goal, with randomized horizontal target from roughly -4.5 to 4.5 and height from low to high. Simulate ballistic flight and bouncing/friction. Display a gold circular prediction marker at the target on the goal plane when the shot is fired; make this marker optional via a menu setting.

The core mechanic is reading each shot and moving or choosing the correct save action. Let the goalkeeper move within a bounded goalmouth area horizontally and slightly forward/backward. Movement uses a virtual joystick on mobile and WASD on desktop; Shift temporarily increases movement speed. Provide three save actions: dive left, jump/high save, and dive right. Desktop shortcuts are Q for left dive, Space for jump, and E for right dive. Mobile buttons are circular controls labeled “Q LEFT,” “▲ JUMP,” and “E RIGHT.” A left/right dive animates the keeper laterally with a rotation and gives a larger horizontal reach; jumping animates a vertical leap and is required or strongly useful for high shots. When the ball reaches the goal, evaluate whether the keeper’s horizontal distance and vertical reach match the shot: a successful action stops the ball and reports “DIVING SAVE,” “HIGH CATCH,” “CATCH,” or “PARRY”; otherwise concede a goal, increment the away score, and show “GOAL — TOO LATE.” Shots that miss the goal show “MISS.” Include simple generated sound effects for whistle, save, and goal using browser audio when available.

Build a start menu as a dark translucent, rounded glass panel over the scene. Show the large title “LAST LINE GK,” with “GK” highlighted cyan, and the tagline “Own the box. Read the shot. Make the save.” Include selectors for Team (Harbor City, Redwood Athletic, Northstar FC), Difficulty (Easy, Normal, Hard), Mode (Match, Penalty Mode, Training, Reflex Challenge), Match Length (90 minutes, 45 minutes, 10 minute demo), Shot indicator (On/Off), and AI Coach (On/Off), plus a prominent “START MATCH” button. Show the keyboard/mobile control instructions in the menu. Difficulty should affect shot timing/accuracy: Easy gives slower/easier shots, Normal is intermediate, and Hard gives faster/more difficult shots. Training should use a repeating set of predetermined low/high target heights and show a “TRAINING — READ THE MARKER” kickoff message; penalty mode should use penalty-like random target placement; reflex mode should use more frequent shots and end according to the game’s challenge condition.

During play, show a top HUD with a translucent scoreboard panel. It should read the selected team in uppercase followed by “· AWAY,” show the score as “0 — 0,” and show a clock such as “00:00 · PLAYING,” updating as the in-game minute advances. In Match mode, end when the selected match length is reached and show “FULL TIME — WIN” if home leads or “FULL TIME — DRAW” otherwise. Show transient large centered messages such as “KICKOFF,” “LOW SHOT,” “HIGH SHOT,” save results, “GOAL — TOO LATE,” and “MISS.” Include a rounded pause button in the upper-right with a pause icon; pressing it opens a centered PAUSED panel with RESUME and QUIT TO MENU buttons. On mobile, put the translucent joystick at bottom-left and the three action buttons at bottom-right; on larger screens make these touch controls subdued and use keyboard controls.

Optionally implement the AI Coach behavior shown by the interface: during Match play, periodically send the current minute, score, shot/save totals, ball horizontal position, possession, and half to a coach endpoint, then show a small centered translucent notification near the top reading “Coach AI: [short tactical note].” If no external AI is available, use a local fallback note such as “Local tactics active — keep your shape.” Keep the visual style clean, minimal, and premium: navy glassmorphism HUD, cyan/blue accents, gold shot marker, pale typography with uppercase letter spacing, rounded borders, and simple capsule characters rather than detailed stadium assets. The game should be playable from the initial menu through active saves, goals, pause, and end-of-match states.