
First Minute: Where Do I Even Tap? I opened Endlessseige on my phone expecting the usual tower-defense clutter — a cramped grid, tiny icons, some wave counter I'd squint at. Instead the screen stayed mostly empty for a f
First Minute: Where Do I Even Tap?
I opened Endlessseige on my phone expecting the usual tower-defense clutter — a cramped grid, tiny icons, some wave counter I'd squint at. Instead the screen stayed mostly empty for a few seconds, just a winding dirt path and a single glowing build spot. That emptiness is the first hint: this game isn't going to hold your hand. I tapped the spot, dragged a basic archer tower onto it, and watched a lone skeleton shamble down the path. The archer plinked it in three shots. Gold popped up. No tutorial pop-up, no arrow pointing at the next button. Just the quiet implication: you figure it out.
If you're on desktop, the first thing you'll do is click. On mobile, you'll tap. Both work, but the feel is wildly different. On a phone, your finger covers the tile you're trying to select, which leads to misplacements in the first couple of waves. On a keyboard, the mouse gives you precision, but the hotkeys aren't labeled — I'll get to that. The first minute is about making one or two quick placements and then realizing the enemies don't stop coming while you're thinking. There's no pause between waves, no "ready" button. The siege is, as the name says, endless.
The Loop: It's Not About Surviving One Wave
Endlessseige doesn't have discrete rounds. Enemies spawn continuously, with the composition shifting over time. Early on it's slow skeletons, then faster ghouls, then shielded knights who shrug off arrow fire. You're not optimizing for a wave 10 boss. You're optimizing for a death spiral that happens somewhere between minute six and minute twelve, depending on how clean your early decisions are.
Gold ticks in from kills. You spend it on new towers or upgrading existing ones. Upgrades increase damage, range, or attack speed depending on the tower type, and the cost curve is steep — a tier-three mage tower costs more than three tier-ones, and you'll feel that math in your gut when a fast-moving wolf pack slips through because you over-invested in one corner. The loop is: place to cover a choke, upgrade just enough to hold that choke, then expand to cover the next leak point before the enemy mix changes. The game punishes both turtling and overexpansion. Find the middle or restart.
There's no explicit health bar for your base, but enemies that reach the end of the path subtract from a life counter. You start with twenty lives. Lose them all and the run ends. You don't regenerate lives between anything. That number sits in the top-left corner, and by the time you notice it ticking down fast, you're usually already dead.
What You're Actually Optimizing
The hidden stat is coverage overlap. Every tower has a circular range indicator that appears when you select it. The game wants you to overlap those circles so that fast enemies get hit by at least two towers simultaneously. Single-tower coverage works for the first three minutes, then falls apart when ghouls start sprinting through. I lost three runs before I realized my archers on straightaways were letting single targets slip because their projectile speed wasn't high enough to catch a moving enemy without help.
Second hidden stat: path length. The map has a fixed winding path, but you can force enemies to walk farther by placing cheap "block" towers — walls essentially — that don't attack but redirect movement around them. The game never tells you this. I discovered it by accident when I placed a tower slightly off-grid and noticed a skeleton detour around it. Suddenly the whole strategy opened up. You're not just placing damage dealers; you're sculpting the path to keep enemies under fire longer. A well-placed block tower that adds three seconds of walk time is worth more than a damage upgrade that costs twice as much.
Mistakes That End Runs Early
Here's what killed my first half-dozen attempts, in order.
Over-upgrading the first tower. That archer you placed at the entrance feels strong at level three. It solos the first two minutes. Then shielded knights appear with physical resistance, and your super-archer plinks them for one damage while three of them march past. You've sunk 200 gold into a tower that's now useless against the current enemy type. Spread upgrades across at least two damage types — physical and magic — before you push any single tower past level two.
Ignoring the backline. The natural instinct is to build at the entrance and layer defenses forward. But fast enemies and flying units (bats show up around minute five) ignore your frontline entirely if you haven't placed anti-air near the exit. I lost a run with fifteen lives remaining because three bats flew over every tower and drained me in ten seconds. Place one archer or mage near the final stretch by minute four, even if it feels wasteful. It's insurance.
Selling towers reflexively. You can sell towers for a partial refund. I started doing this to "fix" bad placements, but the refund rate is something like 60% — you're bleeding gold every time. Better to leave a suboptimal tower and build around it than to sell and create a temporary gap. The only time selling makes sense is when a tower's damage type is completely negated by the current wave and you have zero gold for a new one. Even then, consider whether that tower is at least blocking pathing.
Not watching enemy types. The spawn mix changes gradually, not in announced waves. You have to glance at what's actually walking down the path. Shields mean physical resist. Robes mean magic resist. Fast-moving small enemies mean your slow-attacking cannons will overkill one target while three others sprint past. If you don't look at the enemies themselves and only watch your gold count, you'll build the wrong counter.
Building too far from the path. Range circles that barely clip the road are a trap. Enemies move at different speeds, and a tower that can technically reach the path might only get one shot off on a fast ghoul. Place towers so the path runs through the inner half of their range circle, not the outer edge.
Touch vs Keyboard vs Fullscreen: What Actually Matters
I played on both phone and desktop. The game supports touch, mouse, and keyboard, but the experience isn't symmetrical.
On mobile (touch): Tapping to select a tower works fine, but dragging to place a new one is where it gets messy. Your finger obscures the tile grid, and I misclicked placements maybe one in five times during tense moments. The workaround is to zoom in — pinch-to-zoom exists, though the game never mentions it. Zoom in until the build spots are finger-sized, then place. The downside: zooming in means you lose peripheral vision of the path, so you might miss a leak. I developed a rhythm: zoom out to scan, zoom in to build, zoom out again. It's not elegant but it works.
A mobile-specific annoyance: the sell button is tiny and sits right next to the upgrade button. I accidentally sold a level-three mage tower once while trying to upgrade it mid-wave. That ended the run. On a smaller screen, use the pad of your finger deliberately, not the tip, when navigating the tower menu.
On desktop (mouse + keyboard): Mouse placement is precise. Click to select a build spot, click the tower type, done. Keyboard shortcuts exist but aren't documented in-game. From trial and error: number keys 1–4 select tower types, U upgrades the selected tower, S sells it, and spacebar toggles speed — yes, there's a fast-forward, and it's essential for the slow early minutes. Press space once and the game runs at roughly 1.5x speed. Press it again to go back to normal. I use fast-forward for the first three minutes of every run, then drop to normal speed once the enemy mix gets complicated.
Fullscreen: The fullscreen button is in the bottom-right corner of the browser window. On desktop, fullscreen helps immensely because it removes browser tabs and bookmarks from your peripheral vision, which matters when you're tracking small fast enemies near the screen edge. On mobile, fullscreen hides the browser address bar and gives you maybe 15% more vertical space. That extra sliver is the difference between seeing the path exit and having it hidden behind your phone's nav bar. Always go fullscreen on mobile before you start a serious run.
One weird quirk: exiting fullscreen mid-run on desktop sometimes causes the game to stutter for a half-second. If you're in a late run with enemies near the exit, that stutter can cost a life. Toggle fullscreen only between runs or in the first slow minute.
A Short Practice Plan
If you're losing runs around the six-minute mark, here's a concrete sequence I used to push past that wall. It's not a guaranteed win — the game gets harder indefinitely — but it'll build the habits that extend runs.
Run 1: No upgrades. Play a full run where you never upgrade a tower. Only place new ones. The goal is to learn coverage and path-blocking without the crutch of over-leveled single towers. You'll die early, probably around minute four. Pay attention to where the leak happens — that exact tile is where your next run's first block tower should go.
Run 2: Two damage types only. Place one physical tower (archer or cannon) and one magic tower (mage) before minute three. Upgrade neither past level two. Focus entirely on overlapping their fields of fire. The goal is to see how long balanced coverage holds without heavy investment. You'll learn the timing of the enemy-type shifts by watching when each tower starts underperforming.
Run 3: Path sculpting focus. Spend your first 100 gold on a block tower placed to extend the walking path, not on damage. Place it so enemies have to walk around it, then put an archer so it fires along the new longer route. This run teaches you that gold spent on path manipulation is gold saved on upgrades. You may die early while figuring out placement — that's fine. Restart and adjust the block position by one tile. Small changes matter.
Run 4: Full attempt with everything. Now combine: fast-forward the first three minutes, place block towers to lengthen the path, build one physical and one magic tower before minute three, add anti-air near the exit by minute four, and only upgrade when a specific tower is clearly falling behind. You should see your runs push past eight, maybe ten minutes.
This practice sequence takes under an hour total and forces you to engage with systems the game never explains. It's more effective than bashing your head against full runs hoping to out-click the difficulty curve.
What I Wish I'd Known Two Hours Ago
Some small things that don't fit neatly above but matter in the moment.
Flying enemies have a distinct shadow that moves along the ground before the sprite appears on screen. You can spot incoming bats by watching the path shadows, not the sky. This gives you an extra two seconds to sell or place an anti-air tower if you're quick.
The game auto-saves your run if you close the browser tab, but only at the start of each "wave" — which, since there are no discrete waves, seems to mean every minute or so. If you close mid-minute, you might lose progress. I wouldn't rely on this for anything important.
Sound cues exist. Enemy deaths make different sounds based on type — skeletons clatter, ghouls squelch, bats screech. With practice you can identify what's dying off-screen without looking. It's not essential but it helps in the chaotic later minutes when you're focused on building and can't scan the whole path.
Endlessseige runs in any modern browser without downloads or accounts. It's free, it loads in a few seconds, and it doesn't pester you with ads between runs. The only interruption is your own restart button when a run collapses. That restraint is rare and worth appreciating in a sea of ad-stuffed tower defense games.
The game doesn't have a formal tutorial, story, or even a title screen with lore. From what I can tell, it's a pure mechanics exercise: place towers, manage gold, survive as long as possible. That minimalism is the point. Everything you learn comes from failing, squinting at the screen, and trying one slightly different placement next time. It's frustrating in the way good arcade games are frustrating — you always know why you died, even if you couldn't stop it in time.