Should The Asendancy Update Be Rolled Back?

Well, PPV2 has piqued the interest of my son and he's about to pledge and is building/egnineering a Python Mk 2 bounty hunter. I have yet to work out who I want to pledge to, not sure if I should follow his lead or go my own way as I wonder if pledging to two separate powers would cause complications when we play together. But undoing that is a big no from me.
 
Seems like every time there is a major update someone starts a thread asking if the patch should be rolled back.

Its a silly thing to suggest, because rolling back is not really a simple process, especially when you have thousands of players already playing on it.

The rolling back itself could cause way more issues for players than doing nothing.

I'm half convinced that people who suggest "rolling back" know nothing about software development or even what rolling back really means, they just heard the phrase once and decided they have to use it somehow.

The solution is to fix the bugs, not roll back. Rolling back is generally left for when the released system is literally unplayable.
 
Sounds like a total knightmare.

1731103069979.jpeg
 
Speaking as someone who did not have a massive stockpile of exploration or exobiological data to hand in for PP2.0, I think it's a bit bobbins that all that hard work has been so casually rendered pointless. They genuinely worked hard for all of that data, and it's going to take more weeks/months/years to build up another stockpile of such a size (during which they're not going to be able to do much else anyway). It's not even as if they actually cheated or anything like that.

How was it pointless? They still got the cash for all of the work they did BEFORE the release of PP2, which is the same thing as everyone else got for turning in data BEFORE the release of PP2.

If you’re insisting on giving PP2 merits for data that was obtained before the PP2 release the you might as well award merits to everyone else that has ever turned in data as well.
 
There are multiple bugs in the new powerplay system.

Some players have missions they can't complete because the mission origin and destination are the same, and the powerplay mechs mean they can't be completed.
Some players are missing weekly tasks.
There's a possible bug with NPCs interdicting in non-powerplay systems.
Settlements in non-powerplay systems have no loot/data spawns (affecting progression in Colonia).
Merits appear to be highly unbalanced.

All in all, the update is a buggy mess that is causing severe player progression disparity. With that in mind, I ask:
Should FDev just roll the update back and actually test it properly before deploying it again?
wurd
 
Seems like every time there is a major update someone starts a thread asking if the patch should be rolled back.

Its a silly thing to suggest, because rolling back is not really a simple process, especially when you have thousands of players already playing on it.

The rolling back itself could cause way more issues for players than doing nothing.

I'm half convinced that people who suggest "rolling back" know nothing about software development or even what rolling back really means, they just heard the phrase once and decided they have to use it somehow.

The solution is to fix the bugs, not roll back. Rolling back is generally left for when the released system is literally unplayable.
Player data and Game Code are seperate. Updating a game and rolling back an update are no different from a technical standpoint.

Signed,
A Software Developer
 
You want to lose the Mandalay that you purchased with ARX and spent time and materials to upgrade?

How about no?
Player data and Game code are seperate. You may lose access to the Mandalay (depending on the rollback) but it will still be there waiting in the future, when major game bugs are actually fixed.

Worth noting, the Mandalay release was delyaed and rolled into Ascendency, so there is no reason that it shouldn't stay in game after a rollback.
 
Player data and Game Code are seperate. Updating a game and rolling back an update are no different from a technical standpoint.

Signed,
A Software Developer

As a software developer you'd be very aware that it's not the software developer doing the roll back. It's the people using the software.

Signed,
An end user.
 
Thing is, for a game like this, some bugs and exploits only come to light when it's been played by a great many people at once all racing for a higher rank.
Also, this many people stress tests the entire thing more than any set of employed testers ever could. That's why the servers went down for maintenance last week and when they came back online everything was running a hell of a lot smoother then it had since the update was released.

Some bugs were clearly ones that could have been caught beforehand, but FDev do seem to actually be working on them fast (see the expansions going to random Powers issue). As someone who remembers the bug of the PP 1.0 conflict zones having opposed NPCs that did NOTHING but sit there, an issue that took a MONTH to be resolved, I'm actually fairly okay with smaller bugs because it seems they're actively being tracked and squished right now!

PP 2.0 is good. Ascendancy is pretty solid, and as I said earlier, running pretty smoothly after last week's maintenance (bar the long FSD jumps at times).
 
Last edited:
Player data and Game Code are seperate. Updating a game and rolling back an update are no different from a technical standpoint.

Signed,
A Software Developer

Player data structure could be changed after an update, so rolling back the game might also require rolling back save data (if such exists), or just go ahead and risk player saves becoming invalid as the older version of the game doesn't know how to handle the new save data.

Also, you're talking about the theory. I've seen a few rollbacks go boo-boo due to bad practices in version management.

Also, Mr Software Developer, i'm sure you know you only do rollbacks when absoloutely required, not just because of a few bugs that can be ironed out.
 
OK sure, don't roll back, but seriously fdev, fix this pile of spaghetti already.
Sometimes such complicated tasks as restocking ammo are too much for the servers, you get these error messages (see below).
An hour ago I accepted a simple wing assassination mission, which resulted in instant CTD and I even had to reboot afterwards because half of my keys stopped working for some inexplicable reason. This is borderline malware behaviour for a piece of software.
1731237942152.png
1731237976941.png
 
Player data and Game code are seperate. You may lose access to the Mandalay (depending on the rollback) but it will still be there waiting in the future, when major game bugs are actually fixed.

Worth noting, the Mandalay release was delyaed and rolled into Ascendency, so there is no reason that it shouldn't stay in game after a rollback.
Really as I recall the announcements both were always going to happen at the same time, then both got delayed a week.

But while I am sure there is no theoretical reason that a rollback has to remove both it seems sensible to a user that if the game is rolled back to before the update everything added by the update would go.
 
Back
Top Bottom