Mission-Files (.mis) that work - or do not work - STEP 3

[REV_BL!TZKR!EG]

Okay, new version. LUCMIS() now brings this table:

Code: [Select]

module_LUCMIS written by BL!TZKR!EG/REViSi0N+DEF

Class=DDHuntIII     |Type=4  |Origin=British
Class=CVIllustrious |Type=9  |Origin=British
Class=CVIllustrious |Type=9  |Origin=British
Class=DDTribal      |Type=4  |Origin=British
Class=DDClemson     |Type=4  |Origin=British
Class=DDCClass      |Type=4  |Origin=British
Class=DDJClass      |Type=4  |Origin=British
Class=DDV&W         |Type=4  |Origin=British
Class=OTMS          |Type=101|Origin=British
Class=CLDido        |Type=6  |Origin=British
Class=DDCClass      |Type=4  |Origin=British
Class=DDJClass      |Type=4  |Origin=British
Class=DDHuntIII     |Type=3  |Origin=British
Class=LL            |Type=102|Origin=American
Class=OTMS          |Type=101|Origin=American
Class=VV            |Type=102|Origin=American
Class=KSQ           |Type=102|Origin=Netherland
Class=LL            |Type=102|Origin=American
Class=DDHuntIII     |Type=4  |Origin=British
Class=FFBlackSwan   |Type=2  |Origin=British
Class=COFlower      |Type=1  |Origin=British
Class=DDCClass      |Type=4  |Origin=British
Class=PCTrawler     |Type=0  |Origin=British
Class=PCTrawler     |Type=0  |Origin=British
Class=PCTrawler     |Type=0  |Origin=British
Class=PCTrawler     |Type=0  |Origin=British
Class=COFlower      |Type=1  |Origin=British
Class=COFlower      |Type=1  |Origin=British
Class=SSTypeVIIC    |Type=200|Origin=German
Class=SSTypeVIIC    |Type=200|Origin=German
Class=SSTypeVIIC    |Type=200|Origin=German
Class=SSTypeVIIC    |Type=200|Origin=German
Class=SSTypeVIIC    |Type=200|Origin=German
Class=SSTypeVIIC    |Type=200|Origin=German
Class=SSTypeVIIC    |Type=200|Origin=German
Class=SSTypeVIIC    |Type=200|Origin=German
Class=DBJU87Stuka   |Type=302|Origin=German
Class=LBJU88        |Type=302|Origin=German

Opening D:\_SH3_\SilentHunterIII-GWM\data\sea\EnglishNames.cfg
Opening D:\_SH3_\SilentHunterIII-GWM\data\sea\GermanNames.cfg
Opening D:\_SH3_\SilentHunterIII-GWM\data\air\EnglishNames.cfg
Opening D:\_SH3_\SilentHunterIII-GWM\data\air\GermanNames.cfg
Opening D:\_SH3_\SilentHunterIII-GWM\data\land\EnglishNames.cfg
Opening D:\_SH3_\SilentHunterIII-GWM\data\land\GermanNames.cfg
Opening D:\_SH3_\SilentHunterIII-GWM\data\ordnance\EnglishNames.cfg
Opening D:\_SH3_\SilentHunterIII-GWM\data\ordnance\GermanNames.cfg

Units not found:
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
NONE = ALL UNITS OKAY

[REV_BL!TZKR!EG]

Next step is that I must read this result-table line by line
and see if the units have the same type in the target-installation. -> AIR -> LAND -> SEA

My problem are the idiotic path-names, what pothead did these in SH3?

For example how idiotic this is:
INGAME the ship is called "OTMS"
THE PATH of that very same ship is suddenly called "NOTMs_"

My question: Where is the table that lists those path names?
From where do I know (remember I must write this into program code!!!) that the ship OTMS is found in SEA\NOTMs_ ????

How does the engine of SH3 determine which folder it is for every unit? Or in other words: How does SH3 know WHERE (=IN WHICH FOLDER) TO LOOK for the corresponding .cfg file?