Arcade › Diamond Duel
Click the game above and it runs right here in your browser. No download, no installer, no account needed. brydenbarrera13 built it with Cinevva, so it works on a phone or a tablet too.
Nobody has said anything about Diamond Duel yet. Play it, then tell brydenbarrera13 what you would add next.
Diamond Duel was built by brydenbarrera13 with the Cinevva game creator: describe the game you want in chat, watch it get built, and play it in your browser minutes later.
Remix Diamond Duel opens the real game in the creator and forks its actual files, chat and design doc, so you start from the code rather than from a description.
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.
Recreate a browser-based 3D arcade baseball timing game titled “Diamond Duel: Nine Inning Showdown.” Use a Three.js-like real-time 3D scene with a fixed elevated camera behind home plate, looking toward center field. The setting is a compact stylized low-poly baseball diamond: vivid green circular grass/outfield, brown pitcher’s mound near the far side, white pentagonal home plate in the foreground, white chalk foul lines, three white bases, dark teal outfield wall, and two tall dark foul poles. Add small low-poly stadium banner props at the corners and a gold championship trophy prop to the right of the field. Light it brightly with soft shadows, a warm key light, cool rim light, dark navy sky/background, and subtle distance fog. The playable characters should be chunky low-poly animated 3D humanoids: a batter near home plate and a pitcher on the mound, with a matching runner model appearing on occupied bases. Team choice changes their colors and character theme; use visual equivalents for these selectable teams: Trojans (warrior), Cowboys, Kings (add a crown), Astronauts, Band (guitar-themed), Chefs, Vikings, Pirates, Thieves, and Ninjas. Keep the character models colorful, toy-like, and clearly readable rather than realistic. On launch, show a full-screen dark translucent team-selection overlay over the visible field. The overlay is centered and vertically scrollable on small screens. Display the gold uppercase kicker “CHOOSE YOUR TEAM,” the heading “Choose how to play,” two side-by-side buttons “🤖 Play vs CPU” and “👥 2 Player Mode,” then “Then pick your team” and ten large stacked team buttons labeled with the same emoji/name pairs: ⚔️ Trojans, 🤠 Cowboys, 👑 Kings, 🚀 Astronauts, 🎸 Band, 👨🍳 Chefs, 🛡️ Vikings, 🏴☠️ Pirates, 🕵️ Thieves, 🥷 Ninjas. Team buttons are disabled until a mode is selected and assets are loaded; show “Loading character teams…” and then “Now choose your team.” Selecting a mode highlights it gold. Selecting a team dismisses the overlay, chooses that team for the player, and automatically uses the first different team as the opponent. Show the matchup in the HUD as “Player Team vs Opponent Team • CPU” or “... • 2 Player.” The game is a nine-inning baseball showdown, beginning at the top of the first with the player batting. In each at-bat, throw one ball from the pitcher toward the plate along the z axis. The ball is a small white baseball with a red seam, visibly traveling toward the batter; in CPU mode, most pitches are fastballs and about 30% are curveballs that drift sideways. The player must press the large bottom-center gold/orange “SPACE BAR” button, click/tap it, or press Space (in the top half) when the ball reaches the plate. Also support W for batting in two-player mode. Make the timing mechanic explicit: show “NOW!” in the message area when the ball is in the hitting zone. Animate the wooden bat swinging when the player attempts a hit, and use the character attack animations or a clear stylized swing/kick substitute for hit and miss. Evaluate player batting by timing and horizontal accuracy. A well-timed, centered swing is a hit: the quality tiers produce single, double, triple, or home run, with the best timing producing a home run. Singles, doubles, and triples advance existing runners appropriately; home runs score one run plus all runners and clear the bases. Show result messages such as “SINGLE — batter on first,” “DOUBLE — ball into the outfield,” “TRIPLE — ball off the wall,” and “HOME RUN — over the fence!” Launch the ball into a visible flight arc with different trajectories for each result. On a miss, increment strikes and show “Swing and miss.” If the player does not swing before the pitch crosses the plate, call a strike when it is over the plate or a ball when it is outside. Display “Called strike — over the plate,” “Ball — outside the plate,” and “Ball four — walk.” Three strikes make an out; four balls reset the count and produce a walk. The implementation may preserve the source game’s simplified walk behavior (it resets count without fully advancing a batter). Use occupied-base state for first, second, and third. Turn occupied bases gold and place a matching low-poly runner model on them. Show base runners in the hint text, for example “Runner on 1B.” While batting in CPU mode, press S to steal; in two-player mode, press E during the top half. Stealing selects the furthest occupied runner, moves them to the next unoccupied base or home, scores if stealing home, and reports “Runner stole second/third/home!” or “Steal blocked — the next base is occupied.” If there is no runner, report “No runner is on base.” After the player’s three outs, switch to the bottom half of the inning: the opponent becomes batter and the player becomes pitcher. In CPU mode, the CPU automatically pitches and bats. The opponent attempts to swing as the moving ball nears the plate, with imperfect timing; successful CPU hits are randomly singles, doubles, or home runs and should show messages such as “Bot hit a single!” The source version tracks CPU hits and has a botRuns field but does not visibly add CPU runs to the main score, so keep the simple single-score presentation rather than inventing a second scoreboard if matching the original behavior. In two-player mode, show controls in the hint: “P1: W to pitch • P2: ↑ once fastball, ↑ twice curveball, ↑ to bat • E/↓ steal.” Player 1 presses W or the bottom action button to throw a fastball; Player 2 presses ArrowUp once to throw a fastball, twice quickly for a curveball, then ArrowUp again or the action button to swing. In CPU mode during the bottom half, the action button says “CPU PITCHING” and is hidden/disabled for batting; stealing uses S. The source’s two-player bottom-half hit path is intentionally lightweight, using hit animations and ball flight without the same player-run advancement as the top-half batting path. Run through top and bottom halves, resetting outs, count, and bases at each half-inning. Advance the inning after the bottom half; after nine innings, stop play and show “GAME OVER” on the main action button plus a RESTART button. Report a final message such as “Final score: 3 runs after 9 innings.” Allow restart by clicking RESTART or pressing R after game over. Use a persistent HUD over the 3D scene. At top left, put a dark translucent rounded panel with gold uppercase “DIAMOND DUEL,” the title “Nine Inning Showdown,” and the matchup/subtitle. At top right, put a matching stats panel with four columns: large RUNS score, COUNT shown as balls-strikes such as “0-0,” HALF shown as “T1” for top of inning or “B1” for bottom, and OUTS. Near the top center, show a dark translucent rounded message panel for current results and “Waiting for the pitch…”/inning status. Near the bottom center show a small hint line describing controls and base runners, above a large rounded gold-to-orange gradient action button labeled “SPACE BAR” (or contextually “P1 SWING,” “P2 SWING,” or “CPU PITCHING”). Use white bold sans-serif text, navy translucent panels, subtle borders/shadows, responsive mobile layout, safe-area padding, and touch-friendly controls. Keep the overall feel as a polished but simple arcade timing game with a dark teal sports broadcast UI and bright gold action accents.”,