bw_wolverine |
09-29-2012 04:05 PM |
I'll just say this in response:
This is a release candidate patch from devs who have stated very clearly that they are not putting any more priority or time into fixing Cliffs of Dover until the sequel is released (IF a sequel is released). There will be NO MORE fixing after they publish their last patch. THIS patch.
Yes, it's going to be looked at and tested (by us for free btw) and hopefully these issues will be corrected in the final RC patch but...
How many patches have we had where something gets broken every single time? What confidence is there that even when they tweak and tune this RC patch that something ELSE won't break? With this patch it's the Hurricane engines (again).
So in a system where every released patch breaks something or is unfinished how can there ever be a LAST one where suddenly everything works?
We're all just hoping that the RC patch breaks or doesn't fix something we can live with at this point I think. So I think I can understand Catseye's frustration and post here.
This whole saga of Cliffs of Dover is an exercise in frustration for the faithful. It's pushing everyone to breaking point, some more than others.
We'll keep testing and playing this patch release candidate but seriously think about the fact that this was a bug that got FIXED in the last patch and is back again. And then consider that 1C didn't release this patch as another beta to test, they felt it was good enough to release as a release candidate patch. How does THAT make sense? Saying it's a release candidate patch is just inviting people to lose their minds over the bugs. It should have been pushed as another beta.
|