General hints (FRED)

From FreeSpace Wiki
Revision as of 10:51, 25 October 2009 by TopAce (talk | contribs) (some cleanup, adding opening paragraph, one more hint)
Jump to: navigation, search

Here are some general FREDding hints that do not require separate articles to elaborate, from beginner level until intermediate.

  • Use the Y-axis (height) and rotate most of your ships on one or more of the axes to give a more realistic feeling.
  • Use the Selection Lock (Spacebar) if you have selected all the ships you want to move or rotate. This will make sure you do not select an unwanted craft by accident. Press Spacebar once more to disable Selection Lock.
  • If you want a directive to appear only after a specified event, use event chaining:
    • Collect all the triggering conditions in one event. Chain the next event (which is the actual directive) to the previous event with a delay of at least 1 second.
    • This will make it sure the event will not appear sooner than desired. This is especially useful if you want Command to order the desctruction/capture/inspection of a ship.
  • Use the designer's notes of the Mission Specs Editor (SHIFT-N) as a reminder for yourself. There are some things that you want to be in your mission only temporarily, for testing purposes such as enabling No Traitor if you want to test if a ship sends the right message if its hull dropos below 50%.
  • Using keyboard shortcuts makes editing more convenient.
  • If you do not want a ship to open fire, simply use the turret-lock-all SEXP instead of disarming all the turrets manually.
  • If you want to use a special, special-case support ship, you have to make changes in the ship tables. You cannot simply place a support ship and disallow all player orders.
  • Always remove player orders for ship classes other than fighters or bombers. By default, the player can give orders to transports and above. If you give the 'Attack my ship' order to a transport that is supposed to board and capture a ship, it will not follow its default orders until the player-given orders are accomplished.
  • If you do not want a ship destroyed, but you want to make its subsystems destroyable, use the ship-guardian SEXP.
  • Increasing/decreasing the skill level of single turrets also affects the given turret's rate of fire. It is advised to increase the level of sentry guns by at least one rank.
  • Pressing TAB while having multiple ships selected changes the central point of rotation. If you start rotating, that ship will be the center of the circle your ships will be rotated around. The same is true for moving, the selected 'central' ship will be moving with the cursor.
  • If you get lost on the grid, press SHIFT-Z. Or, zoom on any of the ships by selecting the fighter in the Selection Menu (H) and pressing ALT-Z.
  • Wingmen initial orders is limited, but using the add-goal SEXP removes this limitation.
  • Placing a waypoint into the center of a jump node enables you to measure distances between any ships and the jump node. The waypoint and the jump node must share the same coordinates. Technically, the engine measures the distance between the assigned ship(s) and the waypoint, but since the center of the node and the waypoint are at the same position, you can measure distance between ships and the jump node.
  • Colored text can be used in the Command briefing, but cannot be used in the debriefing.
  • An ideal mission length ranges between five and eleven minutes. It is not advised to make a mission longer, as FreeSpace players are not used to flying for more than ten minutes.
  • For better performance, use the wireframe view mode. The textured view mode eats up more memory and makes the mission editor run slower.
  • If you want a ship just to suddenly appear, use the No Warp Effect feature in the arrival cue section of the Ship Editor. If the departure cue has the No Warp Effect set, then the ship will suddenly disappear. This is useful for nebula missions. Beware of using the ship-vanish SEXP: ships that vanish do not count as "departed", so the "has-departed-delay <ship that vanishes using ship-vanish>" will not trigger.
  • Believe it or not, the EMP effect also works on AI-controlled ships. Bear this in mind while creating nebula missions.
  • Players usually start by increasing the throttle to maximum. Set the player's speed to 100% by default in the Initial Status options if it's likely that most players would start the mission by accelerating.
  • In case one or more ships in a wing departs without the departure cue becoming true, the wing will not be considered departed. This means if you order one (or all) ships from Beta wing to leave the area and there is an event which becomes true if Beta wing has departed, the event will become incomplete until you restart the mission.
  • The "Neutral" IFF is hostile to the player. If you want the "Hostile", "Neutral" and "Friendly" sides to attack each other, set the All teams at War option in the Mission Specs Editor.
  • You can manually set the player traitor but using the change-iff SEXP on the player's ship to make the player "Neutral" (FreeSpace Open introduced the "Traitor" IFF).
  • The Protect Ship option is not completely reliable. The AI may still attack those ships. Rather make that ship invulnerable. It looks daft, but this is the best solution to make the AI not lose the mission for the player by destroying any ships which are supposed captured or not destroyed. You can also use the change-iff to make the ship Friendly (as it was used in First Strike). Hostiles will still attack that ship, so make sure they ignore it.
  • Changing the order of events in FRED is not recommended. Such a move will confuse the game engine, and weird mission flaws will come up. Use a text editor instead for this purpose. You won't need to change the order of in-mission events anyway, except for chained events.

Using FRED with mods

  • Note that FRED2 Open uses the same mod usage as FS2 Open, that is,

-mod mod1,mod2,mediavps where <mod1> is the name of the mod being played, <mod2> is the name of the mod that the mod being played depends on, and <mediavps> is where the Media VP files are put. See the wiki instructions Getting Started > Installing mods for fs2_open > Alternative method / more info for complete details. Also, I've heard (and FRED2 Open says) that you should run with the -fredhtl option. So, say you were creating a mod for the FreeSpace Port (for a mission during the Great War) You'd use something like the following, depending on where you installed FSPort and the Media VPs: (note the quotes) "\<whatever dir Fred is in>\FRED2_build_date_whatever.exe" -mod fsport,mediavps -fredhtl This would allow you to use FS1 weapons, ships, etc. Note you might not need mediavps if you use the mod.ini options mentioned in the installing mods wiki mentioned above, or if you weren't creating a mission for FS Open.

See also

Typical FREDding mistakes