Matrix Games Forums

Hi all,

I’m looking for some guidance from experienced modders on the cleanest way to move data from one scenario into another.

Specifically, I want to take the ship, ship class, aircraft, device, and LCU data from an older custom scenario and bring it into a newer scenario built on the modern map and database. I’m trying to avoid re‑entering everything manually if there’s a supported workflow for exporting/importing or otherwise transferring the data.

For those of you who have done large‑scale scenario work:
• What tools or methods do you use to export data from one scenario?
• Is there a standard workflow for importing that data into a different scenario number?
• Are there any pitfalls or steps I should be aware of when moving OOB elements between scenarios?

I’d appreciate hearing how others approach this, especially anyone who has modernized an older scenario or merged data across versions.

Thanks in advance.

Alas, you cannot port anything, but you have to open a scn (anything you like), do a save as new number, then type everything in yourself- gutting isn't it. This may be one reason there are not many big mods.

Cav.

I believe that once you create the new scenario by copying the old one, you can use witploadAE to export csv files from that scenario. You can modify those csv files then reimport them and update the scenario.

Instructions:

WITPloadAE version 9.0

This program will export the scenario database files for a scenario number to several CSV files.

As part of the export, a reference table CSV is generated showing the values for certain exported/editor fields.

In addition, it also provides the ability to import changes to these CSV files back into the scenario database files.

It is suggested that when creating a new scenario that you copy the original database files (wpa, wpl, wph, wpd, wpg, wpp, wpc and wps) to a new directory and modify them there. And then copy them back to the game’s scenario directory.

Do not modify any of the official scenarios (1-25) as this may impact your ability to apply patches in the future. If you want to change an official scenario, it is best to copy and rename them to a spare scenario number or load it by the Editor and then save it a spare slot.

Be careful. The import function does not check that the value entered for a field is within the game parameters. For example, assigning a weapon slot to a non-defined weapon device will not be picked up by the import.
The program will do simple byte checking - it will reject ("Value error") an attempt to load a value into a field that cannot hold that value.

Restrictions:
The first row (field names) must NOT be altered otherwise the fields cannot be imported.
The first column (UnitNumber) must always be first otherwise the program will not know which item number the fields apply to.
The scenario databases must exist in order for the import to function. If building a new scenario, copy the files for an existing scenario and rename them to your scenario number. Then import the CSV files for your new scenario.

Running the program:
The program is run from the command prompt.
Start->Run->cmd.exe

The CSV files are always created/read from the current directory.

Several parameters are defined for use with the program. The default parameters are:
a) Import the CSV files
b) To scenario #1 database
c) In the current directory.

To override the default case, the following options are available.

/e Exports to CSV format
/s### Scenario number (1-199) to import or export.
/d Path to the scenario files. In some window versions, the path must be defined in quotes (").
/i Use the default install path (“C:\Matrix Games\War in the Pacific Admiral's Edition\SCEN”).
/bX Use character X as a different delimiter than ',' between fields (eg /b; will use ';' rather than ','

Eamples:
To export scenario #15 in the current directory
witploadae /e /s15

To import scenario #15 in the current directory
witploadae /s15

To export scenario #15 from the default install directory
witploadae /e /s15 /i

To see options
witploadae /?


I hope that you find this program useful.

Michael
Australia

OK neat so things are possible - good.

What about map differences? My scenario is pre 2015 so I'm sure it has an older map. If I create a NEW scenario bases off of a stock scenario provided with the game that the new scenario will be using a newer map version?

If you are changing the actual map you will need to edit the hex data file. If just editing, adding, or delating bases the location csv can be edited and uploaded or use the AE Editor exe application.

And maybe consider using one of Andrews versions, updated or standard map. Updated is corrections to the map from 2009.

https://sites.google.com/view/witp-ae-m ... elease-map

Skyros wrote: Thu Feb 12, 2026 4:08 pm I believe that once you create the new scenario by copying the old one, you can use witploadAE to export csv files from that scenario. You can modify those csv files then reimport them and update the scenario.

Instructions:

WITPloadAE version 9.0

This program will export the scenario database files for a scenario number to several CSV files.

As part of the export, a reference table CSV is generated showing the values for certain exported/editor fields.

In addition, it also provides the ability to import changes to these CSV files back into the scenario database files.

How do I know I have version 9.0?

I have 1.126a installed and the timestamp on my witploadAE.exe is 7/6/2016