BasicsThere are these files in
Program Files/Microsoft Games/Mechwarrior Mercenaries/RESOURCE/Missions and
UserMissions called .nfm files. There is a separate .nfm file for every map you have installed, and they contain game settings and parameters for different games that are used on that map
if you're hosting. If you're not running a dedicated server or hosting, then they are completely useless and serve no function whatsoever, but you've still got to have them, and when they get screwed up, it will completely hork your game.
The game ships with an .nfm editor program in your Mercs directory, but you should
never, ever use this. The editor doesn't support a lot of the newer gametypes and changes that the user community has made to the game, and opening an .nfm with it will completely screw up those changes. Instead, .nfm files should only be edited with a basic text editor like Notepad.
The contents of an .nfm file will have a lot of entries that look like this:
CODE
Banzai={
[server]
ruleset=$(StockTeamBattle)
name=Ronin
teamAllowed=1
teamcount=2
scenariotext=resource\missions\tbat.txt
respawnLimit=0
isNight=0
weather=1
radarmode=0
onlyStockMech=0
gameLength=30
team_0={
[teamdata]
Skin=&
}
team_1={
[teamdata]
Skin=d
}
}
Makes your head hurt, doesn't it? OK, let me explain. Let's say I pulled this entry out of the .nfm file for the map
Factory. (so the filename would be Factory.nfm in my Missions directory) If I'm hosting, and choose Team Battle as the gametype, then a list of maps will come up. If I scroll down that list and select
Factory - Ronin from that list (see where it says 'Name=Ronin' above?) then in effect, what I'm doing is choosing Factory as the map, and this set of restrictions to use with it.
Here's what each entry means:
ruleset=$(StockTeamBattle)
(this sets the scoring system for the drop)name=Ronin
(name of the ruleset)teamAllowed=1
(are teams allowed? 0 = No. 1 = Yes. So in this one, yes - teams are allowed)teamcount=2
(how many teams are allowed? 2)scenariotext=resource\missions\tbat.txt
(this is the text the server will show under the map tab in the lobby)respawnLimit=0
(is there a limit to respawns? No.)isNight=0
(is it night? No.)weather=1
(Is the weather turned on? Yes.)radarmode=0
(radar is normal)onlyStockMech=0
(Are stock 'Mechs required? No.)gameLength=30
(How long is the drop? 30 minutes)There are quite a few other things you can specify with .nfm files, like visibility (clear, light fog, heavy fog, etc.) and some other things, but that's enough to give you a basic idea. Anything that doesn't have an entry will be at the map's default setting. So in this example, since there isn't an entry for visibility, it will automatically be set to the default for that map.
Now, remember up there where we said teams were allowed on this map? Well, immediately below that section in our .nfm entry we can specify different settings for each team:
team_0={
(here's the info on the first team - team_0 = Team 1 in the game)[teamdata]
Skin=&
(team 1 will be wearing the skin that corresponds to this symbol)}
team_1={
(here's the info on the second team)[teamdata]
Skin=d
(team 2 will be wearing the skin that corresponds to this symbol)}
(this bracket closes the data entry for team 2)}
(and this bracket closes the data entry for the entire Ronin ruleset)In this example, the only parameter I've specified for the two teams is different skins, but you can use the teamdata section to impose player limits, different tonnage or 'Mech limits for each team, all sorts of stuff.
A typical .nfm file will have about a dozen different entries that look pretty similar to this one. All will have a different ruleset name (this one is named Ronin, because it's the one we run on our server most of the time) and all will correspond to the specific map that this .nfm file is for.