Hosted Projects - Standalone > FRED Academy (Diaspora)

[WIP] Diaspora_FA-C01M02A.fs2

<< < (2/3) > >>

Yep, I haven't fleshed out the possible failure scenarios yet, but taking out Intersun is definitely one of them.  I was planning to add messaging to avoid firing on it unless directed to do so.

On the container count thing I wasn't sure on the right mix of reality versus fun.  The first mission you have to scan 20 ships to determine the cargo.  I didn't know if wanted to have the very next mission repeat that type of process?  What do you think? Better to leave the count unknown?

On the order of events regarding taking out the ftl then clearing?  I was envisioning a slow OJ Simpson type chase through the debris field with the cruise ship dragging you near the traps.

Monday update.  I think it's pretty clean at this point, just needs more play testing for possible holes.

Cleaned up Briefing(s).
Added failure scenarios.
Added additional dialog.
Tightened up the timing.
Added some additional warheads to intercept.
Fixed a few mission breaking holes.
Adopted Osirus as Battlestar name.

Still Needs:
More play testing
Adoption of common background/planet bitmap.
Debriefing still sounds a bit listy.

In addition to some minor tweaks I'm going to try and create a name plate for the battlestar.  I suck at all things art related so this may take a while.

If you've playtested 3 other missions, you can ask for me to playtest. :)

Loading this mission keeps crashing FS2 for me (exit state of -805306369) immediately upon clicking "commit" during the briefing.  I took a crack at looking for anything in the setup events, but I didn't find anything yet. (still not sure what that was about, but it seems to have fixed itself)  The few things I can think of changing from loading the mission in FRED...

Using either the "when-argument" or "every-time-argument" SEXP's for redundant events (like how you've booby-trapped some of the containers) makes it easier to work with them.  You could also use those with "random-multiple-of" in order to make it so the booby-trapped containers are chosen at random at the start of the mission (that's actually how I've set up mine).  For the landing event, I'd recommend using two instances of "dist-ship-subsystem" (the "landingstrip" subsystems are dead center of each pod) instead of "is-in-box" since you won't need to the battlestar to be in a specific location.  And a little more variety in the positions and types of cargo containers wouldn't hurt!  :p

After playing it, the debris field feels empty: I'd bump the number of objects up a bunch.  I noticed a few typos in the messages, but that's not a huge deal.  This actually had a really good feel to it, but might be a bit short.

Thanks for the feedback.

I like the idea of randomizing the containers so I'll look into that.

For the landing event, I just used the same technique presented in the walkthrough.  It's not really position dependent as the coordinate system is local to the battlestar.

Roger on the container types.

As for the debris field I think it's already at max number of pieces.  Sometimes it does feel empty and other times there are lots of large pieces flying about.  I could tighten up the field some to make if feel more full.

Do you remember what your playtime was?  I was actually shortening this one up on purpose.  I had a few runs of the other posted missions and they are running 10+ minutes so I thought I would keep this one relatively short.  There's also a 30% chance for you to fail near the end of the mission and if it were long you would dread having to replay to that point.

TO Kara:

I've played some of the others but haven't posted much feedback to this point.  Also, I'm not sure I'm ready for a profession beat down just yet ;)


[0] Message Index

[#] Next page

[*] Previous page

Go to full version