Modding, Mission Design, and Coding > FRED Academy

[FA] C3 M14 Chrisatsilph

<< < (2/3) > >>

Mobius:
Ok, I'm here...sooner than expected.  :)

The mission, overall, wasn't bad...I was a bit ":confused:" about the alternative ending...here's a list of what may be improved:

Spellings/Names:

- Signiture ---> Signature;

- Anniliated ---> Annihilated;

- Long ranged ---> Long range;

- shivan ---> Shivan;

- A installation/invasion fleet ---> An installation/invasion fleet;

- Goodluck ---> Good luck;

- Nehkbet ---> Nekhbet;

- The freighter "Triton" should have an unique name;

- The NTF installation "Installation" should have an unique name as well;

(there are other misspellings in the mission)


Other things:

- Alpha 1's initial speed is 0. IMO it should be 33/100. FRED ---> Editors ---> Ships ---> Initial Status ---> Velocity;

- There's no starfield so I suggest using it. FRED ---> Editors ---> Background ---> Skybox Model ---> write "starfield.pof" (without the quotes);

- If the Meson bomb's hull integrity reaches 0 the bombs enters a prolonged status of imminent explosion. Check the bomb's hitpoints in FRED ---> Editors ---> Ships ---> Special Hitpoints;

- The NTD Vortex is too far from the main area, when I was told to scan it I was about 14 clicks away from it;

- There's no AWOL debriefing. You circumvented the problem by disabling Alpha 1's subspace drive but learning how to handle AWOL debriefings really helps;

- In the briefing there are many, short stages. IMO it'd be better to have less stages with more text. This is not a real problem, anyway, so you're free to exclude this;

- Cheat triggered by pressing Q... well, why don't you use another letter or better, a series of letters? I triggered the cheat even if I didn't want to - the problem is that Q balances shields and even if my Pegasus didn't have shields I pressed Q because I usually do it. I suggest using a word to trigger the cheat, use:

Example:

and-in-sequence
  key-pressed
   W
  key-pressed
   O
  key-pressed
   R
  key-pressed
   D


...and then write the word that triggers the cheat at the end of your debriefing;

- The Colossus collides with the Aquitaine upon arrival;

- No RTB directive if I trigger the alternate ending;

- Even if I trigger the cheat there's a message telling me to scan the Vortex even if the destroyer isn't in the area of operations;



Other than these, few nitpicks the mission you designed wasn't bad. Keep up the good work! :)

Chrisatsilph:
Spellings/Names:

- Signiture ---> Signature;

- Anniliated ---> Annihilated;

- Long ranged ---> Long range;

- shivan ---> Shivan;

- A installation/invasion fleet ---> An installation/invasion fleet;

- Goodluck ---> Good luck;

- Nehkbet ---> Nekhbet;

- The freighter "Triton" should have an unique name;

- The NTF installation "Installation" should have an unique name as well;

(there are other misspellings in the mission)

Fixing :)


Other things:

- Alpha 1's initial speed is 0. IMO it should be 33/100. FRED ---> Editors ---> Ships ---> Initial Status ---> Velocity;

Thankyou for pointing this out, I will add it in shortly :)

- There's no starfield so I suggest using it. FRED ---> Editors ---> Background ---> Skybox Model ---> write "starfield.pof" (without the quotes);

I thought the starfields were default, Ill fix it up.

- If the Meson bomb's hull integrity reaches 0 the bombs enters a prolonged status of imminent explosion. Check the bomb's hitpoints in FRED ---> Editors ---> Ships ---> Special Hitpoints;

As I went though the mission, I realised this and couldnt find a way to make it 'blow up' Ill try that method

- The NTD Vortex is too far from the main area, when I was told to scan it I was about 14 clicks away from it;

I made the NTD Vortex that far away because some people will approach the ships that warp in, since when it appears it says unscanned in the HUD, players might scan it instantly thinking it might be a bonus objective and might interfere with te secondary objectives.

- There's no AWOL debriefing. You circumvented the problem by disabling Alpha 1's subspace drive but learning how to handle AWOL debriefings really helps;

True, might add it in :)

- In the briefing there are many, short stages. IMO it'd be better to have less stages with more text. This is not a real problem, anyway, so you're free to exclude this;

I like short :)

- Cheat triggered by pressing Q... well, why don't you use another letter or better, a series of letters? I triggered the cheat even if I didn't want to - the problem is that Q balances shields and even if my Pegasus didn't have shields I pressed Q because I usually do it. I suggest using a word to trigger the cheat, use:

Example:

and-in-sequence
  key-pressed
   W
  key-pressed
   O
  key-pressed
   R
  key-pressed
   D


...and then write the word that triggers the cheat at the end of your debriefing;

Thankyou for this, I persumed that you could only press 1 letter for the SEXP, not a word, Ill add it in as soon as possible.

- The Colossus collides with the Aquitaine upon arrival;

Didnt notice it, I was too busy admiring the beam fire :)

- No RTB directive if I trigger the alternate ending;

As I was writing the first post, I relised I should add one in and I did, I decided I will release it when some feedback comes though and I can make more changes.

- Even if I trigger the cheat there's a message telling me to scan the Vortex even if the destroyer isn't in the area of operations;

Any ideas to avoid this?

dragonsniper:

--- Quote from: Chrisatsilph on January 14, 2009, 05:22:02 pm ---Any ideas to avoid this?

--- End quote ---
I'll take a quick look.

SypheDMar:
The key isn't mapped to key. It's mapped to the shield button. In my case, it's 5. I couldn't tell if I completed the mission without using the cheat at all, since I saw the Colossus at the end.

Mobius:
What happened to my tag in your post? :(


--- Quote from: Chrisatsilph on January 14, 2009, 05:22:02 pm ---- The NTD Vortex is too far from the main area, when I was told to scan it I was about 14 clicks away from it;

I made the NTD Vortex that far away because some people will approach the ships that warp in, since when it appears it says unscanned in the HUD, players might scan it instantly thinking it might be a bonus objective and might interfere with te secondary objectives.

--- End quote ---

I see. You could still reduce the distance and use the Y axis. :)


--- Quote from: Chrisatsilph on January 14, 2009, 05:22:02 pm ---- Even if I trigger the cheat there's a message telling me to scan the Vortex even if the destroyer isn't in the area of operations;

Any ideas to avoid this?

--- End quote ---

I think the message shouldn't appear if the cheat is triggered. The cheat basically turns the mission into some sort of BoE so it'd be better to have a new set of messages for that evenience.


Another thing I'm now thinking about: speed. Warships are immobile and strangely static, you could set a few waypoint paths around the installation. Be careful or the ships might collide! ;)


--- Quote from: SypheDMar on January 14, 2009, 05:29:14 pm ---The key isn't mapped to key. It's mapped to the shield button. In my case, it's 5. I couldn't tell if I completed the mission without using the cheat at all, since I saw the Colossus at the end.

--- End quote ---

Interesting...I'm afraid, however, that most players use Q to balance shields. People might even press Q by mistake in an attempt to target a ship from the escort list and/or engage the afterburners.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version