In 2.45 it's not as easy as editing the Mapdata.py, though it's a Python editing, but you must
take a file from 2.40 and update according the Levels you have installed.
WORDPAD or TEXTEDITOR is good to go
The following is OFFLINE ONLY, DON'T USE when Multiplayer addict, may result in Banns, Flames or other Insults. ONLY FOR THE ADVANCED OFFLINE FIDDLER.
The File that is not easy to edit in 2.45, but in 2.40, is called:
...\EA GAMES\Battlefield 2\mods\fh2\python\game\plugins\NCOrifleData.pyc
Editing in this older is easier, takes 5 Minutes, but be as precise as a swiss watch and control
each init.con in all Mapfolders. Maps that you haven't got in Levels, but in this original file, are from the Devs (Kuuterselka, Crimea...).
I took the naming for my files from the Levelfolder Mapfolders and deleted these WIP stuff.
REMEMBER TO MAKE A BACKUP First of a Clean 2.45, SP Patch Fixed, your custom FH2 AND HERE'S THE EXAMPLE WHY YOU SHOULD KEEP A CLEAN BACKUP OF OLDER 2.40, MAKES MODDING EASIER.
ALL NCO RIFLES will be activated even on custom Maps. Even in Bootcamp_1 (Multiplayer only).
NO CLASSES ARE SHOWN IN SELECTION SCREEN
PICKUP KITS ARE NOT SHOWN INGAME
A: tmp.con not handling init.con content, i.e. you tried converting a 2.40 Custom Map to 2.45 which wasn't delivered a tmp.con, then you supposedly get empty selection screen or CTD before seeing the Map-start screen.
B: Map is supposed to be 2.45 standard, but your custom Classkits not showing up, nor your Pickupkits ingame. Make sure to use the classkits of init.con and place their lines to tmp.con as described above
(only 14!!!, not one single more, 7 per side!!!), same for the pickupkits you wanna see ingame.
Those you forgot, you won't see ingame.
In case of custom Classes and Kits:
All is corrected and you still experience this BUG, then you made a mess with conflicting Weapon-indexes
or using a non handled weapon (without AI code).
I made myself an Excel file handling all ingame Weapons indices and showing them correctly.
This is crucial if you wanna create custom-kits bug-free.
MAPDATA.py and old custom Maps:
You can try to create a mapdata.py the way described above and still it won't work flawless,
NOT ENABLING RIFLE NCO's nor other things written in the Mapdata.py. Why? Don't ask, I tried all.
Best is:
If the map lacks this file, that is no problem to run in 2.45 as some may think.
My old maps run fine and CTD free without, if delivered without originally, creating this file causes problems and seems to be CTD prone to the bone.
Not to mention it is best to use the original mapdata.py on their pre-defined Maps.
UPDATED
Knoch