Typical FREDding mistakes
- (Written by: Karajorma. Taken from the original source with the following alterations: spellchecking, Wikifying)
In the last few months of working on the FRED Academy I've tested a whole load of missions by very new FREDders and I've noticed that often it's the same mistakes that come up time and time again. Rather than continually repeating myself I figured it might be an idea to have a little list of some of the more common FREDding mistakes I've seen.
13) Poor spelling and grammar
I've not been that hard on this one while playtesting because
a) I'm not that observant and
b) Spellchecking is something I feel should be done last of all
c) I understand that many people here are not native English speakers.
That doesn't mean that you shouldn't try to correct those things as you go along. When a mission is complete, this leaps from being a low-grade annoyance to a very big one. Completed missions should never have ships with obvious spelling errors in them. If English isn't your first language, ask someone for some help.
12) No use of the Y-axis
Ever seen Star Trek II : Wrath of Khan? Ever got the feeling that the captains of all the ships in a mission haven't? They're all arranged on the XZ plane. No ships diving in from above or nipping in from below. While it's believable that a small convoy of ships might arrange themselves this way so as to spread their flak above and below them effectively it's harder to believe that enemy ships jumping in would somehow know what plane they were on and leap in on it.
11) Poorly chained directives
This is quite a common one. If you forget to chain your Return to Base Objective it will appear at the start of the mission. FreeSpace is clever enough to avoid putting up a directive to kill Cancer wing if they aren't present yet, but it doesn't do that for every directive. Unless you're sure you don't need to you'll have to chain the directive to the event which triggers it.
10) Magically completed mission objectives
A close relative of the above error. Quite often a FREDder will put in a mission objective but forget to actually put in the trigger because he means to go back and put it in later. Nothing screams out "I haven't tested this mission" quite as loud as this because unlike the above one this one has music to draw the playtester to the fact that you've screwed up.
9) No use of the escort list
All major capships and anything which is mission critical should appear on the escort list. Making a ship appear there is very simple. Just go to the ships editor>>misc. Tick the escort ship box and assign a priority. All caps should be given a priority. Don't make the mistake of only giving them to the three most important ships in the game. If one of them is blown up the next most important ship should then appear on the list.
8) Poorly chosen event and message names
This one won't affect people playing the mission, but it's just plain common sense. While you might think you'll remember the arcane naming system you've chosen to use, you almost certainly won't if something makes you come back to the mission in a years time to fix a bug. In addition to making your life easier, it makes life easier for playtesters as they can give you the name of a faulty event/message for you to fix. Finally when you look over your mission and see an is-event-true-delay SEXP how on Earth can you tell what other event it refers to if all of them are called "Event name"?
7) Only one RTB directive
Some missions only need to use Return to Base Directive. What some FREDders like to do is have an event that gathers up all the possible events that can end the mission and chain the RTB to that. However, amongst new FREDders only one RTB is generally more indicative of a poorly thought out mission. Basically the designer thinks "Hmmm, Alpha will fight this cruiser, kill the fighters and then escape with the convoy". No thought is given to what happens if something goes wrong. When this happens the mission basically continues forever because no thought was given to this possibility.
6) The everlasting mission
A more insidious relative of the mission with only one RTB is the everlasting mission. Unlike the previous one there are RTBs in the mission but the player can do something that causes it to never appear (for instance disabling the wrong ship in the final FS2 mission can prevent Capella from going nova). Unlike the above error this isn't a newbie mistake as quite often even the professionals have failed to think of something the player might try.
It is seen fairly commonly in newbie missions though so I mentioned it here. As a mission designer you must actively think of ways that a player could screw up your mission and prevent them. If an enemy ship must survive the mission you must have a plan for what to do should the player disable it.
5) Only one debriefing
A close relative of the the only 1 RTB error is the only one debriefing error. Basically the same logic is at work here and the mission only has a debriefing for a successfully completed mission. If anything else happens you'll only see "No debriefing for mission: xxxx".
4) Odd naming conventions
FreeSpace has certain naming conventions that should be used in any mission set in the FS2 universe unless you have a damn good reason for changing it. GTVA wings are always named after letters of the Greek alphabet. Enemy fighter wings are named after signs of the zodiac. Although there is more leeway in the names of capships expecting anyone to take the GTD Suck My Balls seriously is frowned upon. Worse than poorly thought out names is the appearance of GTC Fenris 37 as this shows that you've put no thought into the names of your ships. All capships must have a unique name. You might be able to get away with giving a Poseidon or Isis a number but that is less forgivable in a Triton or Argo.
3) No delay between waves
Even in the most intense of battle there should be a few seconds delay between the death of the last ship in one wave and the next wave arriving. Otherwise it looks like the ships were lurking in subspace waiting for the death of their teammates. If you really have to avoid giving the player a breather for some reason you should still use a delay but increase the threshold for the wave so that the player is too busy with the current wave to notice the appearance of the next one.
2) Poorly thought out team loadouts
This one is a biggie. The biggest mistake is the use of the D variant weapons in singleplayer. These weapons are for use in multiplayer and thus are completely useless in the singleplayer game.
The other big mistake is having too few or too many weapons available. What's the point in 700 Helios bombs available if there are no bombers in the mission? Hell what's the point in having 700 Helios bombs available period. Similarly there's no point in making Tempests available if you only give out 10 of them.
A minor mistake is having a loadout consisting only of 5 Myrmidons when everyone is already in Myrmidons. Why bother putting anything in the ship loadout in that case?
(The last two will become somewhat moot once the SCP introduce a resource tracking element to campaigns but if you're not using that they are still worth mentioning).
1) And the biggest/most common mistake of all is.....
No AWOL Debriefing*
This is the debriefing that appears if you leave the battle when you weren't told to do so. A lot of newbies think that this one is added automatically so they don't put it in. But if you think about it, how does FS2 know whether you were supposed to leave them mission or not? A good AWOL debriefing should check if any of the conditions allowing you to leave have come true. In addition the other debriefing sections should check and *not* be played if the AWOL one was (Why would Command applaud you for protecting a ship if they are about to take you out and shoot you!) Basically this is an offshoot of the only one debriefing error but it's so common even in people who've got several debriefing stages that it was worthy of special mention.