I am not sure that is the case. It couldnt have been avoided in my opinion. It is part of their ethos it seems: lets see how much we can get away with. If they released in three weeks it would be the same mess it was. The fact that there
was so much negativity and input from people with knowledge of what is letting the game down has forced them to get there finger out and improve things.
I don't think we should underestimate the input the beta testers post release are having on the improvements to the game. They are on loop in their ears telling them what needs to happen to make the game better.
Its like a lazy cook: all the ingredients are there but couldn't be arsed so half baked the cake. Now the people who are eating the cake are telling them: back in the kitchen and bake the effing thing properly!
Something like that.
I will add that I do think there are some passionate and caring developers involved with the game, probably the vast majority. I know
@MattW is genuinly passionate about getting the dream cricket game. But there are constraints from a higher level that are in my opinion counterproductive to the creative process. I know nothing about this of course and it is based on nothing than my own flawed perspective but that is the way it seems to me after watching from afar and being involved in beta processes right up to Cricket 22 which I left because of the way things were being done and especially the way that developers would get angry because you pointed out faults in their work. I called out right at the beginning of Cricket 22 that it was basically a copy paste job. Remember then that the big selling point was the overhauled fielding. Sound familiar?
