Stadia developers can’t fix the bugs in their own game because Google was shooting at them

Photo for an article titled Stadia Developers Cant Fix The Bugs in their own game because Google was shooting them

Image: A trip to the planet Savage

In addition to the sacking about 150 developers, the thrush of Google Stadia has left a ton of early adopters well and truly in the church. Stadia was maligned from the beginning, and if the latest experience of Stadia users is any indication, it’s certainly as hell not to leave a good impression on the way out.

It ‘s one of the few games Google actually has – although it was first released on consoles and PC before its debut at Stadia – there were A trip to the planet Savage. Google acquired Typhon Studios by the end of 2019, and the agreement meant that A trip to the planet Savage it was one of the few games that came free with a Stadia Pro membership.

Typhon Studios was the first studio acquired by Google, but with the effective closure of Google’s gaming desires, the developers there were let go by everyone else. For users who are still playing on Stadia though – at least the ones that don’t claim Google – that has caused a bit of a problem, because no – one is around to fix their games.

Anyone who tried to play A trip to the planet Savage – who came to Stadia Pro just a few weeks ago – has run into a series of bites, introducing a freeze on the main plate, disasters, and hanging. And since it’s on Stadia, where the game files are stored on a server farm far away from your PC, regular users don’t have a remit to solve their own problem.

Unable to play Tour in single player or co-op, one user reached out to publisher of the game, 505 Games. After telling the Stadia social team that they would be working with the publisher on a solution, the publisher said: Honestly, we can’t arrange this for you at all.

Photo for an article titled Stadia Developers Cant Fix The Bugs in their own game because Google was shooting them

Screenshot: Reddit (u / lordubuntu)

“Unfortunately, we can’t do anything from our end right now because all game code and data on Stadia is owned by Google,” a 505 support worker said in an email.

Following a few days ago, another 505 Games support worker suggested that the user be reminded of Google, of course, Google is the one who is responsible for publishing everything Google Stadium.


Screenshot: Reddit (u / lordubuntu)

As the original lordubuntu poster noted, the setting is a complete shitshow. You can’t blame the original developers – Google fired them all, so it’s not their fault that Google’s service solves problems. (I’m sure they’re not excited about leaving their customers in the lighthouse, but at the same time, would you raise a finger to help Google after they shoot you and your colleagues? ?) And Google ‘s support should know from the outset that traditional publishers can’t solve problems with Stadia like they might for a standard game.

Of course, it’s not the fault of the individual supporters. It’s just a real message, although many would have expected it because of Google’s history cancel projects. Also, that is worth remembering games are still coming to Stadia. “You can continue to play your games on Stadia and Stadia Pro, and we will continue to bring new titles from third parties to the platform,” Phil Harrison at Stadia said in a blog post earlier this month.

But if this is the quality of service that customers might expect when things go wrong, why not invest more in your Stadia library – especially when better there are services?

This story first appeared Kotaku Australia.