A couple questions I couldn't find answers for on the forum:

 

How are databases related to battlesets? Can you use any db with any battleset?

 

What is the difference between EC2000 and EC2003? They have the same scenarios.

I noticed that some scenarios download sections are listed for GUIK or EC2000 0r EC2003 all in one. Does this mean that the scenarios are interchangeable between all three battlesets.

 

I guess I just don't understand why there are different battlesets covering basically the same area with similar units involved.

A couple questions I couldn't find answers for on the forum:

How are databases related to battlesets? Can you use any db with any battleset? What is the difference between EC2000 and EC2003? They have the same scenarios. I noticed that some scenarios download sections are listed for GUIK or EC2000 0r EC2003 all in one. Does this mean that the scenarios are interchangeable between all three battlesets. I guess I just don't understand why there are different battlesets covering basically the same area with similar units involved.

 

A "battleset" will always include a map. It may also contain one or more scenarios and a database.

 

The oldest battlesets - GIUK, NACV, MEDC, IOPG, HDS 1 through 9; HDS A, B and C, and the EC2000 series - and all of the scenarios in them, all use a built in, non-editable database.

 

You cannot access this database through the Platform Editor (PE).

 

Also, any custom scenarios built using these older battlesets will necessarily use the built in, non-editable database.

 

The four EC2003 battlesets and the newest battlesets - Westpac, Caribbean Basin, South Atlantic, South Africa and the Middle East - and the scenarios that come packaged with HCE, all use the Official HCE Database, that is, the HCDB database hosted here at HarpGamer.

 

Custom scenarios built for any of these battlesets (that is, EC2003 and the newest ones mentioned above) can use either the HCDB or some other custom built database.

 

Also, any custom made battleset that one might put together using the BattleSet Builder utility, can also use either the HCDB or some other custom built database.

 

Scenarios available for download here at HarpGamer are organized by their appropriate battlesets. Fortunately this also tends to be organized by geography but the battleset will rule.

 

The scenario author should also have indicated which database he used to build the scenario, and which, of course, must necessarily also be used to run it.

 

Hope this helps. We will probably flesh out this thread and use the material to update the FAQ to help those who might have the same question(s) in the future.

 

Thanks for asking (and please go ahead and shoot if you have more questions) and welcome to HarpGamer!

That was very helpful...thanks.

Once again, thanks for the post. It should be in the manual or at least the readme.

 

A stupid question; why even include the old battlesets. Wouldn't have been better to just rebuild the old scenarios in the newer EC2003 format? It just seems it would confuse people and perpetuate designers continuing to support it.

A stupid question; why even include the old battlesets. Wouldn't have been better to just rebuild the old scenarios in the newer EC2003 format? It just seems it would confuse people and perpetuate designers continuing to support it.

 

The old battlesets and the scenarios in them still have plenty of 'life' in them. Although one cannot edit the database that they use, and the platforms represented in them are therefore fixed (and in some ways not terribly accurate), they are still great scenarios and have gallons of charm.

 

Keep in mind that the Game Engine (GE) code is the same regardless of battleset used.

 

Folks are certainly able to 'rebuild' or overhaul the older scenarios with a new database, or as part of a new custom battleset, but I cannot imagine we would ever entertain tossing the old battlesets.

 

Unfortunately only a handful of folks actually write scenarios and share them with the community. More of that kind of effort is always encouraged!

Once again, thanks for the post. It should be in the manual or at least the readme.

 

A stupid question; why even include the old battlesets. Wouldn't have been better to just rebuild the old scenarios in the newer EC2003 format? It just seems it would confuse people and perpetuate designers continuing to support it.

 

While I agree in theory with what Brad said ... I have been tempted to dump the old battlesets and not worry about compatibility. Some of the changes we make to the game have database data dependencies and we have to 'fake' it and derive representative values for the legacy battlesets (pre-EC2003). That takes time and changes the way the scenarios play. Therein lies a purposeful design decision, that we want the legacy battlesets to run without crashing but that we won't make an undue effort to keep them playing like they may have played a decade or two ago.

 

I still think it a very real possibility that we'll at some point ship a different game engine (GE/winharp32.exe) for the legacy battlesets and forget about that backward compatibility.

 

Brad also very gently mentioned that this is a volunteer effort. We have 'real jobs' and do this for fun. That means there isn't enough time. Ideally a slew of players would step up and re-build the legacy scenarios. A few of us did just that for the USNI Battleset in the demo and I really like the result! That database (made by Brad/CV32) could be a nice foundation for remakes. I'd happily include such full remake battlesets in the game distribution as long as they keep a similar spirit to the originals.

Thanks from me too! Appreciate the info. I was wondering this myself!

> Keep in mind that the Game Engine (GE) code is the same regardless of battleset used.

 

Hi,

I have a maybe stupid question about this issue - do all HCE engine improvements (AI, etc.) are working in the older battlesets? Or are they available for the new ones only?

 

Francesco

... do all HCE engine improvements (AI, etc.) are working in the older battlesets? Or are they available for the new ones only?

 

Yes, by and large, all GE changes (improvements or otherwise) translate into the older battlesets.

 

Keep in mind, though, that some changes were intended to be reflected in the database and the inability to edit the old database keeps some of them from being fully or properly incorporated.

 

For example, the Tu-16 Badger J electronic jamming aircraft in some of the older battlesets lacks a jammer.

... do all HCE engine improvements (AI, etc.) are working in the older battlesets? Or are they available for the new ones only?

 

Yes, by and large, all GE changes (improvements or otherwise) translate into the older battlesets.

 

Keep in mind, though, that some changes were intended to be reflected in the database and the inability to edit the old database keeps some of them from being fully or properly incorporated.

 

For example, the Tu-16 Badger J electronic jamming aircraft in some of the older battlesets lacks a jammer.

 

Got it. Thank you.

Francesco