Parcelmoose
Associate Cricketer
- Joined
- Oct 19, 2017
- Profile Flag
- England
Except their games haven't always been "better", that's been the problem. If anything, their games have shipped buggier each time, and show the telltale signs of a game released before it's been fully tested. The fact that things like pitchware still weren't fixed on release of Ashes or things like cover drives not being doable on release of DBC 17 were silly. They weren't game destroying, but they certainly spoke to a lack of QA. DBC 14 remains their best game out of the box.
Hell, I was one of the most vocal in support of BigAnt for years too. I invested a huge amount of time into DBC 14 and 17, although my work in the community was largely limited to DBC 14. It's not about "what I'd consider gospel", but rather anything they can do to break those patterns. When granny gets on the drink, you know what's going to come out her mouth; that's what we're seeing from BigAnt at the moment.
Again, the game isn't going to be bad, but you can bet your last dollar that it'll have some glaring bugs across the board on release, the first patch will makes 90% of those worse, and about 30-50% of those issues will never be resolved, even after their skeleton patching crew spending several months "patching" the game.
This is the thing, I really hope some competition appears. That said, the big issue seems to be that BigAnt are racing their shadow. If anything, competition might make them rush more.
The biggest issue now is that they have Ashes release deadlines. The stumping bug in AC17 was ridiculous, and then there was a patch released months later that meant the ball did not swing for a time. They should really be starting to nail these games, but after AC17's numerous backward steps; I have my doubts.
There isn't enough money in cricket games for major competition, and whilst BA hold the Aus and Eng licenses the onus is on them to keep making better games