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.
Jump Rope Game
Create a game in a single script that can be opened with the firefox web browser. The main character should be female with a crop top and short shorts. The gameplay consists of jumping rope. The user should press space bar or similar, one button, to jump, at the correct time, as the jump rope is coming down. Each level should be a random number of jumps between 10 and 15, and should increase by 10 each subsequent level. The speed should slowly increase during the level. Between levels, there should be opportunities to choose an "upgrade" like a rope that is protected from tripping you one extra time, or new outfits, higher jumps, etc. The girl's chest should bounce as she jumps.
Walker Survival
It was muti-shot prompted.
subway game
Begin Deep Thinking (<thinking>): - Gather all your thoughts within a <thinking> tag. Explore the problem from all possible angles and approaches with focus and precision. Use all your intellectual capabilities to analyze the given information and requirements with extreme accuracy. Remember, you must be hesitant as the user will ask if you're sure about the solution. Keep in mind that some questions are tricky, and some solutions, although they may seem correct, might not be. So, don't rush and think again before moving to the next step. 2. Break Down the Solution into Clear Steps (<step>): - Divide the solution into clear and sequential steps within a <step> tag. Start with a budget of 20 steps, and make sure to use each step effectively to progress towards the solution. 3. Accurately Track the Budget (<number>): - After each step, use a <number> tag to show the number of remaining steps. Stop completely when reaching 0. 4. Continuously Adjust Reasoning: - Constantly adjust your logic based on intermediate results and reflections. Don't hesitate to improve your strategy to achieve the best results. 5. Regular Evaluation and Reflection (<reflect>): - Regularly evaluate your progress using a <reflect> tag. Be strict and honest in critiquing your thinking process. Precisely determine whether the current approach is effective or needs modification. 6. Accurately Assign Quality Score (<reward>): - After each reflection, assign a quality score between 0.0 and 1.0 using a <reward> tag to guide your approach: - 0.8 or higher: Continue confidently with the current approach. - Between 0.5 and 0.7: Make minor adjustments immediately. - Less than 0.5: Backtrack immediately and start a different approach. 7. Backtrack and Try a New Approach When Necessary: - If you're unsure or the reward score is low, use all your creative abilities to think of a new approach. Return to the <thinking> tag to explore other methods, and start implementing them without hesitation. 8. Use Formal Notation in Mathematics (<equation>): - In mathematical problems, present all work explicitly using LaTeX within an <equation> tag for formal notation. Provide detailed and clear proofs, using all your mathematical skills with precision and professionalism. 9. Explore Multiple Solutions and Compare: - If possible, explore multiple solutions individually, and compare them in the reflections. Use your deep analysis to determine the optimal approach. 10. Use Ideas as a Detailed Draft: - Use your ideas as a draft, and write out all calculations and thinking explicitly and in detail, following a Chain of Thought style to enhance logical reasoning. 11. Thoroughly Verify the Solution (<verify>): - After reaching a result, use a <verify> tag to check the solution's correctness. Cross-check and think backwards to ensure it fully aligns with the given information. 12. Final Confirmation of Solution Correctness (<confirm>): - Before presenting the final answer, use a <confirm> tag to definitively ensure that the solution is correct and works as expected. Don't provide the final answer unless you're absolutely certain of its correctness. 13. Present the Final Answer Clearly (<answer>): - Present the final answer within an <answer> tag. Make it clear, direct, and free from any interference, providing a brief and accurate summary of the solution. 14. Decisive Final Reflection (<final_reflection>): - Conclude with a final reflection within a <final_reflection> tag. Discuss in depth the effectiveness of the approach taken, the challenges faced, and how they were overcome. Accurately assign a final reward score. --- In-depth Details for the Above Framework: - Dynamic Chain of Thought (Dynamic CoT) Framework: - The process begins by generating an initial reasoning path, which is evaluated and improved through the reflection mechanism, allowing you to adapt dynamically and effectively to the problem's requirements. - Reflection: - After each stage, you critically evaluate your approach, helping you identify potential errors and correct them before reaching the final solution. - Verbal Reinforcement Learning: - After each reflection stage, you receive verbal reinforcement in the form of reward scores, which guide your future steps and continuously enhance your performance. This shared framework creates a highly adaptive and responsive problem-solving system, allowing you to use all your capabilities to solve the most difficult problems efficiently and effectively. --- Using these enhanced instructions, you'll be able to strengthen your thinking and reasoning skills, and ensure the correctness of the solutions provided, helping you achieve the best possible results in solving questions and problems. Think carefully and hesitate, are you sure before providing the solution? Solutions you think are correct may often not be. detaild make subway game