Just reserving a value in the SetOptions string; the maps' race-swap triggers expect to see either 0 (for no change) or 1/2/3 (for terran/zerg/protoss) on word 16, but the generator logic isn't ready yet, so this will allow that work to be merged and applied without worrying about potential conflicts.
How was this tested?
Compiled the maps with race-swap triggers active
Loaded a map that was race-swappable (Smash and Grab); verified that it loaded and ran correctly with a 0 in the race override slot
Loaded a map that was NOT race-swappable yet (Zero Hour); verified that it loaded and ran correctly ie. having a value in the slot didn't cause issues
Did /download_data to get the version of the maps without race-swap triggers whatsoever; loaded Smash and Grab again, verified that it ran correctly ie. no weird behavior as a result of an extra character in the options string
TLDR having the 0 doesn't break maps that aren't set up to read the value, and correctly produces default behavior on maps that ARE set up to read it
What is this fixing or adding?
Just reserving a value in the SetOptions string; the maps' race-swap triggers expect to see either 0 (for no change) or 1/2/3 (for terran/zerg/protoss) on word 16, but the generator logic isn't ready yet, so this will allow that work to be merged and applied without worrying about potential conflicts.
How was this tested?
TLDR having the 0 doesn't break maps that aren't set up to read the value, and correctly produces default behavior on maps that ARE set up to read it