Wheel Make It Steam Delay Leaves 11,000 Wishlists and 15-Player Peak

Wheel Make It, a physics-driven comedy co-op game about propelling a wheelchair through chaotic challenges, has become a sharp illustration of how precarious a small Steam launch can be. Publisher 2 Left Thumbs says the game had more than 11,000 wishlists before release, but recorded a 24-hour concurrent-player peak of only 15 after it arrived on November 1. At the point those figures were checked, three people were playing.

The publisher’s central complaint is not that every wishlist should have become a sale, nor that the game was destined to dominate Steam’s charts. Rather, it argues that an approval delay broke the promotional momentum it had built around an intended October 12 launch. Wheel Make It was not approved until October 25, and the team says it could not formally set a new release date afterward. In practical terms, it believes it was forced into something close to a shadow drop: a release with little of the visible countdown, public scheduling, and renewed attention normally associated with a planned launch.

The episode has also become part of a wider argument about Steam’s review workload, AI-assisted game submissions, and cloned games. There is evidence of developer frustration and of increasing page volume across PC storefronts, but no public evidence here that establishes exactly how much AI-related volume delayed Wheel Make It’s review, or that it was the decisive reason for the game’s low player count. That distinction matters. The publisher’s account is a credible description of its experience; the broader causal claim remains an allegation rather than a demonstrated fact.

A calendar problem, not simply a player-count problem

Low launch concurrency is common on a storefront as vast as Steam. A game with a tiny player count is not, by itself, proof of a platform failure, poor visibility allocation, or a bad game. A wishlist is also not a preorder. It is a signal of interest that can translate into purchases at wildly different rates depending on price, release timing, discounts, notifications, competing launches, friends’ availability for multiplayer games, and whether potential players decide to wait.

2 Left Thumbs acknowledges some of that uncertainty. The publisher has described Wheel Make It as “friendslop,” a knowingly silly small-team project rather than a supposedly essential indie masterpiece denied its deserved spotlight. It also concedes that people may simply have chosen not to spend $5 at launch. That candor gives the dispute a clearer shape: this is not a claim that a particular sales result was guaranteed, but that the team lost a fair chance to test the audience it had assembled under the conditions it expected.

The numbers create a conspicuous gap. More than 11,000 wishlists accompanied 11 user reviews, 90% of them positive, and a 15-player daily peak. None of those metrics measures exactly the same thing. Reviews reflect only a fraction of purchasers, while concurrent users measure people playing simultaneously rather than total owners. Yet together they explain why the publisher is dissatisfied: the initial visible activity was much smaller than it expected from the interest expressed before launch.

For a co-op game, timing may be especially consequential. Games built around playing with friends benefit from a shared moment: one person sees a release date, sends it to a group chat, and several people decide to jump in together. If the date disappears and the eventual arrival is less clearly telegraphed, that social prompt can be harder to recreate. This is an inference about the format and the publisher’s argument, not a measured explanation of Wheel Make It’s performance.

The review issue described by the team

Wheel Make It’s development posts provide a more specific account than a general complaint that Steam took too long. In an October 21 update, developer tlproductions said the game had failed review for a new issue that had not previously been flagged: the resolution-setting menu option was not accessible using a controller. The developer characterized the process as a nightmare and said Steam had confirmed the team would not be permitted to choose a new date.

Controller access to a resolution setting may sound narrow, but it is not an inherently trivial quality-assurance concern. Controller accessibility means that a player navigating without a mouse and keyboard can reach and operate needed interface functions. If a game supports controller play but strands players in part of its options menu, that can be a genuine usability problem. The disagreement is therefore not necessarily about whether the item required fixing. It is about the timing of that feedback, the effect of receiving it late in the review process, and what options a developer has once the original date no longer works.

Steam’s published review guidance says store-presence review typically takes three to five business days, while advising developers to submit at least seven business days before they want to go live to allow time for changes. Wheel Make It’s intended October 12 release and its October 25 approval sit uncomfortably beside that expectation. Still, the documentation is guidance rather than a promise that every submission will be approved within a fixed window. A game may need changes, and the information available does not show each submission, response, or queue stage involved in this case.

The practical takeaway for developers is less satisfying than it is useful: a launch plan needs buffer time for both predictable fixes and unexpected feedback. That is not a criticism of a small team for failing to foresee every issue. It is recognition that a release calendar can be vulnerable when the final approval stage sits close to the public date. If the process is running more slowly than normal, a buffer calculated around typical turnaround becomes inadequate quickly.

AI volume is a concern, but the causal chain is incomplete

2 Left Thumbs attributes the damaging delay to a review queue overwhelmed by what it calls AI slop. Valve has acknowledged problems involving AI and cloning on Steam, while other developers have separately described longer waits. Komi Games, for example, said it submitted Infested DX for review on October 9, received a requested small change on October 21, made it immediately, and was still awaiting a follow-up.

Those experiences point to a shared concern: review capacity may be under strain. An open game marketplace also reported on October 31 that the number of game pages created per day had doubled over the prior two months, seemingly boosted by AI. More submissions can mean more work checking store pages, builds, policy compliance, and reported infringement. But the available information does not quantify Steam’s queue, identify its internal triage rules, or isolate AI-generated submissions as the reason for a specific delay.

That gap should not be brushed aside, because the policy stakes are meaningful. “AI slop” is a loose and often emotionally charged phrase. It can describe low-effort, rapidly produced games; it does not precisely identify a technical category or automatically prove misconduct. The more concrete problem is submission volume: if a platform receives a flood of pages and builds requiring review, every legitimate developer may face a slower or less predictable approval process, regardless of whether their own game uses AI tools.

Cloning is related but distinct. A clone is a game or product that imitates another closely enough to create potential infringement, consumer confusion, or unfair competition concerns. Valve’s advice to developers confronting easily copied concepts has included avoiding reliance on a single mechanic that another party can reproduce, while directing extortion reports to law enforcement. That advice may reflect the limits of a storefront’s ability to adjudicate every conflict, but it is not a complete remedy for a studio that believes discovery and review systems are being overwhelmed.

The bigger question is operational: how can a large storefront review submissions quickly enough to support small developers while still checking key requirements and responding to abuse? Speeding review indiscriminately could let more deceptive or incomplete products through. Reviewing every submission more deeply risks imposing costly uncertainty on teams whose promotional plans depend on a date. Wheel Make It shows how that tension can land on a game whose issue was an interface setting rather than an allegation of fraud or infringement.

Why visibility and dates are so intertwined

Launch visibility is not one switch that is either on or off. It is a compound of storefront placement, wishlists, notifications, demo interest, a public release date, social-media posts, coverage, and the sense that players are arriving at the same time. The publisher says Steam had assured it that missing the original date would not change the usual launch-visibility mechanisms. It disputes that conclusion after seeing the result.

Both ideas can be true in different senses. A platform may preserve technical visibility mechanisms after a delay, while a developer still loses the human attention created by a known release date. A calendar slot lets prospective buyers plan around a launch. It lets a studio schedule posts, coordinate with collaborators, and convert curiosity into a shared event. If a date is removed or cannot be reset publicly, the underlying store algorithms may be operating as designed even as the campaign no longer has the same force.

This is why a 15-player peak should not be read as a simple verdict on Wheel Make It’s quality. It is one early result from a release whose context the publisher says changed substantially. Conversely, the delay alone cannot establish that the game would have had a much larger debut on October 12. The demo response, wishlist total, and pre-release momentum cited by the publisher are meaningful signals, but they cannot reveal the alternate outcome that never occurred.

For readers watching the broader PC storefront contest, this incident also drew an unsurprising reaction from Epic Games chief executive Tim Sweeney, who liked a post criticizing Valve. 2 Left Thumbs found that attention amusing, but clarified that its frustration was aimed at generative AI volume rather than Steam as a whole. The publisher has also said Valve’s support staff were pleasant and clear about their position, even though it disagreed with some rulings.

That nuance is important. This is not a neat “Steam bad, rival good” story. It is a case in which a developer can be unhappy with a platform outcome, understand the staff are not personally hostile, accept that a controller-menu issue needed attention, and still argue that the system’s timing left its game at a serious disadvantage. The PC store landscape is shaped not only by revenue splits or library features, but also by unglamorous workflows such as review queues, release-date controls, communication speed, and how exceptions are handled.

What Wheel Make It’s launch can and cannot tell us

It can show that 2 Left Thumbs experienced a delayed approval, a missed October 12 target, an October 25 approval, and a November 1 release followed by a 15-player 24-hour peak.
It can show that the publisher believes the loss of a public, planned release harmed its momentum, despite more than 11,000 wishlists.
It can show that at least one other developer has publicly described a lengthy review follow-up, adding to concern about turnaround times.
It cannot show exactly how many sales or active players Wheel Make It would have gained had it released on October 12.
It cannot show that AI-assisted submissions directly caused this individual approval delay without platform-level queue data.
It cannot show that the game’s reception, distinctiveness, price, or multiplayer premise played no part in its launch performance.

That last list is not an attempt to neutralize the publisher’s complaint. It is the basis for taking it seriously without turning an incomplete record into a settled diagnosis. The relevant problem is not merely whether Wheel Make It became a hit. It is whether a system that tells developers to plan around a certain review window can respond adequately when late-stage changes and heavy queues make that planning unreliable.

Small releases rarely get a second chance to create a first impression. Once a carefully prepared date is missed, the game may still be available, still receive updates, and still find players over time. But a launch campaign is perishable. Wheel Make It’s situation is therefore less about one goofy co-op game’s current concurrent count than about the vulnerability of studios that build months of outreach around a date they do not entirely control. For more on the structural advantages shaping PC storefront competition, see the challenge of shifting Steam’s entrenched user base.