mission.lvl and map.lvl files work differently. The map files such as hoth.lvl lists everything on the map, and where it is to be placed, in order with starting with the prop_ to show its type, then listing its name as a prop and its face(how it appears) and its locations then ends in prop0.
The map files are referenced in a generic, prescan before loading the map, telling spawn points, building how they all should look and placing them where they are supposed to be and sometimes more info like damage specials and amount of vehicle spawns.
The mission file on the other hand lists all the the variable types in order for everything in the game all at the top of the file , as if to list them across the top of a page then the actual # or variable itself is listed below in hex, someone (like myself) needs to go into hex , be in hex edit mode in mission.lvl file and match the things listed in the beggining in order with its value listed below it , a snippet from the mission.lvl is below:
all_fly_xwing,all_fly_ywing,all_inf_basicurban,all _inf_lukeskywalker,all_inf_smuggler,PowerupItem,En tityMine,Aimer,Obstacle,SetSpawnDelay.
after these is a series of gibberish which i have determined is the hexidecmial equal of binary digits meaning in example if say 2 hex #s over we'll be altering the information (variable ) for all_fly_ywing.
More to come...but in general mission.lvl is the main decision maker for stats on everything on ALL maps.