Goonhub
07-26-2015, 06:11 AM
It's 100% a maintainer problem.
For every map you add, any time anyone makes a change that requires adding/removing something from a map, or rejiggering how things work, that's an extra map they have to worry about debugging and refining.
On top of that, due to how byond saves map files, any time anyone tries to make a change to the map and push it to the versioning software, it conflicts with any existing attempts to do that, so this just compounds that. I know there's some recently made mapmerge utilities that partially fix this to only conflict on the atom level, but DM still has some issues with versioning software in the compiled output DMMs.
About the best you could do is split out every zlevel into their own DMM file, and write/use a dynamic map loader that loaded them all in peacemeal on roundstart. That way you'd only have to change a single map file with a single zlevel, instead of a single map file with multiple zlevels.
For every map you add, any time anyone makes a change that requires adding/removing something from a map, or rejiggering how things work, that's an extra map they have to worry about debugging and refining.
On top of that, due to how byond saves map files, any time anyone tries to make a change to the map and push it to the versioning software, it conflicts with any existing attempts to do that, so this just compounds that. I know there's some recently made mapmerge utilities that partially fix this to only conflict on the atom level, but DM still has some issues with versioning software in the compiled output DMMs.
About the best you could do is split out every zlevel into their own DMM file, and write/use a dynamic map loader that loaded them all in peacemeal on roundstart. That way you'd only have to change a single map file with a single zlevel, instead of a single map file with multiple zlevels.