I can see what you’re saying - but I’m not convinced it was strictly a planned design change. It came across much more as a feature they didn’t bother to add back in after making other changes because they ‘believed no one used it’ (based on them stating that they don’t use it). Less an active decision and more an omission because they viewed it as unimportant. The feedback quickly disabused them of the idea that no one used it, so they added a limited version of the original functionality. Unfortunately, in the process of fixing multiple issues (not just custom split stack) they somehow messed up the toggle sprint (I’ve no idea what exactly they were adjusting that led to the problem, but experience using mods tells me that seemingly completely unrelated systems within this game can have strange impacts on each other). And now they have to fix that (and other things), so who knows what’ll be impacted next

It’s also worth remembering that some portion of the 2 week schedule on these hotfixes tends to be about getting it through Microsoft/Sony’s systems. They may have had the fix ready to roll out very quickly, but if they still have to wait for third party approval, they (and we) are kinda stuck.
As for why they didn’t heed testlive feedback - they rarely ever have, whether it’s a bug or an intended change - but they often seem to use some of that feedback to inform what goes into the first hotfix. Not a satisfactory solution from our side, but at least it means they can get started on the hotfix before the patch has even gone live. Unfortunately something just went particularly wrong this time. We’ve both been around long enough to know that this hotfix into another hotfix situation is pretty unusual - normally it’s one hotfix and then wait for next main update for any further fixes - so at least it shows they’re taking the issue seriously, even if it is hard for us to understand why it happened in the first place.
1 Like