Pdubya64 wrote:I just feel that it's time. Time to move on. Time to give the community a non-moving target so that the modders can do their thing without worrying about being compatible. Time to let AGEOD know that we are more interested in a AACW2 than AACW.
Franciscus wrote:It is obvious that it is time to move on, and this in my mind is settled when PhilThib also agrees.
I did not vote in the famous "support" poll, and think that the mere existence of that poll is a direct consequence of the problems felt in this forum in the last few months.
I also hope that the eventual future development of an AACW2 does not suffer from the same problems. It is up to Ageod to find the main reasons for it and take the necessary measures to prevent future troubles.
Regards
Gray_Lensman wrote:I have to agree AACW needs to be finalized in a legacy patch.
However, going forward, AGEod will have to figure out what their response is going to be as the database discrepancies continue to be reported in the various threads AFTER the finalized legacy patch is released.
As I see it, they only have 3 choices:
1.) Ignore the post... i.e. don't fix the reported new discrepancy and don't respond to the post either.
2.) Respond to the reported new discrepancy thanking the poster but informing him the game is finalized and nothing further is to be done unless there is a game crash bug.
3.) Continue to fix the reported discrepancies even though they have supposedly "finalized" it.
The first 2 are probably unacceptable from a public relations standpoint. So what do they do?
Read the posts every day and you will see that these discrepancy reports still continue to come in regardless of the game's supposed finished condition. This is not from any lax support but more from the enormity of the design of the database itself. It is virtually impossible for a small designer group to eliminate these types of discrepancies prior to a game's release thus the need for continual after release support. This doesn't even take into account discrepancies introduced when new features are added after the initial release. AACW2 will have the same issues when/if it is ever released.
Gray_Lensman wrote:... This is not from any lax support but more from the enormity of the design of the database itself. It is virtually impossible for a small designer group to eliminate these types of discrepancies prior to a game's release thus the need for continual after release support. This doesn't even take into account discrepancies introduced when new features are added after the initial release. AACW2 will have the same issues when/if it is ever released.
Pdubya64 wrote:
I haven't played a game or campaign since 2007 when I did my AAR. Part because I have a lot of other irons in the fire, part because there is always some new problem unearthed by the latest patch or patches.
Return to “AGEod's American Civil War”
Users browsing this forum: No registered users and 29 guests