Strategy & technique
70 guides written by the people who designed and tuned these games. Specific advice, real numbers taken from the source, and an honest account of what we have and have not tested.
The 20 in-depth guides that cover a whole topic properly. Start here.
The genre
A monster arcade game is a short, score-driven browser game built around repeated attempts. Here is what actually defines the genre, the six shapes it takes, and why the format survived the arrival of everything else.
Library guide
Not a ranking — a route. Which of our thirty monster games to play first, what each one actually teaches, and the order that introduces one new demand at a time instead of all of them at once.
Under the hood
What is actually happening behind a monster arcade game: the loop, the state machine, how difficulty is calculated, why every enemy telegraphs, and where the numbers in our other guides come from.
Category deep dive
Why platformers feel precise when they are built well: coyote time, jump buffering, variable jump height, and the heavy-gravity arc that makes a jump land where you meant it to.
Category deep dive
Battle games are won by watching, not by reacting. How telegraphs work, why mid-distance is the most dangerous place on the board, and how wave and upgrade systems shape a run.
Category deep dive
Runners are the easiest category to start and the hardest to hold. What separates the five here, why every run ends the same way, and the rhythm trap that causes most plateaus.
Category deep dive
Adventure games are the thinking end of the library: spatial freedom, an objective, and a resource that makes every detour cost something. How routing works and why banking beats greed.
Systems
Phases, telegraphs, the twenty per cent learning bonus and the counter-strategy for each boss design in the library. Why you should spend the first cycle of a new phase watching rather than attacking.
Category deep dive
Gems, eggs, tokens and treasure — what each spawn pattern is telling you, why the multiplier matters more than the haul, and what a 'token' actually is on a site with no currency of any kind.
Getting better
The habits that actually move a score, in rough order of how much they are worth: where you look, what you pre-decide, how you protect a chain, and when to stop playing.
Category deep dive
One button, one decision, and nothing to blame. How timing windows are sized, why we never go below 80 milliseconds, and the trap of chasing perfects.
Systems
How a game generates content that has never existed before and is still fair. Chunk templates versus per-obstacle generation, the constraint that guarantees playability, and what improves when nothing repeats.
Systems
What our Easy, Medium, Hard and Expert labels actually mean, why every curve here is asymptotic, and the difference between a game that is hard and a game that is unfair.
Systems
Ten power-ups, what each one actually does, and the single rule that governs when to use them: make a hard section easy, never an easy section faster.
Systems
The multiplier is the score. How chains build, why they time out as well as breaking, what a cap of ×10 does to a game, and the arithmetic that makes caution the greedy option.
Playing well
Which games actually fit into two minutes, which ones only look like they do, and why the instant restart is simultaneously the genre's best feature and its worst trap.
Technical
What is actually happening when a monster game runs in a browser tab: the canvas, the frame loop, device pixel ratio, why there are no image files, and how a whole game fits in a few kilobytes.
Playing well
Touch controls designed alongside the desktop ones rather than bolted on: where buttons go and why, which games work one-handed, and the specific ways phone play differs from desktop.
Design notes
How we build a level set that teaches: introduce alone, combine later, never surprise. The eight-level structure of Monster Castle, and the rules a procedural generator has to follow to do the same job.
Context
Why creatures have been arcade antagonists since the beginning, what changed when games moved into the browser, and which constraints are gone versus which were design choices all along.
50 shorter articles on a single technique, question or category.
Technique
Obstacles are not the problem — pairs of obstacles are. How to read the visual language, why early is safer than late, and the three habits that cause most avoidable collisions.
Technique
Practical ways to respond faster that do not involve trying to react faster: gaze position, pre-commitment, posture, sound, and knowing when to stop.
Technique
Specific technique for single-button games: where to look, why you keep missing early, how to handle a narrowing window, and the scoring band that is worth ignoring.
Strategy
Concrete combo play: when to be greedy, when to protect, how to rebuild after a break, and the routing habit that keeps a chain alive through empty space.
Strategy
A practical checklist for boss fights: what to do in the first ten seconds, how to use a phase change, when to stop attacking entirely, and how to decide a fight is not winnable today.
Strategy
How to add distance to an endless run: breaking your own rhythm, managing commitment length, deciding how greedy to be with collectibles, and the session-level habits that matter more than any single technique.
Technique
Concrete platformer technique: reading platform types, handling crumbling stone and moving platforms, wall sliding, and what to do the instant a jump goes wrong.
Strategy
Route planning that survives contact with a map: clearing dead ends first, collecting in passing, banking early, and how to judge whether the high-value detour is still affordable.
Systems
The shared collectible system behind every game on the site: types, values, magnetisability, spawn patterns, and the update loop that resolves a pickup.
Technique
A shield absorbs one hit, so its value depends entirely on which hit. Why shields are most valuable when you are healthy, and the specific situations worth spending one on.
Technique
A speed boost is the power-up most likely to end a run. Why +45% movement is a liability in tight spaces, where it genuinely pays, and how it interacts with low-friction surfaces.
Systems
The specific dials that get turned as a run progresses, what each one feels like from the player's side, and how to tell which one is beating you.
Systems
Seven movement behaviours cover every creature in the library. What each one does, how to recognise it within a second, and why creatures are frozen during their own wind-up.
Technique
Every boss tell in the library, what it looks like in the first tenth of a second, and how to build a recognition habit that survives a phase change.
Strategy
Navigating a generated maze under pressure: why corners beat corridors, how to plan a loop rather than a back-and-forth, and what changes when hunters stop patrolling.
Environments
What the cave setting does mechanically: restricted vision, vertical layouts, falling hazards from above, and why a shrinking light radius is a better timer than a clock.
Environments
Why castles suit platformers: verticality, hard architecture, mechanical hazards on fixed cycles, and the readability that comes from a world made of rectangles.
Environments
The jungle setting is about layers: a safe ground line and a lucrative high line. How vine swinging works, when to release, and why parallax density is an accessibility question.
Environments
Volcanic levels are about a floor that is coming for you. Climbing efficiently, reading cracked ledges, using walls, and why hesitation is the only real cause of death here.
Environments
Low friction converts a spatial problem into a temporal one. The exact retention figure, why turns must start two body-lengths early, and how to read a curving trail before entering it.
Environments
Swimming is not walking. Buoyancy, four-directional momentum, a breath meter that drains faster at depth, and why banking matters more here than anywhere else on the site.
Environments
What removing or inverting gravity does to a game: hovering, momentum without friction, and why a zero-gravity boss fight is harder than the same boss on the ground.
Creature types
Designing a creature that reads as alien without becoming unreadable. Silhouette rules, why unfamiliar shapes are risky in a fast game, and where our alien creatures appear.
Creature types
Machine creatures are the most learnable enemies in any arcade game, because machines repeat exactly. Cycles, armour phases, and why predictability is a design feature rather than a flaw.
Creature types
Building an original fantasy bestiary without borrowing one: what makes a creature design ours, how the roster is structured, and why the friendly-looking ones matter.
Creature types
Playing as the enormous thing inverts every obstacle. How scale is sold, why momentum replaces collision as the failure state, and what changes when obstacles break instead of blocking.
Creature types
Shadow creatures are the library's hunters: line-of-sight pursuit, convergence behaviour, and the visual language that makes a chaser readable without making it harmless.
Strategy
Deciding what to take and what to leave: reading value against distance, handling high-value clusters placed far from safety, and the banking threshold worth setting in advance.
Systems
What a token is on a site with no currency: how values are assigned, why they differ between games, and an explicit statement of what these objects are not.
Systems
A closer look at the generators: tagged chunk templates, weighted selection, guaranteed routes, and the difference between a generator with rules and a random number generator.
Design notes
Escalation started as a way to end runs and turned out to be the only structure that makes an endless game meaningful. What it does for the player, and what happens without it.
Technique
A step-by-step method for reaching a high multiplier and keeping it: the opening, the climb, the plateau, and the specific behaviours that break chains without you noticing.
Systems
Six scoring metrics, what each one rewards, why they are not comparable between games, and how to tell which number you should actually be playing for.
Technique
What is fixed, what is trainable, and the four components of a response that you can genuinely shorten — with a practice routine built from games on this site.
Technique
Timing is a different skill from reaction: it is about anticipating a known moment rather than responding to an unknown one. How to practise it, and why consistency beats accuracy.
Controls
Every touch layout on the site explained: what each control does, where it sits, how the virtual stick handles deadzones, and the habits that make thumb play accurate.
Controls
Practical advice for playing on a phone: grip, screen space, battery, interruptions, and which games to avoid on a small screen.
Controls
The complete keyboard and mouse reference: every key, what it maps to, why several keys share an action, and the accessibility details behind the scheme.
Technical
A closer look at canvas rendering: draw order, why art is code rather than images, the cost of a gradient, and how a creature is assembled from primitives.
Technical
What browser games can and cannot do, why these load in under a second, which browsers are supported, and what to try if a game runs badly.
Design notes
Four properties that make a short game worth a twentieth attempt: cheap failure, legible failure, visible improvement and a variable outcome — and what happens when any one is missing.
Accessibility
What we have built, what we have not, and the gaps we would rather name than imply away. Keyboard access, reduced motion, contrast, pausing and the honest limits of a canvas game.
Design notes
How an enemy is designed here: one behaviour, one tell, one counter. Why telegraphs freeze a creature, and the rules that keep a roster readable as it grows.
Design notes
An obstacle is a question with exactly one correct answer. How commit cost drives spacing, why colour carries the answer, and the difference between a hazard and a trap.
Design notes
Designing a boss that teaches while it fights: phase structure, the twenty per cent learning bonus, why attacks are shared across bosses, and what makes a boss different rather than merely tougher.
Design notes
Four requirements every power-up must meet, why banking one is more interesting than triggering it, and the state model that lets effects stack without conflicting.
Design notes
How a level set should escalate: one new thing at a time, a mid-set breather, and a final level that combines rather than invents. With the shapes used by our three level-based games.
Technical
Exactly what is written to your browser when a run ends, why there is no leaderboard, what happens when storage is blocked, and how to clear everything.
Design notes
Feedback, pacing and the small details that make a mechanically identical game feel better: screen shake, particle timing, popup text, and why silence after an action reads as a bug.
Reference
Every term used across this site, defined once: commit cost, coyote time, telegraph, chain window, asymptotic curve, greed pocket and the rest.
If you are new to the genre, read what are monster arcade games, then how monster arcade games work.
If you already play and want to improve, the highest-value articles are improving your scores, how combo systems work and recognising boss attack patterns — those three cover the habits behind most avoidable losses.