What Are Fantasy Arcade Games?
A definition that actually distinguishes them from fantasy RPGs and from generic arcade games, and what the combination changes about how they play.
How the mechanics actually work - attacks, guards, timing, scoring - and how to play each category well. Every guide is written after playing the games it covers.
The systems that transfer between every game in the library.
A definition that actually distinguishes them from fantasy RPGs and from generic arcade games, and what the combination changes about how they play.
The four systems underneath every game in the library - the loop, three-phase actions, quality scoring and difficulty curves - and what each one means for how you should play.
An honest starting order through the library: which game to play first for each kind of player, what each one teaches, and where to go next.
Why good platformers feel fair and bad ones feel broken: coyote time, input buffering, reachability, momentum, and how to read a platform before you commit.
The leave-or-stay decision that defines the category, how perfect mazes work, why patrols are better than chasers, and how to plan a route under a clock.
Why a spell is interesting only when it costs something: cast times, mana economies, the four elements, and the difference between a resource and a cooldown.
Positioning beats attack speed: why arenas are round, what each creature in the bestiary asks of you, and how wave composition is built so a crowd is solvable.
Fixed treasure values, nine spawn patterns, chains on timers versus chains on counters, and why the greedy route usually beats the efficient one.
Reaction and anticipation are different skills with different ceilings. How timing is graded, why consistency beats brilliance, and why the runs are deliberately short.
Five dragon games that use the creature for something mechanical rather than decorative - as a vehicle, a hazard, a schedule and a hoard worth robbing.
Six wizard games and the resource each one is really about: mana, Focus, mana-for-blinks, a recipe, a single button, and gravity itself.
Seven knight games across five categories, and what a knight is mechanically: the character who can take a hit, which changes what the game can ask of you.
Counters, timers and quality gates: the three ways a combo can be built, what each one does to a player's behaviour, and how to protect a multiplier.
Why the curve is eased rather than linear, why every fourth wave is easier on purpose, and the difference between adding threats and removing reaction time.
A boss is a schedule, not a health bar. Telegraph floors, recovery windows, attack rotation, and why the best boss on this site cannot be killed at all.
How an endless game stays interesting past two minutes: procedural generation with guarantees, realm rotation, and why a plateau is better than an endless ramp.
What a single button can and cannot express, why setting a value beats adding to one, and how a one-input game finds a skill ceiling.
A practical method: diagnose which skill is failing, practise it in the game that isolates it, and stop making the four mistakes that cost the most.
What separates a level from a list of obstacles: teaching without a tutorial, rhythm, readable risk, and the difference between designed and generated space.
What actually changes on a phone: contact points, occlusion, session length - and the four control schemes that survive the move from keyboard to thumb.
Ad space reserved. See README.md to connect an ad unit.
7 guides
Jump timing is a release problem more than a press problem. How to find the right moment, and why most missed jumps are held too long rather than started too late.
Every surface in the library states what it is before you touch it. The full vocabulary, and the habit of looking one platform further than you are aiming.
Acceleration and friction are what make a platformer feel like anything at all. What momentum buys, what it costs, and how to use it deliberately.
Why vertical games need a one-way camera, a wrapping screen and a pressure source - and how to climb well when you cannot see what is above you.
Why tile collision must resolve vertically before horizontally, how one-way platforms are implemented, and what both mean for how you move through a tile level.
How a continuous height field differs from platforms, why landing angle decides your speed, and how to read a slope before you reach it.
Which keys do what, what the touch controls map to, and the four habits that make a first platformer session go substantially better.
8 guides
A four-step method for reading a space, pricing the expensive item, planning a loop instead of a fan, and setting a leaving point before you need one.
What a perfect maze guarantees, why junction memory beats corridor memory, and the three rules that turn a confusing maze into a solvable one.
What makes a space read as a dungeon rather than a cave: brickwork, torches, confinement, and the mechanics that only work underground.
Battlements, gates, portcullises and towers - what each castle feature does mechanically, and why the setting suits defence and climbing so well.
Patrols are timing puzzles with the answer drawn on the floor. How to find a window, why waiting beats outrunning, and when a patrol is actually a chase.
Why swimming controls feel wrong at first, how to steer something that never stops, and the dive-and-return rhythm that makes air management work.
Light as vision, light as safety and light as a clock - three different mechanics that look the same, and how each changes what a player does.
The arithmetic behind the leaving decision: what an exit bonus is actually worth, why banking compounds, and how to set a rule you will actually follow.
8 guides
Regeneration rate against cast cost is the whole economy. How to read a mana bar you have never seen, and why a full bar at the end of a run is a mistake.
A cast is something you do to yourself. Why the vulnerable window is the mechanic, how to choose the moment, and what a long cast is actually buying.
Four colours with fixed meanings, and the two games that turn them into a puzzle. Why matching games are really about restraint rather than recognition.
A slow-time effect buys reaction time you did not have. When to spend it, why hoarding it loses, and the difference between slowing the world and speeding yourself.
One button that changes which way down is. Why the travel time is the difficulty, how pinches differ from blockers, and why reacting stops working at twenty hazards.
Games where the only variable is when. Why symmetric grading is fairer than a bullseye, what the quality number means, and how to practise a window you cannot see.
Games where order matters. Why a visible answer makes a better game than a hidden one, how completion bonuses should scale, and the cost of restarting.
Ten effects that behave identically wherever they appear. What each one is worth, why duration should be visible, and the case for taking a power-up you do not need.
9 guides
In a circular arena you start every wave surrounded. Why backing away loses, how the spawn stagger gives you an order to work in, and when to accept a hit.
A block that always works is not a decision. How Sword Quest's guard turns blocking into timing, what the 0.18-second parry window pays, and why holding guard loses.
A meter that stops you attacking is a pacing device, not a punishment. How to read a stamina bar, why the empty state is worse than it looks, and the two-thirds rule.
Waves grow by count and by roster. Which creature unlocks on which wave, the cap on ranged enemies, why every wave opens with a goblin, and how to read one as it enters.
Six creatures, each asking a different question. Why a small original bestiary beats a large borrowed one, and what each species is actually testing.
When you are defending an object rather than yourself, the calculation inverts. Why leakage is the real currency, and how to decide what to let through.
Four moves with four different prices. What reach and arc actually buy, why the active window is a tenth of a second, and how the combo multiplier really works.
Monster Escape gives you a dash and three runes and nothing else. Why going through a crowd beats looking for a gap, and why no chamber can be cleared.
A boss is a schedule, not an opponent. The four attacks, what the recovery window is for, and why banking treasure is what makes the fight harder.
9 guides
Nine item types with fixed values site-wide. What each is worth, why the expensive ones cannot be magnetised, and how to price a detour.
Nine shapes, each of which means something. Why a pattern is a tested route rather than decoration, and how to read a level from its collectibles alone.
The multiplier is the difference between a good score and a large one. How the steps work, which games decay, and why risk tolerance should fall as it rises.
A magnet changes what a route is worth. Why the valuable items resist it, what 190 pixels of pull actually buys, and when a vacuum is worth more than eight seconds of magnet.
Five lanes, a tenth of a second to change, and no steering skill to hide behind. Why the greedy line loses, and how to read a gold lane that ends badly.
Three carry slots, four belts and two chutes. Why a catcher becomes a logistics problem the moment items have destinations, and how cursed relics apply pressure.
When everything costs the same currency, every decision becomes comparable. Why a clock is a better punishment than a life, and how the vault gets richer each time you leave.
Four colours, a 3x chain and a bloom that makes ignored colours valuable. Why the shortest route is usually the worst one, and how to plan a glade.
A coin is ten points in every game on this site. What that consistency buys, what it costs, and why a game that rescaled its own treasure would be worse.
9 guides
You mostly cannot, and you do not need to. Why anticipation beats reaction by 200 milliseconds, and what to practise instead.
From coin-op cabinets to a canvas element. What each era kept, what the browser changed, and why the short-session arcade form survived everything.
One button, one window, and everything else stripped away. How the orbit gets harder without the window shrinking, and why a reversing rune is the real test.
Some games pay you for nearly being hit. Why that fixes the safest-line problem, how centring is measured, and when a close call is worth the risk.
Momentum means the decision happened earlier than the obstacle. How to aim at where a gap will be, and why correcting late makes things worse.
A three-minute run and an instant restart are design decisions, not limitations. Why cheap failure is what makes a hard game learnable.
Your scores live in your browser and nowhere else. What is stored, what happens in private browsing, and why there is no global leaderboard.
What a canvas game actually is, why these ones have no images or audio files, and what that buys in load time and consistency.
What these games do for players who cannot use a mouse, cannot hear the cues, or need motion reduced - and what they honestly do not do.