Save TNDL STNs and TNDL Members inside of templates

[Tnamrod]

Currently the TNDL STN and TNDL members (outside of the flight itself, if multiple flights exist inside of a static template) aren't saved within the template, this sucks because it makes it harder for mission creators to easily create a standardized set of STNs for flights between missions outside of manually setting the STNs between every AC which can be time consuming and tedious.
Sure you can use the ones generated by the ME and they do 'work' but the only way to know another flights STN is to have them already in your jet as members or have the other flight read them out to you which can clog up the radio. So it's either use the generated ones or have the mission creator spend time before the mission to go through every flight and set the STN which can take a while for larger squadrons with 30+ players per mission.

I think this would be an overall QoL update for squadron mission creators that don't give access to the full .miz to Flight Leads that create templates to send over to the MC for importing into the real .miz.

[SDsc0rch]

wow ---- great idea

i second this, ED