Appearance
Arcade › Slice Storm
Click the game above and it runs right here in your browser. No download, no installer, no account needed. Alexis Licor built it with Cinevva, so it works on a phone or a tablet too.
Nobody has said anything about Slice Storm yet. Play it, then tell Alexis Licor what you would add next.
Slice Storm was built by Alexis Licor 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 Slice Storm 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.
Create a full-screen responsive arcade game titled “Slice Storm,” inspired by Fruit Ninja and rebuilt as a clean Three.js-style 3D scene viewed through an orthographic camera. Use a dark radial-gradient background transitioning from blue-gray near the top to nearly black, with soft fog, subtle lighting, a faint blue elliptical floor glow near the bottom, and a field of small dim stars. Keep the camera fixed facing the play area straight on so the game reads like a 2D arcade screen while objects have stylized 3D shading and rotation. At launch, show a centered modal overlay over the scene. The modal is a dark translucent rounded card with a thin light border and shadow. Display the title “Slice Storm,” followed by: “Drag across fruit. Miss 3 fruit and you're out. Hit one bomb and it’s over.” Include a bright pill-shaped orange-to-pink gradient button labeled “Start Slicing.” Clicking/tapping the button starts a new round and removes the overlay. After game over, reuse the overlay with the button labeled “Play Again” and show the relevant end message, either “Boom. You sliced a bomb. Click to restart.” or “Three fruit got away. Click to restart.” During play, spawn waves of objects from along the bottom of the play area. Each object launches upward with randomized horizontal velocity and upward velocity, follows a ballistic arc under gravity, moves sideways, and spins in 3D. Objects should leave the bottom if not sliced. Spawn one or two objects per wave initially, increasing the wave count by up to two as elapsed time passes. Spawn waves increasingly often, with the interval decreasing toward about 0.38 seconds; also gradually increase launch speed. Keep the play field broad, approximately 16 world units wide, with launch positions around y=-8.7 and removal below about y=-9.8. Most objects are colorful fruit spheres with a small green leaf cap and brown stem. Randomly choose from these fruit appearances: red apple, light green lime, orange fruit, purple plum, blue blueberry, and pinkish watermelon. Use bright saturated colors, soft physically shaded materials, and varied sphere sizes around 0.5–0.72 world units. Fruit slicing is performed with mouse or touch dragging: while the pointer is held, convert its screen position to world position, connect recent positions into a short fading bright white/cyan line trail, and test each movement segment against every unsliced object. A hit occurs when the segment passes within the fruit radius plus about 0.35 units. On a successful fruit hit, remove it, emit a burst of roughly 18 small colored juice particles with gravity and fading opacity, and show an expanding fading colored ring splash at the hit location. Add bombs as occasional dark charcoal-gray spheres, slightly smaller than fruit, with a tan angled fuse and a small pulsing red glowing tip. Their chance starts around 10%, rises gradually over time, is capped around 22%, and do not allow bombs to spawn consecutively. The player must avoid them: slicing a bomb immediately ends the round, pauses the game, resets the combo, displays the bomb end message, and updates the best score if needed. Bomb hits can still produce a red particle/ring burst. Scoring and rules: start each round with score 0, combo 0, and 3 lives. A sliced fruit awards 10 points plus 2 points for each current combo level, then increments the combo. Every third consecutive slice gives an additional 15-point bonus. When a normal fruit falls off-screen unsliced, reset combo to 0 and subtract one life; add a small white miss particle burst near the bottom. When lives reach zero, end the round and show the “Three fruit got away” message. Store the best score persistently and display it across rounds. The game’s difficulty level is conceptually 1 plus one per 18 seconds of elapsed play. Place a fixed translucent HUD across the top with three rounded glass-like panels: left panel shows “Score” and “Best” with their values; center panel shows “Combo” and “Lives”; right panel shows the current status text, initially “Drag to slice fruit,” and a smaller hint “Avoid bombs — click or tap to start audio.” On narrow screens stack these panels vertically. Update score, best, combo, and lives immediately as gameplay changes. Use a clean Arial-like sans-serif, white text, subtle borders, backdrop blur, and shadows. Support mouse and touch dragging, including pointer down/move/up and touch equivalents. A click/tap should initialize browser audio. Use soft Tone.js synth sounds if available: a short triangle blip for a slice, a brighter score sound (two notes for combos of three or more), a low miss sound, and a deeper bomb sound. Pressing the M key toggles mute and changes the status to “Muted” or “Audio on.” The game should render continuously with responsive resizing, an orthographic camera, antialiasing, tone mapping, and animation of fruit rotation, particles, splashes, the fading slash trail, subtle world sway, and slowly rotating stars. There are no cutscenes; the core experience is the real-time slicing challenge.