LA NAVE ESPECIAL
- 3
- Plays
- 0
- Like
- 0
- Comments
About this game
Build a browser game for Tapverse, a platform where people play games instantly on phones and computers. MY GAME IDEA: Crea un juego 2D estilo arcade espacial con estética pixel art. El jugador controla una nave en la parte inferior de la pantalla que se mueve de izquierda a derecha con las flechas y dispara láseres con la barra espaciadora. Desde arriba caen asteroides y naves enemigas a velocidad creciente. El jugador tiene 3 vidas, suma 10 puntos por cada enemigo destruido y pierde una vida
How to play
Build a browser game for Tapverse, a platform where people play games instantly on phones and computers.
MY GAME IDEA: Crea un juego 2D estilo arcade espacial con estética pixel art. El jugador controla una nave en la parte inferior de la pantalla que se mueve de izquierda a derecha con las flechas y dispara láseres con la barra espaciadora. Desde arriba caen asteroides y naves enemigas a velocidad creciente. El jugador tiene 3 vidas, suma 10 puntos por cada enemigo destruido y pierde una vida si choca o si un enemigo llega abajo del todo. Añade un marcador en la esquina superior y un botón para reiniciar al perder.
REQUIREMENTS: - Type: single player - Orientation: portrait - Camera / microphone: none - Reply to me in Spanish; keep code comments in English.
Follow the Tapverse game rules below exactly, and build on the starter template after them: keep its structure, platform helpers and phases, and replace the example game with mine. Deliver the complete index.html, then the two cover image prompts and the "How to play" paragraph the rules describe.
===== TAPVERSE GAME RULES (tapverse-games skill) ===== --- name: tapverse-games description: Platform rules for building or fixing a browser game that will be uploaded to Tapverse (playtapverse.com) — packaging, the Tapverse SDK, multiplayer rooms, the players' 3D characters, touch controls (analog joysticks), screen orientation, camera/microphone, gamepads, ads and what the game frame allows. Use whenever making, porting, updating or debugging a game for Tapverse, single-player or multiplayer. ---
# Building games for Tapverse
> **To an AI building a game from someone's idea:** follow every rule here. If the idea conflicts > with a rule, keep the rule and explain the change briefly. Reply in the person's language; keep > code comments and identifiers in English. If they attached a Tapverse starter template, build on > it: keep its structure, platform helpers and phases, and replace the example game. > > **Deliver:** (1) the complete `index.html` (everything inline, or a folder with `index.html` at > its root when the game needs separate assets) including the manifest of §2; (2) two image > prompts for the covers: one 16:9 landscape and one 9:16 portrait, main subject in the center > 60%, bright colors on a dark background, no text except the title (see §2 for where cards crop); > (3) a short "How to play" paragraph for the game's description; (4) three to five moments of > play worth a screenshot for the game's page (what's on screen and when). > > **Every game has:** a start screen (title, big Play button, one-line how-to; nothing starts or > sounds before that tap), a pause button and a mute toggle while playing, a paused screen > (Resume, Restart), and a game-over/results screen (Play again, and a "Watch an ad to continue" > button when there's a natural second chance, see §4). Short UI text, big numbers, English and > Spanish from `navigator.language`. Touch and mouse via Pointer Events, keyboard on desktop. > On touch screens, movement or steering uses an on-screen **analog joystick**, never left/right > arrow buttons, and actions are buttons (≥ 56 px) under the right thumb (§7); tap targets > ≥ 44 px, no hover-only or long-press interactions. Every screen works with the phone **upright > and sideways**, including short landscape heights (§3). 60 fps on a mid-range phone, frame > time capped (~50 ms). Show player-typed text with `textContent`, never `innerHTML`.
Tapverse runs each game in its own sandboxed iframe on its own origin (`https://<slug>.tapversegames.com`), embedded by `https://playtapverse.com`. Games are static files only: no server code. Everything below is what the platform actually enforces or provides.
1. Package
- Upload a single **`index.html`**, or a **`.zip`** with `index.html` at its root (or inside one top-level folder). `__MACOSX/`, `.DS_Store`, `Thumbs.db` and `.git/` are ignored. - Limits: **50 MB** zipped, **200 MB** unzipped, **1000 files**, paths ≤ 300 characters. Aim for < 5 MB so phones open it in seconds. - No file may live under `_tapverse/` (reserved by the platform). - **Use relative paths** (`assets/hero.png`, `./js/main.js`). The entry page redirects to `/v/<version>/`, and files there are cached forever, so each update reaches players at once. Absolute paths (`/assets/...`) still load but are revalidated on every visit (slower), and break on test deploys that serve games under `/g/<slug>/`. - Served with the right type: html, js/mjs, css, json, png, jpg, gif, webp, avif, svg, ico, mp3, ogg, wav, m4a, mp4, webm, wasm, glb, gltf, bin, data, ktx2, hdr, woff/woff2, ttf, otf, txt, xml. Other extensions are sent as `application/octet-stream`. - Pre-compressed builds work: files ending in `.br` / `.gz` (e.g. Unity's `game.wasm.br`) are sent with `Content-Encoding` and the type of the extension underneath. No extra loader settings needed. - Libraries may load from public CDNs; pin exact versions. - Engines: Phaser, PixiJS, three.js, Babylon.js, p5.js, Kaplay → zip the build folder with `index.html` at the top. Unity → WebGL build (Brotli or Gzip both work) without multithreading. Godot 4 → Web export with Thread Support off (the default since 4.3); Godot 3 as is. GameMaker, Construct 3, GDevelop, PlayCanvas, Defold, Emscripten/Rust, pygbag, RPG Maker, PICO-8, Twine, Ren'Py, TurboWarp → their HTML5/Web export. Not supported: native apps (APK, iOS, desktop executables) and builds that need `SharedArrayBuffer`.
2. Manifest (read on upload)
Put it in `<head>` of `index.html`. Creator Studio pre-fills the upload form from it.
```html <script type="application/json" id="tapverse-manifest"> { "spec": 1, "title": "Space Cat", "description": "Tap to boost, collect fish, don't crash.", "tags": ["arcade", "casual"], "orientation": "any", "multiplayer": false, "permissions": [], "permissionReason": "", "controls": ["touch", "keyboard"], "aiTool": "Claude
What's new
Version 1 · November 16, 2026
Information
- Players
- 1 player
- Controls
- Touch Keyboard and mouse
- Screen
- Both
- Uses
- No camera or microphone
- Age
- 13+