[karajorma]

I just played AoA on 3.6.12 final and I noticed that the damage I did to the Duke's engines as it headed to the node was magically repaired in the one immediately afterwards. But I know that mission has a bunch of persistent variables named after major subsystems cause I know it crashed 3.6.13 Ant 8 builds until I fixed a bug with persistent variables.

Are those variables meant to do anything still? If so I might have to start bug hunting to see what's going on there.

[General Battuta]

Let me take a peek.

[General Battuta]

It appears the variables are recorded, but never applied at the start of the next mission. 

This might be worth touching up just for the sake of polish, but to be honest I never want to roll out another AoA update again. In the meantime I suspect you're in the clear codewise.

[Fury]

This might be worth touching up just for the sake of polish, but to be honest I never want to roll out another AoA update again. In the meantime I suspect you're in the clear codewise.

Wat? Conveniently missions are located in the Core package that is little over 200 KB large, so hardly a problem buddy. Besides, Core will have to be updated anyway at some point for some tabling improvements, such as better weapon loadout description for Balor.

And when someone gets to optimize new-gen Terran ships, Visuals1 has to be updated. Sorry, but there should be updates to AoA as long as BP is supported by its staff.

[General Battuta]

Yeah I guess you're right.

[Androgeos Exeunt]

Once BP is completely done, we'll end up in the same position as FSPort and TBP. Much of what we have to do then is to maintain the mod's compatibility and continue fixing any bugs that may surface each time its compatibility is updated.