The answer before the background

Our recommendation

Use this Tower Tactics Liberation SteamDB, wiki and Reddit guide as a source ladder, not as three interchangeable authorities. Steam app 1709900 and official update posts own product identity, platforms, release dates, DLC and current changes. SteamDB preserves useful build and patch history but is community-operated. The Fandom wiki, Steam guides, Steam discussions and Reddit can explain cards or player experiences, yet every claim needs a patch, DLC, mode and date before it becomes reliable database content.

Send each question to the source that can answer it

QuestionBest starting sourceRequired qualifier
Official platform, developer or release dateSteam store app 1709900Country store and review date.
Current balance or fixOfficial Steam newsExact version and DLC tag.
Historical build or old patchSteamDB patch historyCommunity mirror; link back to the original update when available.
Card or trinket catalogLive client, then community wikiPatch, base/DLC pool and exact tooltip.
Strategy or save problemSteam guides and discussionsAuthor date, version, mode, reproduction steps and developer reply if present.
Broad opinionSteam reviews or RedditPlaytime, post date and product version; never treat one comment as a fact table.

Store facts so later patches can update one field instead of rewriting a page

  • Product row: app ID, exact title, developer, publisher, release date, supported OS and official URL.
  • Version row: patch number, date, base game or DLC, changed objects and original announcement URL.
  • Card row: exact name, type, mana, levels, effect text, deck or pool, reviewed version and screenshot reference.
  • Trinket row: rarity, effect, acquisition context, stacking rule, DLC and version.
  • Mechanic row: name, mode, trigger, threshold, output, exceptions and last verified build.
  • Strategy row: deck, Ascension, offerings, DLC, route, result and number of comparable attempts.

Keep an old answer dated instead of silently merging it with the current game

Victory Lap illustrates why source dates matter. An early-access update described it as beta and explained the post-boss loop. That record is useful history, but it does not prove every current modifier. Likewise, an older Overload threshold or card value cannot overwrite the live 1.18.5 tooltip simply because it appears in a search snippet.

The franchise also creates entity conflicts. The Liberation news feed contains announcements for Tower Tactics 2 and Tower Tactics Arena. Workshop, map-editor, controller and Steam Deck statements from the sequel remain sequel facts. A database should store product app IDs before importing any feature from a shared news feed.

When a community answer and current client disagree, retain both with dates, then prefer the current first-party client or developer correction. Do not average two values or remove the disagreement from the record.

Community value

Community sources are useful for discovery, reproducible strategies and locating old behavior. Their role label tells readers what still needs first-party or live-client verification.

Common questions

Is SteamDB official?

No. It is a valuable community-operated database, while Steam's store and developer posts are the first-party product sources.

Is there an official Tower Tactics: Liberation wiki?

The accessible Fandom wiki is community-maintained. Use it as a discovery index and verify current values in the client or official updates.

Should I trust a Reddit build?

Treat it as a player report. Check its date, deck, Ascension, DLC, patch and reproducible result before applying it.

Where are the official patch notes?

Use the Tower Tactics: Liberation Steam news and update history for app 1709900.

Why do some Liberation pages mention Tower Tactics 2?

The shared developer news feed promotes the sequel. Store the product identity first so sequel features are not imported into Liberation.

What we checked

Official listings establish current availability and product facts. Community pages are used for mechanics and build history, then labeled separately.