The license to distribute Star Trek: Resurgence has officially expired, and with it goes another chunk of gaming's already fragile digital preservation record. Publisher Bruner House posted the terse notice on the game's Steam page: the Paramount deal ran its course after roughly three years, so the Telltale-style narrative adventure is being pulled from Steam, Epic, PlayStation Store, and everywhere else it lingered. Existing owners keep their copies and can redownload at will, which is the standard corporate fig leaf in these situations. The game, built by Dramatic Labs—a studio packed with ex-Telltale talent—is already gone from the Xbox store and the main Steam storefront itself now shows only a delisting notice.

This one stings for the preservation crowd because Resurgence wasn't some forgotten shovelware. It earned Very Positive reviews on Steam with an 89% score across more than 3,000 ratings, peaked at around 660 concurrent players, and carved out a respectable niche as a character-driven Star Trek story featuring the likes of a legacy Riker and an elderly Spock. Yet a three-year license window was apparently all Paramount was willing to grant before the rights math no longer worked. Community forums on Reddit and ResetEra are already filling with the familiar mix of last-minute panic buys and resigned complaints about how quickly licensed Trek projects vanish while decades-old titles somehow linger. One recurring theory on r/TwoBestFriendsPlay points to Paramount jacking up renewal fees to levels a modest narrative game simply can't justify.

The receipts paint a familiar industry pattern: ambitious ex-Telltale devs get a shot at a beloved IP, deliver something players actually liked, then watch the corporate overlords pull the plug once the initial window closes. Dramatic Labs and Bruner House have not elaborated beyond the LLAP sign-off, but the silence speaks volumes about how licensing agreements treat games as temporary rentals rather than enduring cultural artifacts. For a medium already hemorrhaging access to its own history, this is less a surprise than another quiet data point in the case file against unchecked publisher control.