Good point. The last thing we need is a sequel to
Harpoon-like database chaos, the "solution" to which ends up being
innumerable duplicate entries for the exact same platform/weapon system/sensor entry - nearly one for each and every scenario written.
That's not a solution - that's a clunky workaround that renders the resultant database useless for actually looking up the various entries, since it becomes extremely difficult to wade through, say, 15 slightly different entries for the Tu-22KD, all of which represent the exact same platform.
Locking down the database also keeps people from stealing the info (which must have taken years to aggregate), which I suppose must frustrate some people known for that sort of thing.
So creating whatever your heart desires makes it a more realistic database? While I thoroughly enjoyed Fleet Command/NWP with their modded base, there was much turmoil when newer patches, nay, updates came out with the older scenarios and/or others modded scenarios with their own version of reality. It can get very frustrating when trying to troubleshoot CTDs. How do you mitigate mismatched databases when playing multiplayer?
Bumping