There shouldn't be any complaints about the missions being random enough.
You didn't need to separate the Allied and Axis files into separate folders. The Red and Blue designations in the file name are what determines if a mission is an Axis or Allied mission. The player then has the option to use the button at the top of the QMB to switch between them without having to change map folders.
By using a map name that does not correspond to a .mis file map name certain users will get gibberish in their map area, especially the Russian players.
Smolensk_Axis_AviarBlueScramble001 - this is one of your template filenames
Smolensk_Axis_Aviar - This shows up as the map name in the QMB
(This should really match the loading name in the .mis file so that all players will see the name in their own language correctly since the QMB has been set up to automatically translate the folder names that match a current stock map .mis file name.)
Blue - This determines what mission templates will be used when you switch between Allies and Axis using the black button at the top of the main page of the QMB.
Red - Allies
Blue - Axis
Scramble - Mission Type
NoneA Template - Target: None | Pos.
+ ( Advantage template where the player is expecting to be behind the enemy)
NoneD Template - Target: None | Pos.
- (Disadvantage template where the player is expecting to be in front of the enemy)
NoneN Template - Target: None | Pos.
= (Neither the player or opponent has the advantage and the player is expecting it to generate a head on pass.)
Armor Template - Target: Armor (Player will be expecting to attack Tanks)
Bridge Template - Target: Bridge (Player will be expecting to attack a Bridge)
Airbase Template - Target: Airbase (Player will be expecting to attack an Airbase, At this time an aircraft carrier is also considered an Airbase)
Scramble Template - Target: Scramble (Player will be expecting to be taking off while under attack.)
001 - This is the last part of the file name and it is used so that you can create multiple missions templates of the same type to add the illusion of randomness. There are no set limitations to naming this part of the filename and it can be randomized as the template maker sees fit so that they can create more than one mission of the same type. This variability in naming also allows several users to create templates for the same map and it should limit the possibility of their QMB templates overwriting someone else's existing template. By using my username as part of the filename in this area for the QMB templates I created it makes it less likely that anyone can "accidentally" overwrite them with new files.
I haven't had a chance to fly them but I will soon.
Wheels