Exactly my point.That would only be valid for some features which are not impactful (like the announced assets) but barely for fixes on existing bugs, especially on anything affecting the simulation as that stuff can only really be tested as a whole with everything else being in place. Changing one end can lead to unpredictable reactions on another end, so things which are currently planned can be removed last minute due to unwanted effects.
If the upcoming patch does include fixes to the game (and frankly, I am not expecting anything big), they are available now already. They will not change anything anymore this week, even less so considering the fact that they allegedly have to wait for third party certifications for their patches.
Given the timelines it becomes clear that PDX/CO are trying to buy time. March is the last month of the quarter, so they seemingly are trying to create the best quarter result possible under the given circumstances.
The last patch has been three months ago. It can be safely assumed that the release of any new "functional" patch has been and will be planned ahead, given the disastrous results of recent patches.
This planning includes (better: should include) that any patch has passed the PDX QA before it was transferred to the above mentioned third parties. That would have been last week - and may have been the reason why on Monday it was something "BIG" to come while on Wednesday it was downgraded to "a little something" - which, as far as CS2 is concerned, was the correct term.
This week is at its best meant for those third parties to do their job - but PDX should be pretty sure about their own assessment.
The pure fact that this patch will not be released at the anniversary date but a week later leads me to assuming that they indeed did have to downstrip it and to adjust the release date accordingly. In turn that would mean that CO did mess up once again - which does fit to the pattern.
- 9
- 2
- 2