MOBA / mobile-first
Portrait 3v3 ARAM MOBA for Phones
Tested with Claude · produced BREAKWATER
The Prompt
Build a portrait-orientation 3v3 ARAM MOBA in ONE self-contained HTML file (Canvas 2D or WebGL, inline CSS/JS, no libraries, no external assets). The design constraint is the phone: one vertical lane, one thumb, one eight-minute match. Map and camera: - One lane running bottom-to-top between two island keeps, with two towers per side and a core objective at each end. The camera follows the hero with a fixed diagonal tilt; no free camera. - Random hero at match start, two bot allies and three bot enemies. No draft, no bans, no item shop. - Minion waves every 25 seconds, tower aggro rules (creeps before heroes, retaliate on hero attacks), and a visible objective health bar. Heroes: - Exactly eight heroes, four abilities each, one passive, one ultimate at level 5. Cover tank, bruiser, knight, assassin, marksman, mage, support and controller. Every kit must be understandable from a single fight. - Keep the total ability count at 32. Do not add a ninth hero until all eight have bots that use them competently. Combat and controls: - Mobile: left virtual stick for movement; tap a skill to cast at the nearest valid target, drag to aim skillshots; release outside the joystick to cancel. Large 56px targets and safe-area padding. - Desktop: right-click move and attack, hold Q/E/R to aim with a trajectory preview and release to cast, Esc or right-click cancels, F blink, S stop, diagonal MOBA camera. - Auto-buy items on a timer so gold matters without a shop screen. Show the next item and its arrival time. Bots: - Three difficulties (learning, normal, brutal). Bots must last-hit, retreat below 30% health, group for objectives and use ultimates off cooldown. Ban the behaviour where a bot walks alone into the enemy core. - Fixed 30Hz simulation tick with render interpolation. Seeded RNG; a match must be replayable from its seed. Testing and delivery: - Run 200 headless bot-vs-bot matches. Report average match length, side win rate, heroes never picked and any match under 4 minutes or over 15. - Print a single balance table for hero stats, ability damage, creep stats, tower damage and item timings. - Deliver in stages: one hero and creeps first, then towers, then all eight heroes, then bots, then the tide-cycle modifier as a separate pass.
What This Prompt Produces
BREAKWATER is the proof: one portrait lane, eight heroes, self-buying items, three bot difficulties and about eight minutes a match, built with Claude Opus 5.5 on a 1M-token context through Claude Code. Cutting the shop and the draft is what makes a MOBA fit a thumb.
Modification Tips
- Delete the item shop. Auto-buying items keeps the economy meaningful without a screen that a phone cannot comfortably show.
- Randomise the hero but keep eight, not twenty. Recognition in one fight is the whole skill ceiling of a one-lane MOBA.
- Put bot competence on the critical path. A 3v3 match with passive allies is unplayable no matter how good the heroes are.
- Simulate at a fixed tick and interpolate. Touch input jitter plus variable timestep makes abilities land differently on every phone.
The Game This Prompt Produced
Want to try it? Open Claude, paste the prompt, and you'll have a playable game in minutes. When you're happy with the result, submit it to Daily AI Games.