Is it the sort of thing that could be done with a batch "find>replace"?
Well I did something
a lot simpler:
Instead of swapping out the BP AI classes with "Find > Replace" in
every mission file, I simply renamed classes already tabled in the default BP2-AIs, and dropped them into %DIRECTORY%/data/tables/ai.tbl:
- None
- Coward
- BP2-Lieutenant --> Lieutenant
- BP2-Captain --> Captain
- BP2-Major --> Major
- BP2-Colonel --> Colonel
- BP2-General --> General
- BALLS OF STEELE --> Ace
Nice. All of them are now default FS1/FS2 classes except for Ace. Which I can manually edit in the mission file. We can now ship the campaign, right?
HOLD THE PHONE. Now comes the issue of rebalancing the missions. Fury AI is such a powerful dynamic,
it changes things. (Like, imagine if you suddenly turned on your VCR—because people still totally have those now right?—and watched
Big Trouble in Little China, and it was different because Jack Burton didn't "NO U" the knife in time, or Lo Pan wasn't able to survive the truck crash because he ran out of magic, or Miao Yin was able to karate chop the Lords of Death and everyone sat and drank and partied for 90 minutes on screen instead... it's the same concept. Insert favorite action movie here.)
Remember, I
want things to be more intense. But the initial issues I'm dealing with:
- Your wingmen getting all the kills? I don't think so.
- Escort missions where the cargo go kablooey, because wing after wing of shivans. You know the one I'm talking about.
- Training missions where the instructor is so smart and overpowered, he destroys a drone instead of injuring it and fails you for not following instructions.
- Long-ass missions where you just end up defending yourself after yer winkmen get kilt
Oh. Did I mention that there's
no check for cheating in the most recent iteration of FSO? That's right. I don't know how, but you can cheat your way through a campaign. Any campaign. Any mod. Just type
www.freespace2.com, slap BFReds (or equivalent) on your puny little interceptor, and send a beam straight through the spine of a capship—not even kidding. (I'm going to add an event called
"PUMPKINEATER --> while --> player-is-cheating" to check for cheating and set conditions
"and --> is-event-incomplete" for every mission in order to advance through a campaign, in my FSO campaign. Possibly also send a message from command about what a loser the cheater is.)
By the way: I'm also
working on a combat training mission where you learn the basics of glide, reverse thrust, reverse afterburn, and strafe. That's some delay but it's gonna look snazzy.