Steam Backlog: Developers Must Now Test Their Games via Steam Client
Releasing a game on Steam has become a significant test of patience for many developers. Valve is currently struggling with a growing number of submissions, many of which fail initial reviews due to basic technical flaws. To accelerate the verification process and reduce the need for repeated checks, the platform operator has updated its requirements, forcing developers to ensure their games actually work within the Steam ecosystem before submission.
In a communication released on November 3, Valve revealed a surprising trend: some developers appear to be testing their games exclusively by launching the executable file directly, bypassing the Steam client entirely. This has led to instances where games submitted for review had never actually been launched through the Steam client. To prevent this, Valve now requires that every game must be run via the green 'Play' button within the Steam client for at least five minutes prior to submission. This proof of runtime must have been established within the last seven days; for older builds, the playtime must be recorded since the most recent upload. Interestingly, the identity of the user running the game does not matter—the requirement focuses solely on ensuring the software functions correctly through the Steam client.
Wait Times Up to Twelve Business Days
The volume of submissions for both games and store pages has increased significantly in recent months. While Valve typically completes reviews within three to five days, developers must now prepare for wait times of up to twelve business days. A major contributor to these delays is the necessity for re-evaluations after previously discovered bugs or technical issues. The real-world consequences of these delays were highlighted by the indie studio tlproductions. Their co-op title, Wheel Make It, was originally scheduled for release on October 12, but the team faced a two-week wait for Valve's approval. The review process was hampered by initial ambiguities regarding local multiplayer functionality and a subsequent failure because a resolution setting was inaccessible while using a controller. The game finally received approval on October 23 and was released on November 1, nearly three weeks behind schedule.
The publisher, _2 Left Thumbs_, noted that the delay effectively neutralized the momentum built up by the game's wishlist—which stood at over 11,000 users at the time. Upon release, Wheel Make It reached a peak of only 15 concurrent players. While it is difficult to definitively prove that the delay was the sole cause of this low engagement, the impact of timing in the digital marketplace remains a critical concern for indie developers.
The AI Factor and New Checklist Requirements
There is ongoing speculation among publishers that the influx of rapidly produced, AI-generated games is overwhelming Valve's review pipeline. While _2 Left Thumbs_ suggested this as a primary cause for the backlog, Valve has not officially confirmed a link between AI content and the increased workload. Instead, the company has attributed the congestion to the sheer volume of submissions and the increased frequency of required re-checks due to errors.
To mitigate these issues, Valve is expanding its pre-release checklist. Developers are now required to explicitly state necessary runtime components, such as DirectX or Visual C++, and verify their Steam Achievements. Additionally, for games utilizing Steam Cloud, developers must provide evidence that save data is successfully uploaded and synchronized. While Valve has announced further improvements to the approval process, no specific timeline has been provided for when wait times might return to their previous levels.
Гика
