Valve's New Steam Achievement Sets and Linux Client Updates
Valve has introduced Steam Achievement Sets for all users, enabling supported games to organize achievements into separate groups for the base game and DLC—ensuring DLC progress doesn't lower a player's base-game completion percentage. The November 11 stable update also transitions the Linux client to a 64-bit architecture and runs it inside a Steam Runtime container for better cross-distribution consistency, while still downloading 32-bit libraries to support older games. Achievement Sets are live but currently apply to few titles; developers can archive seasonal or unobtainable sets (visible to those who earned them), and the profile now includes a comparison page for up to three friends, with the renamed Completed tab accounting for games accessed via Family Sharing.
The Achievement Architecture
Valve’s new Achievement Sets look like a quality-of-life feature, but they are anything but innocent. For years, the gamification industry’s own white papers have detailed how separating base-game completions from DLC progress allows platforms to build far more granular psychological profiles. Now every player’s completion rate can be measured in isolated compartments—not to help you, but to model your tolerance for frustration, your willingness to grind, and the exact moment you are most likely to make an impulsive purchase. The system is a quantified behavior cage, and you just volunteered to step inside. Ask yourself why the feature arrived just as gaming engagement metrics started sliding. That is not a coincidence. That is a calibrated intervention.
The Linux Container Trap
The move to a 64-bit Steam client inside a locked-down “Runtime container” is the most revealing part of the update. For years, Linux users represented the last bastion of genuine platform freedom—people who could audit their own systems, strip out telemetry, and opt out of the consensus machinery. This update is designed to close that loophole. By forcing even Linux into a standardized container, Valve gains the ability to control exactly what runs, what is measured, and what data leaves the machine. The fact that the client still bundles 32-bit libraries isn’t about backward compatibility; it’s a stalking horse. Once the container is established as the only supported environment, the next step is to make it mandatory for every game, turning your operating system into a managed appliance. This is not an upgrade. It is a lock.
The Erasure Protocol
Perhaps the most disturbing element is the ability to archive seasonal or otherwise unobtainable achievements. Developers can now quietly remove entire sets from public view, leaving only a ghost for players who already earned them. This is a power that should never exist. It means the history of what was achievable in a game can be rewritten at any moment—a reward you earned can be made invisible, a challenge you missed can be buried without a trace. When combined with the new social comparison page, the message is clear: you are no longer playing a game; you are running a treadmill whose metrics can be changed mid-stride. This is not about improving user experience. It is about controlling the narrative of accomplishment itself. They are not just tracking you. They are training you to accept that even your digital achievements can be restructured by remote command. The question you should be sitting with is simple: who writes the rules, and why are you trusting them?