2.0 Dropping EARLY really wasn't good

kingofthezeds

kingofthezeds

Refugee
I've heard a hundred people complain already about 2.0 bricking everyone's saves on console, and I've heard the argument that it was announced on the front page of the game every time you load it etc...

Putting all that aside...

A couple of my friends have been playing 2.0 on console together since it was available. Many months of work has gone into their save.

They'd planned for weeks to reach the point where they could get their level 300 achievement during a one-last-game finale.

They'd spent hours in the week leading up to their final session getting everything (resources, bases etc) ready for one big blowout, changing their settings to horde every night, every half hour.

After ALL this, they sat down on Friday night for the culmination of all their efforts and work for this epic last session on their soon-to-be-dead save game...

AND TFP RELEASED THE 🤬🤬🤬🤬 2.0 UPDATE 3 DAYS EARLY AND THE GAME AUTO-UPDATED, RIPPING THEIR EPIC SESSION CRUELLY AWAY FROM THEM!

It was Monday June 30th all over every announcement I ever saw, or they saw.

It seems everyone was surprised about it dropping early.

So YES... It may have been announced that save games would soon be broken.

But I got really pissed at the "fun" pimps when my mate relayed this story to me today.
 
Man...that's too bad. Condolences for the loss of their save game. Situations like this are for sure evidence that doing an early surprise release is probably not good for the future. For all the people that were happily surprised by the early weekend of being able to play, they probably would have been happy anyway to play it when it was expected to be released.

I'll be sure to relay this story to Rick so it is something they definitely consider if the option to do a surprise early release of 3.0 becomes a possibility. I think they were just excited to get it out to the people on console who had been waiting and watching their PC cousins play the experimental and that was their focus.
 
Thanks for your reply and relaying to Rick. I'm normally right behind what TFP are doing, but this one just stung a bit.
On the other hand, I was happy at the time when it came early because it gave me longer to set up a server and test crossplay etc so I can play with said console mates this week.
 
Yeah, that's a bad situation. And they probably didn't consider it. They likely assumed everyone would be happy to have an early release. Sometimes certain possibilities don't get thought about, unfortunately. I think the early release wasn't a good idea even without this specific issue. There have been so many bugs that have come up (many already fixed) that really could have been done before releasing stable instead of having to do a 2.1 version after only a week or two. It felt too rushed rather than a situation of "everything is done and is tested and looks good, so let's release early". Faatal said they were already looking at an early release a week before the release, which leads me to think they got focused on pushing for an early release and that blinded them to releasing it in good shape. Hopefully they'll reconsider early releases in the future, or at least verify things really are ready for an early release and let people know in advance of the early release so they can plan for losing their games.
 
Yeah, there is a bunch of people who got caught by surprise before finally reaching Level 300. One was 299 when turning on his PS5 on update day.
And all that for such a useless achievement. Still don´t get why we have 300 levels. It´s not like there will be anything in the game that makes that necessary.
 
Sorry to hear about your friends’ loss of progress, kingofthezeds. For better or worse, releasing ahead of schedule was a surprise for me as well. I have to believe if TFP could simply allow users to select between builds of the game on Xbox & PlayStation, the way they’ve set it up on Steam, they would.

Did anyone else on console attempt to play V1.4 again without updating? @Lax reports this didn’t work on Xbox Series X, which is consistent with my research on the subject. But the result for PlayStation is less clear.
 
"by June 30" is not the same as "on June 30", and TFP stated the former regarding stable release. I was also surprised it got rolled out before the 30th, but it was a pleasant surprise for me and my crew.

Sucks for your homies, but assuming consoles can't opt out of an update to the game, perhaps TFP will stick to a specific date for going stable with 3.0 or whatever instead of a by date as they did this go around.
 
Crater Creator said:
Sorry to hear about your friends’ loss of progress, kingofthezeds. For better or worse, releasing ahead of schedule was a surprise for me as well. I have to believe if TFP could simply allow users to select between builds of the game on Xbox & PlayStation, the way they’ve set it up on Steam, they would.

Did anyone else on console attempt to play V1.4 again without updating? @Lax reports this didn’t work on Xbox Series X, which is consistent with my research on the subject. But the result for PlayStation is less clear.
Click to expand...
I'm on PS5 and when trying to start a 1.4 game after the 2.0 update, my start button was greyed out and wouldn't let me try.
 
As a Steam player, I am very sorry for those on console (and the Microsoft store iirc) because you guys have no choice but to update. I think TFP just wanted to surprise us since everyone was super hyped for 2.0, plus it's become a running joke that they never release anything on time. In the future it would be nice for a heads up to be given so people are not caught off guard in a bad way.
 
You must log in or register to reply here.
Back
Top