Title: Owlcat Pulls the Plug on Controversial Warhammer 40,000 Launcher After Criticism
In a surprising turn of events, Owlcat Entertainment swiftly decided to scrap its newly introduced launcher for Warhammer 40,000: Rogue Trader after just 19 hours in operation. The launcher was originally designed to consolidate updates and news related to the game. However, the reaction from the player community was overwhelmingly negative, leading to an expedited retraction of the feature.
The launcher aimed to create a centralized hub for players, eliminating the need to scour various platforms for game news. Despite Owlcat’s claims of the launcher being unobtrusive—it did not require mandatory registration and allegedly did not collect any user data—the reality proved otherwise. Many players expressed their disdain for this kind of software, which they viewed as unnecessary bloatware that hindered their gaming experience.
Soon after the launch, feedback flooded into forums and social media, with players discovering that shutting down the launcher didn’t actually deactivate it; instead, it continued to run invisibly in the background. This oversight became a significant point of contention, especially when players found that closing the launcher resulted in the game erroneously not recording their playtime on Steam. The confusion stemmed from the launcher being integrated as the game’s primary ID on the platform.
In a candid discussion on Reddit, Owlcat’s community manager, Starrok, acknowledged that this experience had not been well managed, admitting that they had not been informed about the change prior to its implementation. They promised to investigate alternative methods to the time-tracking issue that did not rely on a hidden process consuming memory resources.
Instead of trying to salvage the launcher, Owlcat wasted no time in rolling back to the previous patch, which completely eliminated the launcher and its associated complications. The studio issued a public apology, thanking players for their feedback and expressing regret for the frustration caused.
While it is commendable for a developer to listen to player concerns and swiftly act upon them, the entire episode raised eyebrows over how a studio could misjudge player sentiment ahead of a feature launch. Notably, this was not Owlcat’s first stumble; similar backlash in the past had prompted them to discard a data-intensive tool in another title.
Editorial: This swift removal of the launcher highlighted the importance of community feedback in game development, illustrating how crucial it is for studios to engage with players to avoid unnecessary controversies.