How we review
How We Review Tower Defense Games
Our review criteria, scoring bands, sourcing rules, AI disclosure and corrections policy for every tower defense review on Tower Defense Games.
This page explains how a game gets a score on this site, what we count as evidence, and what we refuse to do. It exists so you can judge the review rather than trust the byline.
Who writes the reviews
The reviews are written by Vesperwatch Editorial, the team that builds Vesperwatch, a free browser tower defense game. We are not a general games outlet. We are people who spend our working hours on wave pacing, tower economies, pathing and upgrade commitment, and that perspective shapes what we notice.
It also creates a conflict of interest: we review games that compete with ours. We handle that with disclosure, not with a claim of neutrality. Every review says we make Vesperwatch, every review links to this page, and no game can pay for a score, a placement or a rewritten verdict.
What we assess
Each review uses the same five categories. The weights are fixed so that a charming art style cannot quietly overpower a broken economy.
| Category | Weight | What it covers |
|---|---|---|
| Core loop and tactical depth | 25% | Does the moment-to-moment defense hold up? Are there real decisions about placement, targeting, economy and upgrade commitment, or one dominant build? |
| Onboarding and interface clarity | 20% | Can a new player understand the first hour without a wiki? Are enemy types, damage rules and upgrade paths legible in the UI? |
| Content, progression and replayability | 20% | Map count, mode variety, meta-progression, difficulty ladder and whether the game gives you a reason to return after the campaign. |
| Value and monetization | 20% | Price against content, DLC structure, in-app purchases, and whether the store interferes with the defense. |
| Performance, platform fit and stability | 15% | Frame rate, load times, controls, mobile/desktop differences and the stability issues players actually report. |
A review does not have to mention every category by name. The weights explain how the final number was reached, not how the prose must be structured.
What the score means
Scores are editorial judgments on a 0–10 scale, not averages of Steam percentages or Metacritic. They answer one question: how strongly would we recommend this game to the player described in the "best for" line?
| Score | Band | What it means |
|---|---|---|
| 9.0–10 | Essential | A defining game in the genre. Recommend it even with the caveats. |
| 8.0–8.9 | Excellent | A strong buy for the right player. Flaws are real but do not break the core. |
| 7.0–7.9 | Good, with caveats | Worth playing if the premise appeals. Check the "skip if" line first. |
| 6.0–6.9 | Flawed | Interesting ideas, but the problems affect the core loop or the value. |
| Below 6.0 | Not recommended | We would not spend money or an evening on it in its current state. |
We update a score only when a patch or platform change materially alters the assessment. A price cut alone does not move the score; it may move the verdict.
What counts as evidence
We prefer primary sources and work down this list:
- Official store pages for price, platforms, release date, developer and supported modes.
- Official patch notes, developer posts and documentation for current systems and balance changes.
- In-game systems and tooltips, where they are documented by the developer.
- Community wikis and guides for detailed mechanics that official sources do not publish. We cross-check at least two.
- Recent player reviews for sentiment and recurring complaints. We treat these as a sample, not a census.
Every review lists at least five sources and shows the date the facts were checked. When a number is likely to change — price, map count, player counts — we either date it or phrase it as a range.
What we do not do
- We do not invent playtime, screenshots, quotes, interviews or "our test rig" results.
- We do not copy store copy or another outlet's prose.
- We do not use copyrighted game art, logos or screenshots. The visuals on this site are original CSS and SVG.
- We do not accept payment, sponsorship or affiliate commission for a review.
- We do not promise rankings or traffic to anyone.
- We do not present a model's confidence as evidence.
AI disclosure
We use AI-assisted drafting and research tools to help structure and edit articles. Publication still requires a source check: every factual claim with a number, price or platform must be traceable to the sources on the page, and claims we cannot support are removed or rewritten. We do not publish raw model output, and we do not use AI to fake a playthrough, a person or a quote.
If you find a claim that does not match its source, treat it as an error, not as a style choice. Tell us and we will correct it.
Corrections and updates
We re-check price, platform and patch status when a review is materially affected by a new release, a major patch or a store change. The "Updated" date on the page is the date of the last fact check, not the date of a cosmetic edit.
To report an error, open an issue on GitHub. Include the page URL, the sentence, and the source that contradicts it. We will correct the page and note the change in the page history.
Ownership disclosure
Tower Defense Games is the home of Vesperwatch, a free browser tower defense game. We review competing games. We link to Vesperwatch only where it is relevant to the decision, and we say clearly that it is our game.
If that conflict is a dealbreaker for you, use the reviews for their sources and criteria, and check the games on their official store pages before buying. That is a reasonable way to read any review.
Contact
- Corrections and source disputes: GitHub issues
- The game: Play Vesperwatch
- About the team: About Vesperwatch Editorial