Lampwall is the reason this publication exists. It is a well-made tower defence game with clever maps, a genuinely interesting resource conflict between light and range, and an art style that survives being looked at for thirty hours. It is also, measured against every other game in this file, the single worst thing you could load at half past eleven.
None of that is a matter of length. Plenty of long games sit comfortably in the clean column, because length and stoppability are unrelated properties. Lampwall is hostile because of three specific decisions, each of which is defensible in isolation and which together make leaving feel like a loss.
The first decision: no save inside a map
A map is forty waves. Forty waves takes between one hour and fifty minutes and two and a half hours depending on layout. There is no save point inside a map — quitting returns you to the map select screen, and the map begins again at wave one.
Our shortest completed session across twenty-one evenings was one hour and thirty-four minutes. Our shortest attempted session was eleven minutes, and it produced nothing at all. Twice we lost more than an hour of play because a real-world interruption arrived at wave thirty.
The second decision: the streak
Consecutive completed maps build a multiplier that raises the reward on each subsequent map, and the multiplier resets when you leave the session — not when you fail, when you leave. Failing a map preserves the streak. Quitting to the desktop does not.
This inverts the natural incentive in the most direct way available. On four evenings we started a map we did not have time for, knowing that we would probably fail it, purely because failing preserved something that stopping would destroy. That is a mechanic actively working against the player's evening.
The third decision: the timer that does not pause
Between waves there is a preparation phase of forty-five seconds in which you place and upgrade towers. Opening the pause menu during that phase does not stop the countdown. The wave arrives whether or not you were looking at the screen.
The effect is that the only genuinely safe moment to walk away is during a wave, when you are least able to judge how the map is going. There is no interval in this game in which a person can stand up without cost, which is the definition we use for hostile.
| Measurement | Figure | Note |
|---|---|---|
| Honest session length | 1h 47m | Median across 21 evenings; longest in the file |
| Intended vs actual | +52 min | Largest overrun recorded here |
| Save granularity | Per map | Nothing inside a map is preserved |
| Safe exit points | 1 per 1h47 | Only between maps |
| Pause reliability | Partial | Preparation timer continues while paused |
| Stop quality | Hostile | Leaving costs the map and the streak |
The game underneath
It deserves saying clearly that this is not a bad game. The central conflict — towers need light to see, light attracts a different class of enemy — produces map layouts that genuinely require thought, and the difficulty curve across the campaign is well judged.
Twenty-nine hours in, the maps were still teaching us things. On a Saturday afternoon with nothing else planned it is one of the better tower defence games of the year, and if you play in long deliberate blocks the entire complaint above simply does not apply to you.
A game can be good and still be the wrong game for eleven at night. Those are separate judgements, and this site exists because almost nobody publishes the second one.
What would fix it
A save between waves would resolve nearly everything, and there is no evident technical reason it could not exist — the game already serialises the full board state between maps. Failing that, pausing the preparation timer would at least create a safe interval every ninety seconds.
The streak is the harder problem, because it is doing real design work in encouraging longer sessions. Tying it to completed maps regardless of session boundaries would preserve the intent without punishing anybody for going to bed.
Verdict
Recommended without hesitation for weekend afternoons and withheld absolutely from the last hour of a working day. The score reflects the game; the grade beside it reflects the exit, and no amount of quality in the former compensates for the latter at midnight.
Score
6.8/10
Sharp maps and a genuinely interesting central conflict, wrapped in the most hostile exit measured here: no mid-map save, a streak that punishes quitting, and a timer that ignores the pause menu.