The Ultimate Guide to Sword Arcade Games
What sword arcade games are, how their systems fit together, and the order they are worth learning in.
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.
What sword arcade games are, how their systems fit together, and the order they are worth learning in.
Editor's picks across all six categories, with an honest account of what each one is actually good at.
What is happening under the hood: the loop, the collision test, the timing windows and the numbers behind them.
Two genres that share a weapon and almost nothing else, and how to tell which one you are playing.
The five things worth knowing before your first run, and the fastest path from confused to competent.
What reaction time actually is, what can and cannot be trained, and what to do instead when you hit the floor.
Every mechanic in the combat system, what it costs, what it beats, and when it is the wrong choice.
Why the multiplier is worth more than any single hit, and how to play around a number that resets.
How to beat an opponent who fights back: baiting, spacing, punishing and knowing when to do nothing.
How to fight a crowd: kiting, target priority, corner discipline and why standing still always loses.
How timing windows are shaped, why early and late score the same, and how to correct a bias deliberately.
Which input suits which game, why some schemes feel wrong, and how to set yourself up properly.
Which games work on a phone, which need two thumbs, and how touch controls are designed here.
What actually gets harder, why curves flatten at the top, and how to tell a fair ramp from a broken one.
The three answers, the colour rule, and why reading ahead beats reacting faster.
How defending an objective changes every instinct you built fighting for yourself.
What changes when a sword game has a place to explore, resources to spend and things that cannot be fought.
The design problems behind a combat system that stays fair, and how each one was solved here.
Where the points actually are, which risks pay, and how to stop optimising for survival.
How sword combat in games moved from a single attack button to three-phase timing, and what browsers changed.
Ad space reserved. See README.md to connect an ad unit.
8 guides
The window, the timing, the tells to watch, and how to practise a parry until it stops being luck.
What a guard covers, what it costs, and the three situations where blocking is the wrong answer.
The idea underneath every punish in every game here, explained without the frame-data jargon.
The exact timing arithmetic behind the most common losing habit in every duel on this site.
What everything costs, how the bar refills, and the one rule that prevents most stamina deaths.
The visual language every enemy attack uses, and how to read shape, colour and growth at a glance.
Why some attacks ignore your guard entirely, how to spot them, and what to do instead.
Two effects with no mechanical consequence that decide whether a hit feels like anything.
12 guides
Why dodging late beats dodging early, which direction to go, and what a dodge costs.
What i-frames are, where they come from, and the two kinds you get in these games.
Three answers to an enemy that bounces light attacks off its front, and when each one applies.
Why duel technique fails in a crowd, and the four things that replace it.
The geometry of getting cornered, why it happens gradually, and the habit that prevents it.
The single most important movement pattern in survival games, explained step by step.
All seven enemy archetypes, what each one is for, and the specific answer to each.
Every source of points in the library, and which ones players routinely overlook.
What makes a risk interesting rather than obvious, and the five loops used across this library.
Why a good power-up costs something, and the four used across this library.
The specific advantage independent aim gives, and why it matters more than it looks.
The properties that make someone press retry, and the ones that make them close the tab.
7 guides
Two invisible mechanics that make jumping feel fair, and what happens without them.
What speeds up, what does not, and the floor that keeps an endless game possible.
Where to look, how far ahead to plan, and why watching your character is the main thing holding you back.
The three obstacles, how to identify each at speed, and the one that catches everyone.
The numbers behind a jump that feels right, and why gravity is usually far stronger than reality.
Why you can jump up through a ledge but land on it, and what breaks without that rule.
Route planning under a rising threat, and why climbing early buys the room to be careful later.
4 guides
What changes when the fail state moves off your own health, and the habits that have to change with it.
A concrete method for deciding which of several threats to answer first.
The tightest timing window in the library, what it is worth, and how to practise it.
A short guide about the single most costly targeting habit in arcade games.
8 guides
Why bosses take reduced damage, how phases work, and what makes a boss fair rather than merely hard.
A method for turning an unreadable boss into a solved one in about three attempts.
Health as currency, why it does not refill, and the arithmetic that decides a dungeon run.
A decision procedure for the games where combat is optional, and why it feels wrong.
Why a torch turns navigation into memory, and how to build a map you can actually use.
How a maze is carved so that it is always solvable, and why that guarantee matters.
Why a game that makes you carry your points somewhere is more interesting than one that does not.
Why every enemy here is a different outline, and what happens to a game when they are not.
11 guides
The two completely different ways a hit can be perfect, and why the distinction matters.
The arithmetic that makes a run of good hits worth more than a run of great ones and mistakes.
What a millisecond figure in a browser game actually represents, and what limits its accuracy.
Two mechanisms that feel identical, train completely differently, and have very different ceilings.
A structured routine that produces measurable improvement, and the mistakes that waste practice.
What makes a touch layout work, why five buttons is the ceiling, and the gesture that does two jobs.
Which games work with a single thumb or a single hand, and what you give up.
Why certain keys are chosen for certain actions, and the constraints a browser adds.
What canvas is, how a browser game draws sixty frames a second, and why it works on any device.
Where your records actually live, what that means for privacy, and why they do not follow you.
What an action game owes its players, what is genuinely hard, and what this site does about both.