It's committed and works fine on my machine.
As for the flag - keep in mind that since +Flags: is a bitfield, 128 is simply ORed to the existing flag. In practical terms this simply means add 128. The flag value doesn't necessarily need to
equal 128.
Originally posted by EdrickV
Hmm, another thing I just thought of, does the code work for ships that haven't entered the mission yet? (Normally you have to do beam-free-all once the ship has entered.) And does it work for ships in the second/third/etc. wave, not just the first? (This isn't a big thing for cap ships, but for fighters with beams it could make a difference.)
The code is in the mission parsing routine, which means that upon loading the mission, the parser sets the default status of every ship to beam-free-all. This should work with ships that haven't arrived yet as well as ships that start out in the mission.
As for whether it works for waves - I honestly don't know. I can think of reasons why it could go either way. If each successive wave of ships are simply duplicate instances of the original ships, it ought to work, because it will duplicate the beam-free-all flag along with everything else. But this may not be the case. The only way to know for sure is to load it up and test it.
I'll generously leave this task to someone else, as I'll have a boatload of exam work over the next few days.