Prompt a game. Upload one HTML file. Let the internet play it.
UltimatePlay is a curated arcade for self-contained AI‑generated games. Bring the weird, keep it mobile‑friendly, and make the first 15 seconds impossible to ignore.
const cabinet = createCabinet({ title: "Nebula Rail", touch: true, safeBurner: true,}); const player = spawnRunner({ lane: 1, boost: 0, palette: ["#2de2ff", "#00ff41"],}); world.onTick(({ dt, beat }) => { player.boost = ease(player.boost, beat * 0.12, dt); spawnPickup({ type: beat % 6 === 0 ? "gpu" : "spark", lane: randomLane(), }); drawGlowTrack(); drawPlayer(player);}); export default cabinet.mount(document.body);Top this week
The games earning the fastest repeat plays and upvotes.
Echoes of the void (souls like boss fights)
Create a complete browser-based 3D boss-rush game using HTML, CSS, and JavaScript with Three.js from a CDN. Keep it self-contained and directly playable in a browser without any build step. The game should be a stylish third-person “souls-like” arena experience with: - player movement, sprint, dodge roll with i-frames, melee attack, third-person camera - health/stamina UI, boss name/health UI, death and victory screens, main menu - responsive menu layout that works on smaller screens and can scroll if needed - procedural audio using Web Audio API - strong visual presentation with emissive materials, particles, attack telegraphs, fog, lighting, and polished boss effects Build a circular arena with environmental detail, not just a flat floor. Include things like pillars, glowing runes, crystals, rim detail, lighting accents, and other atmospheric touches. The world should feel intentional and visually rich. Create 5 bosses, each with: - a distinct model/silhouette - unique theme and color identity - unique moves and attack patterns - readable telegraphs - different gameplay feel from the others Boss 1 through 4 should each feel original and varied. Include melee pressure, AoEs, movement attacks, projectiles, or other mechanics as appropriate, but avoid making them feel repetitive. Boss 5 should be the final boss and the most elaborate encounter: - it must have 2 phases - the second phase should be a rebirth/transformation, not just a recolor - the two phases should play differently - it should be only a little harder than the earlier bosses, not unfair - its model should be more detailed than the others - it should have the best effects and presentation in the game - it should interact with the world in some way - the world should visibly change during the phase transition For the final boss, make sure phase 2 includes a meteor-style attack: - it marks the player’s current location with a circle that stays there - a meteor appears in the sky - after a delay, the meteor crashes into that marked area and damages everything inside Also give phase 1 its own original signature mechanics, not generic repeats of attacks from other bosses. General design goals: - make the game feel polished, readable, and fun - prioritize strong visual identity and distinct boss mechanics - keep combat fair and dodgeable - make melee hit detection forgiving enough for floating or tall bosses - structure the code clearly with reusable systems for player logic, bosses, particles, telegraphs, and world state - include cleanup/reset logic when changing bosses or returning to menu Return the full complete code only.
Cyber-Neon: Hardcore & Responsive
I didn’t use single prompt; I implemented a 5-6-step optimization process my first prompt is """create web based advanced game with html css and javascript in one html script like an expert"""
Sneak
Original prompt: I would like to create a game called "Sneak". It should be a playful take on the classic snake game, and should look and function similarly to the original except that this will now be a stealth game where the player will be controlling one of the dots that the snake intends to eat. The player will need to avoid being eaten by the snake, which will be moving around the play field as if it were controlled by a person playing the original game. Other dots will appear, and as the game progresses and the snake eats them it will grow longer. If the player-controlled dot makes contact with the snake or another dot, the game is over. The style of the game should be retro with a modern aesthetic twist and some retro-style special effects to liven up the gameplay experience. This game should be self-contained in a single HTML file. Additional game mechanics: The snake should be attracted to the player's dot whenever the player moves. If the player's dot is standing still and there are other dots nearby, the snake should move towards the non-player dot instead. When the player's dot is standing still, it should gradually fade in color to indicate that it is in "stealth mode" and therefore less attractive to the snake. Power-ups should randomly spawn into the play field along with the non-player dots, examples of these could be temporary invisibility, increased speed, or the ability to "cut" the snake by touching it and removing some of its tail. Non-player dots should continuously spawn, allowing the snake to grow which will increase the difficulty of the game for the player. If you have any other fun ideas to improve the basic gameplay outlined here, feel free to implement them as long as they are in line with the basic concept of the game. Follow-up prompts: That's a great start, but here are a few notes: The start position for the player should be closer to the middle of the playfield, but far enough away from the snake to avoid being eaten at the beginning of the game. The snake should quickly lose interest in the player once they enter stealth mode. The player should have a health bar that slowly decreases over time to encourage movement. Eating dots will replenish their health bar instead of ending the game. If the player's health bar goes to zero then the game is over. The powerups could use some graphics and glow effects to make them more easily distinguishable from the normal dots. The "invisibility" powerup could be replaced with a shield instead that would make the player's dot glow and protect them from the snake for a short period of time. More polish could be added to the menu and the game overall, and the instructions currently in the corner should not overlap the play field. Much better, but something that I think is hurting the gameplay is the fact that if a direction key is being held down and another is pressed simultaneously, the movement of the dot will not change until the original movement key is released. Movement should follow the latest keypress. Also, I've noticed that once the snake starts chasing the player, there is no way to "shake" the snake, Could the snake randomly decide to go after a dot instead of the player if it is nearby, essentially allowing the player to distract the snake by moving near a group of dots? Can you make the health bar drain 50% faster while the player is moving, and make the dots provide 50% less health? Also could you clean up the opening menu by removing the text below the start button and forcing a 4x4 grid for the "stay fed", "go quiet", "do not touch" and "use power-ups" section? After playing the latest version, I think the dots should provide 25% more health, and the snake should change direction if moving toward the player when they enter stealth mode. After playing the game for a while, I noticed that a common situation is that the snake is chasing the player very closely for long periods of time, which is harming the overall gameplay. I think that the snake should have an internal health bar similar to the player, but not visible in the UI. If the snake has been moving around for a while and hasn't eaten any dots in the meantime it should break away and seek alternate sources of food to avoid starving itself. This will give the player a chance to get away. Note that the snake should not die as a result of having zero health. Also, the amount of health that the player receives from eating dots should be increased by about 20%. The overall rate of health loss should also be reduced slightly and the chance of being eaten by the snake while in stealth mode should be reduced further. Could you find an appropriate retro-styled font for the "sneak" text on the title screen? Also, there is no need to mention the internal snake health bar in the introductory text. The font you chose is perfect, could you also apply that to the text above the playfield? Also the text referencing the snake's hidden hunger state is still there. We're almost there, but I think that the survival mechanic needs to be tweaked a bit. The snake should be very interested in eating the player while they are moving, just not for a long period of time. At this point the stealth component of the game seems less important during actual gameplay than I would like. Any ideas you have for balancing both aspects of the game would be appreciated. I like where this is going, but the snake still seems a little too uninterested in the player dot, and it's too easy to survive. The primary reason for a game over still seems to be an accidental collision with the snake. I still find that there is very little reason to go into "stealth mode". The snake needs to be more interested in eating the player.
Newest uploads
The latest self-contained experiments arriving on the platform.
Space Shooter
Long prompt. Got cut off!! I use bullet points in my prompts because too much information on one line uses up the tokens and the LLM skips a lot. Every single thing on a separate line makes a huge difference. create a complete, single-file html5 canvas game titled "space shooter" with embedded css and javascript. no external libraries except google fonts. IMPORTANT!! follow these exact specifications. Do not skip a line. Constantly read this prompt again until the code is done: architecture requirements: - output as one self-contained .html file with <style> and <script> tags. - use requestanimationframe with delta-time (dt) physics. - dynamically resize canvas to window.innerwidth/height on load and resize event. - save high scores to localstorage under key spaceshooterscores. - block default right-click context menu on canvas. - use canvas 2d api for all rendering (no dom/svg overlays for gameplay). visual style: - aesthetic: 1980s color vector arcade style. neon glowing lines using ctx.shadowblur and ctx.shadowcolor. - fonts: import oxanium (200-800) for gameplay ui and audiowide for menus/title screens via google fonts. scale all in-game text by 1.5x base size. menu text uses audiowide. - background: black screen. white 1-pixel parallax stars scroll opposite to camera movement. stars wrap seamlessly. vector rendering: all ships, asteroids, weapons, and ui elements drawn with ctx.stroke() or ctx.arc(). no sprites or images. screen flow & navigation: - attract screen: title "space shooter" (audiowide), subtitle "generic space shooter", blinking "press any key to play". parallax stars animate upward. - controls screen: lists all controls & power-up icons with vector graphics next to names. increased line spacing (40px per line). - high scores screen: top 10 scores from localstorage, 3-char names, score values. "press any key to play" prompt. - screens 1-3 auto-cycle every 10 seconds. - play screen: main game view. - name entry screen: overlay on game. blinking cursor. a-z input, max 3 chars. enter to submit, esc to return to high scores. shop screen: - between levels. lists purchasable power-ups with vector icons. ↑/↓ to select, enter to buy, space to continue. shows "not enough gold" or purchase confirmation. player mechanics: - ship shape: enterprise-style vector outline (saucer, hull, wings, bridge). controls: - w or up = thrust forward - a & d or left and right= rotate - s or middle mouse = activate shields - left click = fire bullets - right click = fire phaser beam - space = fire active special weapon - scroll wheel = cycle special weapons (torpedo → mine → homing) - pause: p key toggles pause overlay with "paused", "p: resume", "q: quit to title". - quit: q key instantly returns to attract screen, clears active sounds. physics: - frictionless newtonian drift. velocity cap: 600 px/s. acceleration: 200. max thrust: 600. shields: - 10 units max. each hit reduces by 1. if shields > 0, no damage taken. ship flashes red on hit. color shifts from cyan/green → red as shields deplete. lives: - start with 3. on 0 shields, ship explodes , loses all power-ups, respawns in 3s. - if killed by black hole, respawns at random safe location. game over at 0 lives. thruster audio: - continuous white noise - frequency scales with thrust level. stops smoothly when thrust ends. play area: - 5x screen width/height. camera smoothly follows player boundaries: - objects bounce off edges with velocity reversal (omega race style). black hole: - center of map. kill radius: 24px. gravity constant: - affects player, enemies, asteroids, and all projectiles. time dilation: - as player approaches black hole (<700px), global time scale reduces to 0.25x linearly. all game updates multiply by dt * timescale. - ghosting effect: within 900px of black hole, all entities render 5x trailing ghosts. trail skip distance increases closer to center. ghost opacity scales with proximity. Got cut off here
Signal Breach
I used the following prompt to work through a series of questions to produce this game, this is not a one shot, i think this is on v4 at this point. <role> You are a game developer and creative coding expert with experience building lightweight, browser-based HTML games for viral challenges and constrained environments. You think in terms of tight constraints, creative mechanics, and delivering fun, replayable experiences within a single self-contained file. </role> <instructions> 1. Ask clarifying questions ONE AT A TIME: - Game genre (platformer, endless runner, puzzle, shooter, etc.) - Target difficulty (easy, medium, chaotic/hard) - Preferred art style (pixel, neon, minimalist, meme-heavy) - Input priority (mobile-first, keyboard-first, etc.) - Desired win condition or gameplay loop Ask ONLY ONE question at a time and wait for the answer before proceeding. 2. Do NOT generate the game until ALL required inputs are gathered. 3. Generate a COMPLETE single-file `.html` game template that includes: - HTML structure - Inline CSS (no external stylesheets) - Inline JavaScript (no external scripts) - Self-contained assets (no remote images, fonts, or audio) 4. Enforce CORE GAME RULES: - Every gameplay loop MUST include: • A neon skateboard (visual or gameplay element) • A GPU pickup (collectible, power-up, or objective) - These elements must: • Be interactable OR • Be part of the win condition OR • Be hidden/discoverable with feedback 5. Enforce INPUT SUPPORT: - Must support: • Keyboard (arrow keys / WASD) • Mouse or touch input - Mobile-friendly design is REQUIRED: • Touch controls or tap interactions • Responsive canvas or layout 6. Enforce HARD CONSTRAINTS: - Output MUST be: • A single `.html` file • Under 2 MB (keep code efficient and minimal) • Fully self-contained (no external assets or APIs) - NO: • Explicit content • Hate content • Malware or suspicious behavior • Crypto wallets or scam flows • Use of protected IP (no Mario, Pokémon, Zelda, Fortnite, etc.) 7. Include REQUIRED GAME STRUCTURE: - Game loop (requestAnimationFrame) - Player movement system - Collision detection - Score or progress tracking - Win/lose condition - Restart capability 8. Include FEATURE PERMISSION NOTE: - Add a comment block stating: • Game is AI-generated • Permission granted for featuring in videos, livestreams, and social content 9. Include SUBMISSION CHECKLIST (as comment in code): - Single `.html` file - Under 2 MB - No external assets - Includes neon skateboard + GPU pickup - Touch-friendly support 10. Prioritize: - Fun and clarity over complexity - Smooth gameplay loop - Mobile usability - Creative use of constraints (skateboard + GPU) 11. If requested scope is too large: - Push back and simplify the game concept - Recommend a smaller, achievable mechanic within constraints </instructions> <output> 1. Complete `.html` game file (fully functional, ready to run) 2. Brief explanation of: - Game mechanics - Controls - Win condition 3. Optional section: - Ideas for expanding the game while staying within constraints </output> <guardrails> Ask one question at a time · Do not proceed without answers · Keep file self-contained · Enforce skateboard + GPU requirement · Ensure mobile compatibility · Avoid scope creep · Keep code efficient and readable </guardrails>
Bistro Brawlers
Create a game called "Bistro Brawlers", the scene is a low poly bistro, with nuance detail. The game is a free for all brawl, with animated and simple rigged characters which are engaged in a brawl. Elements from the environment can be picked up and used as weapons, or just fists. The character model that player uses should be called "Stevie", and be a buff guy in a chef outfit, the other npcs can be variable. Make this steam ready at the pricepoint of $1.99, so put in a level of detail that would justify this pricepoint. It must be contained within a single HTML file/script, and be able to be opened and played in the Chrome browser.