NUTTERNAME
Member
InValid Title
Last edited:
InValid Title
- Thread starter NUTTERNAME
- Start date
NUTTERNAME
Member
InValid Title
Last edited:
NUTTERNAME
Member
InValid Title
Last edited:
NUTTERNAME
Member
InValid Title
Last edited:
KG_Jag
KG Vice Kommandir
From September 2009--almost 6 years ago:
---------------------------------------------------------------------
From Steve on the BF forum:
"The four planned Eastern Front Familes are:
Summer 41 - Winter 41/42
Spring 42 - Winter 42/43
Spring 43 - Winter 43/44
Spring 44 - Spring 45
As luck would have it, the major TO&E and equipment changes were generally made during the Winter and rolled out Spring/Summer. This allows us to logically break things up so that we don't have too much to do for any one release compared to another.
Each Family, no matter what it portrays, is its own standalone game with between 3 and 4 Modules. This means we have roughly 12-16 Eastern Front releases planned. Families can never be combined with each other. Yes, that means you can't have something like a BT-5 swarms in 1945, nor a bunch of Pak37s trying to take on ISU-152s. You weren't supposed to do that in CMBB either, but we didn't explicitly prevent "cheating" in the Editor to achieve such non-historical matchups. Therefore, in theory CMx2's Eastern Front games will not be any different than what CMBB was supposed to be.
As for the order of release, we're starting with the last one (Spring 44 through Spring 45) and working backwards chronologically. From a marketing and development standpoint that makes the most amount of sense for us.
Steve"
See post #185 here:
http://www.battlefront.com/community...70#post1158970
Wow--four Eastern Front families with 4 or five releases each. That's about a decade of releases pushing at a far faster pace than we have seen so far. I wonder how many game engines will be involved in this plan (if it becomes reality).
---------------------------------------------
---------------------------------------------------------------------
From Steve on the BF forum:
"The four planned Eastern Front Familes are:
Summer 41 - Winter 41/42
Spring 42 - Winter 42/43
Spring 43 - Winter 43/44
Spring 44 - Spring 45
As luck would have it, the major TO&E and equipment changes were generally made during the Winter and rolled out Spring/Summer. This allows us to logically break things up so that we don't have too much to do for any one release compared to another.
Each Family, no matter what it portrays, is its own standalone game with between 3 and 4 Modules. This means we have roughly 12-16 Eastern Front releases planned. Families can never be combined with each other. Yes, that means you can't have something like a BT-5 swarms in 1945, nor a bunch of Pak37s trying to take on ISU-152s. You weren't supposed to do that in CMBB either, but we didn't explicitly prevent "cheating" in the Editor to achieve such non-historical matchups. Therefore, in theory CMx2's Eastern Front games will not be any different than what CMBB was supposed to be.
As for the order of release, we're starting with the last one (Spring 44 through Spring 45) and working backwards chronologically. From a marketing and development standpoint that makes the most amount of sense for us.
Steve"
See post #185 here:
http://www.battlefront.com/community...70#post1158970
Wow--four Eastern Front families with 4 or five releases each. That's about a decade of releases pushing at a far faster pace than we have seen so far. I wonder how many game engines will be involved in this plan (if it becomes reality).
---------------------------------------------
NUTTERNAME
Member
InValid Title
Last edited:
NUTTERNAME
Member
InValid Title
Last edited:
NUTTERNAME
Member
InValid Title
Last edited:
NUTTERNAME
Member
InValid Title
Last edited:
NUTTERNAME
Member
InValid Title
Last edited:
NUTTERNAME
Member
InValid Title
Last edited:
NUTTERNAME
Member
InValid Title
Last edited:
NUTTERNAME
Member
InValid Title
Last edited:
NUTTERNAME
Member
InValid Title
Last edited:
mOBIUS
Member
What difference does it make at this point?
NUTTERNAME
Member
InValid Title
Last edited:
NUTTERNAME
Member
InValid Title
Last edited: