Why is the map info duplicated in the scen and map files?

[BuddyGrant]

Does anyone know why the map info is duplicated in the scenario and map files? I thought I found a GS 2.1 bug because Tobruk [6977], Leningrad [7929], and Sevastopol [8463] all have hex PP values in the GS WW2.map file, but hex values of "0" in the GS 1939.scn file. I checked to make sure the original owning country of the hex and the new owner of the hex (when the hex is attacked & defeated) get the hex PP's and in both cases they do, so this is working as designed & there's no bug. That said, this means the game uses the WW2.map hex values and ignores the *.scn values, at least for the PP values of hexes. Maybe this also applies to setting a hex as nothing, a capital, a city, and oilfield, a mine, a fortress, or an airfield. So I wonder why the map info is included in the top part of the *.scn file.

Anyway, this is useful to know if you are manually editing the scenario files. Make sure to get the map info correct in the WW2.map file, regardless what the map info values in the scn file are. Also, I guess this means you cannot use different hex values for 1940, 41, 42, 43, 44 scenario's since they all use the same WW2.map file.

[Peter Stauffenberg]

Actually I have no idea. This is part of the vanilla game.

In the GS v2.1 editor you use the ww2.map for the raw map used by all scenarios. It's read before you can read each scenario.

I know that the settings in the scenario overwrites the ones in the ww2.map like the fortresses in the east in the battle of Kursk (1943 scenario). These fortresses aren't in ww2.map so they are read from the 1943.scn.

We have designed the scenarios so all map features except the fortresses are edited in ww2.map. That is the only file I edit when I make map changes. I have to reload and save all scenario files every time I make a change in ww2.map.

This is how the game was designed and we have to live with it. I don't edit the files manually, but use the editor so I don't see experience any mismatch.