[Mobhack]

No, not as the way the game is coded.

An OOB full name ("United Kingdom") is hard coded, as is the short name ("UK"). In #define statements in the global data. Not stored as variables at all. The leader names and rank names once were, but we exported those to text files a long time ago.

The flag data is hard-coded, and OOBs whose flag changes with the time of the week, have that set in a special bit of flag-swapping code. So if you decide to use OOB X for "new country" - if the original OOB swaps flag after the glorious revolution, you will have the new flag turning up.

The OOB ID also determines where the national flag turns up on the pick a nation type screens - so the South Americans are grouped together, Arab-Israeli war ones etc. Changing Israel to Ruritania would have Ruritania showing as a Middle Eastern country when you wanted it to be in Central Europe. And then again, OOB slot ids get re-used occasionally, or like Georgia replace a nation that fell off the list, leaving a blank slot on the nation picker screen. All hard-coded, and a total nightmare to try to make "data driven" in e.g. some Byzantine mix of XML the game's own programmer could hardly make sense of - let alone some end-user OOB designer.

The Battle locations are hard coded in a large lump of code tat determines who fights where, if say UK plays Argentina and dates are important there too (1982 may produce Falkland Islands forex..). Also, things like "is it winter if X plays Y in this batloc and this month" - please tell me some sane way to just tack that onto some sort of OOB data file!

The leader and unit experience and morale tables are hard-coded in global data. As are the air strike probabilities, counter battery etc. - any stuff that behaves differently for nation X in year Y. As are things like fanatic no-surrender behaviour for e.g. WW2 Japan.

In MBT, we have data-driven pick lists, so that is less of a problem. Actually, it turned out to be more of a problem. WW2 has the pick lists in code, and if I were to rewrite MBT then they would go back to being buried in the code as well, since data-driven lists are in actual fact more of a ***g pain to change than simply wrangling a few if statements in code!.

In fact - looking at the experience with pick lists, the chances of doing some form of "data-driven" OOB type game is probably close to the square root of Sweet Fanny Adams.