Interested in playing PvP in Arma3? Check out FUSION
And don't get me wrong: I am eager to play CCGM. I did a lot to spread the word and I will continue to do so. AND I am glad to be a P&C Club Member. I will NOT call for any refund whatsoever!
“Invincibility lies in the defence; the possibility of victory in the attack.” - Sun Tzu
For my part, I was disappointed that the interaction with the devs has been poor to non-existent. But I'm still looking forward to the final game, and even feel I got my money's worth even out of the beta.
So, I won't be asking for a refund.
Next, being an alpha, REGULARLY build and release. Even if it's small fixes. People love to see progress, even if it's slow. Hell, when there isn't much contact with the Dev team, people *love* patch notes and lots of patches, it's that feeling that SOMETHING is being done. This alone would have made the P&C go much smoother for us.
On that note, your Arma release cycles are too slow; we would have regular beta releases every couple of weeks, but why wait so long for a new official version after 6 months? Many of us use mods and the game built on day one of beta releases anyways, so what's the harm in more rapid release cycles?
I also felt like the bug tracker was not being updated enough. There are those of us out here that really want to help, you could hand out some direct lines to the dev team, be it through a skype conversation, etc, so that those moderators can get feedback and help keep the tracker clean. Let the devs tell the mods what they are thinking of doing, and the moderators can put it in writing, acting as their liaison.
tl;dr More contact with the community, even if it's brief. You need MUCH faster release cycles, even with tiny bug fixes, and let some of the community help moderate the bug trackers and forums so you guys can focus more on your work.
Last edited by Anticept; Jul 25 2012 at 23:17.
The issue that I've brought up and been very vociferous about is the "Game crashing on save" fatal bug that causes the game to either hang indefinitely or crash to the desktop. What doubly sucks about this particular bug is that it only seems to happen after I'm on the last couple of enemy islands and have invested 20 hours or more over the course of days and weeks. I've brought this issue up in the feedback tracker multiple times and been called out for my over use of CAPS owing to my inestimable frustration in regards to this bug. I stopped playing the first version of the beta because of this bug. And I played the second version of the Beta with the false hope that this bug was fully quashed. However, the game saving crash cropped up late in the game and I wasted so many hours trying to find a way past it with no success. So I stopped playing the second version of the Beta and eagerly awaited the 3rd version.....which never came ?!?!
While I'm not pursuing a refund.....yet....I do remain disappointed we haven't seen 2 or more (refined) versions of the Beta since version#2 debuted back in May.
All this being said - if the game ships with this game saving bug crash it will be a critical flaw that will ultimately doom the success of Carrier Command for Bohemia Interactive .
I do hope they are working on CCGA in secret or this is going to be one extremely buggy release scoring a whopping 2 out of 100 on GameSpot.
It is FEATURES that must be thoroughly tested.