Stadia developers can’t fix bugs in their own game because Google fired them

Illustration for the article titled Stadia developers can't fix bugs in their own game because Google fired them

Picture: Journey to the wild planet

Apart from the dismissal of about 150 developers, the limitation of Google Stadia has left a lot of early adopters in the lurch. Stadia was maligned from the start, And if the latest Stadia user experience is any indication, it sure won’t leave a positive impression when you leave.

One of the few games that Google actually owns, although it was first released on consoles and PCs before making its debut on Stadia. was Journey to the wild planet. Google acquired Typhon Studios before the end of 2019, and the deal meant that Journey to the wild planet it was one of the few games that came free with the Stadia Pro subscription.

Typhon Studios was the first studio to be acquired by Google, but with the effective shutdown of Google’s gaming ambitions, the developers let go with everyone else. However, for users who still play on Stadia: at least the ones that aren’t suing Google – That has caused a little problem, because there is no one around to fix their games.

Anyone who tried to play Journey to the wild planet , Which came to Stadia Pro a few weeks ago, has encountered a number of bugs, including freezing in the main menu, crashes, Y pendant. And because it’s on Stadia, where game files are stored in a server farm away from your PC, regular users have no responsibility to fix the problem themselves.

Unable to play Travel In single player or cooperative mode, a user contacted the game editor, 505 Games. After the Stadia social team told him that they would work with the publisher on a solution, the publisher said: We can’t actually fix this at all.

Illustration for the article titled Stadia developers can't fix bugs in their own game because Google fired them

Screenshot: Reddit (u / lordubuntu)

“Unfortunately, there is nothing we can do on our part at this time, as all game code and data on Stadia is the property of Google,” 505’s support staff said in an email.

In a follow-up a few days ago, another 505 Games support staff member suggested that the user remind Google that, in reality, Google is responsible for publishing everything on Google Stadia.


Screenshot: Reddit (u / lordubuntu)

As the original lordubuntu poster pointed out, the situation sucks. You can’t really blame the original developers – Google fired them all, so it’s not really their fault to fix the problems in Google’s service. (I’m sure you’re not enthusiastic about leaving your clients high, but at the same time, would you lift a finger to help Google after you and all of your coworkers got laid off?). And Google support should be aware of the principle that traditional publishers cannot fix problems with Stadia the way they could with a normal game.

Of course it’s not fault of individual support staff. It’s an absolute disaster, although many expected given Google’s track record of canceling projects. Also, it is worth remembering that games keep coming to Stadia. “You can continue to play all your games on Stadia and Stadia Pro, and we will continue to bring new third-party titles to the platform,” Stadia’s Phil Harrison said in a blog post. earlier this month.

But if this is the quality of service users can expect when things go wrong, why would you invest more in your Stadia library, especially when better services exist?

This story originally appeared in Kotaku Australia.


Source link