@Andrez map .cfgs are not really meant to be easily readable by humans. /config/default_map_settings.cfg has all the formatting/comments one would need to understand whats going on in them. As unimportant as the space savings sounds it actually makes quite a big difference when we're talking sendmap/getmap's, especially from 56k internet connections. In theory the cleaned example output .cfg would transfer twice as fast as the input .cfg over the network. Not to mention the less data the .cfg reader has to go through the better.
The best part about it IMO is that it removes the junk lines that tend to accumulate at the end of map .cfgs over time. These lines can cause lots of issues in a map .cfg especially if you're trying to modify it. (adding/removing mapmodels/textures/etc.) I found this out the hard way when modifying an old copy of ac_alcove a week or so ago. Random edits to the file that should have had no effect on the map would screw up a few textures on the map. After acquiring a clean copy of the .cfg all problems went away; modifying the .cfg worked fine and didn't negatively effect the map at random.
Don't gotta use it guys, its just something that I find quite useful so I thought I would share with everyone in hopes that someone else will too.
The best part about it IMO is that it removes the junk lines that tend to accumulate at the end of map .cfgs over time. These lines can cause lots of issues in a map .cfg especially if you're trying to modify it. (adding/removing mapmodels/textures/etc.) I found this out the hard way when modifying an old copy of ac_alcove a week or so ago. Random edits to the file that should have had no effect on the map would screw up a few textures on the map. After acquiring a clean copy of the .cfg all problems went away; modifying the .cfg worked fine and didn't negatively effect the map at random.
Don't gotta use it guys, its just something that I find quite useful so I thought I would share with everyone in hopes that someone else will too.