Sanctum 2: The Historical Geekenstein Review

Preservation edition · October 3, 2026 · Geekenstein Editorial

Historical source: Dustin Triplett, publication date unverified. This edition contains a newly written, condensed account of the original coverage, with historical opinions attributed to their author. It is not the original article or a new firsthand review.

A sequel assessed on PC

Triplett’s review concerned Coffee Stain Studios’ Sanctum 2 on PC, with console editions mentioned in the product panel. He considered it a substantial improvement on the first game’s content and presentation. The exact article publication date remains unverified. This is a synopsis of that historical assessment, not a current patch review or a new playtest.

Building and fighting served the same objective

The review explained the central loop around protecting the Core. Players placed barriers to shape enemy movement and towers to damage or delay attackers, then joined the action with their own weapons. Triplett’s praise centered on that interaction: planning defenses did not end the player’s involvement once a wave began. Shooting and positioning could still change the outcome.

Classes and cooperation

The reviewer described four characters with distinct primary-weapon roles, including assault, explosive, sniper and close-range approaches. Secondary weapons offered some flexibility, but the fixed main roles could feel limiting in solo play. He thought the arrangement made more sense with a coordinated group. Enemy attention and the possibility of player death made positioning and teamwork consequential rather than cosmetic.

Perks and the principal irritation

Unlockable perks were Triplett’s favorite addition. He described options affecting movement, weak-point damage and even the Core’s response to attackers, and valued how combinations changed a team’s approach. By contrast, collecting building resources from crates near the Core frustrated him when timed waves reduced preparation time. These are observations about the version he reviewed; later balance or resource-system changes should be checked separately.

The recommendation’s limits

His verdict favored the game for players drawn to both tower defense and first-person action, particularly cooperative groups. He acknowledged demanding difficulty and the genre’s narrower audience. The original Flash-era video notice, obsolete currency pricing and author biography are omitted. No new compatibility guarantee, present multiplayer-population claim or numerical rating is inferred from the surviving record.

A cooperative game and an individual collection

Editorial follow-up · Geekenstein Editorial · October 6, 2026

The historical review focuses on defending the Core together. The current Sanctum 2 Steam listing also lists Steam Trading Cards. A team’s success in a match and the items in one player’s Steam inventory are separate records; cooperating does not establish who owns a particular card.

Use KLXCards’ Steam card and badge collecting guide when you want to investigate the collection alongside the game. Start with the base game, Steam app 210770, rather than treating its expansions and soundtrack as interchangeable collection identities.

  1. Write down the exact game title and app ID before matching an inventory item.
  2. Check your own badge page for collected and missing cards. Keep that list separate from your team’s builds and unlocks.
  3. Choose an endpoint: document what you have, explore the artwork, or investigate a badge. You can stop without purchasing anything.

The official Steam Trading Cards FAQ explains drops and crafting. The current feature label does not promise a full set from finishing a campaign.

Preservation source and omissions

The historical article container was recovered from a Common Crawl capture dated 2013-12-06. The full original prose, author biography, advertisements and third-party media are not republished. Archive availability alone does not grant reuse rights. The original publication date is shown only where verified.

Common Crawl source file (compressed archive record; capture timestamp 20131206061427).

Browse Geekenstein · About this edition and corrections