Meat Mallet

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 fullscreen responsive browser arcade game titled "Meat Mallet". Use a 2D HTML canvas covering the viewport, with a dark burgundy-to-near-black vertical gradient background. Add subtle atmospheric decoration: faint reddish circular blobs drifting across the lower background and thin, low-opacity horizontal grill-like lines. Use a clean system sans-serif UI with warm cream text, pinkish secondary text, and red/burgundy accents.

The game starts on an attract/start screen. Keep the HUD visible at the top: three dark translucent rounded cards with thin muted-red borders and soft shadows, laid out left, center, and right. They display uppercase labels and large values: "SCORE" with 0, "TIME" with 30, and "COMBO" with "x1". In the center around the upper-middle of the screen show a very large cream heading "MEAT MALLET" with a dark red offset/shadow beneath it, the subtitle "Flatten the steaks before the timer runs out.", and a prominent rounded coral-red button labeled "Start pounding". The button should have bold white text, a darker red bottom shadow, and a pressed state that moves slightly down. At the bottom center show the hint "Tap or click the glowing steaks — desktop: use the mouse" in muted pink.

When the player presses the start button, begin a 30-second timed round, hide the start message, reset score to 0 and combo to 1, and continuously spawn glowing stylized steaks in the playable area. Spawn one steak initially after the round begins and then periodically; the interval is approximately 0.88 seconds early in the round and gradually decreases slightly as time runs down, never below 0.42 seconds. Place each steak at a random x position with enough margin for its roughly 40–62 pixel radius, and a random y position between about 145 pixels from the top and 92 pixels from the bottom so it does not overlap the HUD or bottom hint. Each steak should have a random slight rotation, a subtle independent pulse animation, and a randomized lifetime between 2.3 and 3.7 seconds.

Draw steaks as irregular rounded meat blobs, not geometric circles: a dark red outer silhouette with a strong coral/red glow, a lighter red inner shape, several curved pale fat/grill-like streaks, and a couple of small light pink fat dots. Keep the style flat/vector-like with soft canvas shadows. The player taps/clicks on a steak using mouse or touch/pointer input. A hit succeeds if the pointer is within about 1.2 times the steak radius. Remove the hit steak, add 10 points multiplied by the current combo, then increase combo by 1 up to a maximum of x9. On a successful hit, emit a brief expanding pale impact ring and around 14 small orange square particles that burst outward, arc under gravity, and fade out. Missed clicks do nothing. If any steak reaches its lifetime without being hit, remove it and reset the combo to x1.

Keep the HUD live: score increases as described, time counts down in seconds and displays the ceiling of the remaining time, and combo displays as x1 through x9. End the game when the timer reaches zero, stop spawning and input, save the best score in local browser storage under a persistent high-score key, and show a centered end message reading "DINNER'S READY", followed by "You scored [score] points." and "Best: [high score]", plus a button labeled "Pound again" with the same coral styling. Pressing it resets and starts another 30-second round. Persist and update the high score across rounds/page reloads.

For extra visual feedback during play, draw a simple stylized meat mallet at the lower-right area of the canvas: a tan wooden handle and a wide pale wooden head with a darker red-brown top strip, tilted slightly and gently oscillating. It is decorative and does not need to track the pointer. Make the canvas support high-DPI displays and resize cleanly with the viewport. Disable page scrolling and browser touch gestures over the canvas; both touch and mouse should work through pointer events. Ensure the overlay buttons remain clickable while the canvas itself handles steak taps.