FreeSpace Wiki - User contributions [en]

FreeSpace 2 game information

2011-07-19T07:13:10Z

Shade: Reverted edits by Jamesbrown (Talk) to last revision by The E

Released: October, 1999 
Developed by: Volition Inc. 
Published by: Interplay 

No age restrictions

Sequel of the award-winning FreeSpace: The Great War

==Story==
Thirty-two years have passed since the end of the Great War, we are now in the year of 2367. Ten years after the destruction of the [[SD Lucifer]] in the [[Sol]] system, the Terran and Vasudan species forged a new alliance, called the [[Galactic Terran-Vasudan Alliance]]. The [[Reconstruction]] period began in the galaxy as both races prepare their civilisations for the return of the [[Shivans]].

Even though, not everything goes very well: Admiral Aken Bosch formed the [[Neo-Terra Front]], a true alliance of an ideal considered hostile by the [[Galactic Terran-Vasudan Alliance]]. Both sides have been at war with each other for eighteen months now. [[Deneb]], [[Alpha Centauri]] and [[Epsilon Pegasi]] are the focus points in this war. 
Admiral Bosch's rebellion seems to be winning.

==Features==
*Enhanced graphics
*A completely new and alien environment: The nebula fog
*Be assigned to up to six fighter squadrons, from the Vasudan 203rd Scorpions to the elite 70th Blue Lions!
*Fly for the SOC, [[Special Operations Command]].
*Over 20 weapons of mass destruction
*A thirty-mission single player campaign and even more multiplayer missions!
*Encounter deadly new capital ship weapons: the Flak guns and Beam cannons
*Attack up to 8 players via LAN or TCP/IP
*Over 70 new ships, ranging from Super Capital ships to stealth fighters
*FRED, the easy-to-use mission editor
*Reasonable moddability

==System requirements==
===Minimum===
*Pentium 200MHz
*Windows 95/98/NT with DirectX 6.0 or newer
*32 MBytes of RAM
*400 MB Hard Disk space
*8x CD-ROM
*DirectSound certified video card
*Hardware accelerated card

===Optimum===
*Pentium 266MHz
*64 MBytes RAM
*8 MBytes Video memory
*3D Sound card with EAX or A3D

==Reviews==
===Home of the Underdogs Description (By Karajorma)===
Undoubtedly one of the best 3D space combat games ever made, FreeSpace 2 by Volition is a superb space opera of epic proportions. The strong emphasis on plot development combined with spectacular graphics and story-based missions make FreeSpace 2 a worthy contender to Origin's more well-known Wing Commander games. In fact, in my humble opinion the fun factor of FreeSpace 2 far surpasses that of Prophecy Gold, the last Wing Commander game, by a considerable margin.
The game begins with an alliance of humans and alien Vasudans attempting to rebuild their armies 32 years after the end of 'The Great War,' the battles of which were the subject of FreeSpace. You play a member of the GTVA, a Human-Vasudan alliance which is fighting a group of human rebels who call themselves the NTF.

FreeSpace 2 improves upon the excellent FreeSpace in every respect. Pre-mission elements such as the briefing session and ship configuration are superbly presented, with a lot of details and options to choose from. Frequent cutscenes made with rendered graphics are captivating, especially because outstanding voice acting makes them as absorbing to watch as real-life actors in Origin's Wing Commander IV (the cutscenes, except for the endings, are unfortunately missing in this CD-rip, but fortunately they are not necessary to your knowledge of the plot, since you can tell how the storyline is unfolding during briefing and de-briefing scenes). The game's emphasis on the plot is not just window-dressing, either: as in Wing Commander, your choices as well as mission successes and failures determine how the plot will develop, and ultimately what ending you will see. Even during the missions themselves, your objectives may suddenly change when new backstory-related developments take place. Being able to think "at the seat of the pants" to quickly adapt to changing circumstances is the key to winning in FreeSpace 2.

In terms of gameplay, FreeSpace 2 is basically a 'bigger and better' FreeSpace. Capital ships now have awe-inspiring proportions and are able to fight each other. This makes for many a memorable scene when you are caught like a tiny fly in the middle of capital-ships-only combat with cannons and turrets and huge beam weapons that are wider than your spacecraft. The game universe is much larger than in FreeSpace. Volition also adds a lot of nice graphical details, such as the cool-looking (and appropriately opaque) nebula, on top of much prettier 3D graphics. There are many new ships in the game in addition to all the ships from FreeSpace, more varied and more powerful weapons, and more diverse missions. The strategic aspect has also been much improved: your success in some missions depend as much on your strategic choices as your joystick expertise. Should you send a couple of wingmen ahead to recon enemy ships, or have them protect vulnerable ships? Should you take out the enemy bombers first, or the agile fighters? In-game choices such as these can spell the difference between life and death.

In addition to the superb single-player campaign, FreeSpace 2 includes full multiplayer support: up to 12 players via LAN or the Internet (PXO and SquadWars.com), or head-to-head via modem. In any of these modes, you can choose to fly co-op, team-based, or free-for-all dogfight, with many different missions to choose from. And to add even more bang for the buck, the game includes FRED2, a full-featured editor that you can use to create your own missions and campaigns. With an epic-sized space operaic plot, gorgeous graphics, top-notch space combat action, optional missions and multiple endings, and virtually unlimited replayability, FreeSpace 2 is a must-have for all armchair space pilots... and a worthy entrant into our Hall of Belated Fame.

==Source Code==

Volition released the source code of FreeSpace 2 in 2002. For those interested, the original source can be downloaded [http://www.mediafire.com/download.php?mzgymmz5ynm here].

[[Category:The games]]

Category:Campaign Walkthroughs

2011-06-08T15:27:57Z

Shade: added category

List of campaign walkthroughs on the FreeSpace wiki.

[[Category:Campaigns and Missions]]

Template:Main nav

2011-06-08T15:17:32Z

Shade: Added walkthroughs link to nav bar

{| border=0 align=right cellpadding=4 cellspacing=0 width=20% style="margin: 0 0 1em 1em; background: #302020; border: 1px #AA2020 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #512020; 70%;"|''Retail FreeSpace''
|-
| [[Getting started|Introduction]]
|-
| [[Portal:FreeSpace 1|FreeSpace 1]]
|-
| [[Portal:FreeSpace 2|FreeSpace 2]]
|-
! style="color: white; height: 30px; background: #512020; 70%;"|''FreeSpace Source Code Project''
|-
| [[Getting Started (FreeSpace Open)|Getting Started]]
|-
| [[Installing Mods for FS2 Open|Mod installation instructions]]
|-
| [[SCP_Additions|List of added capabilities]]
|-
| [[Portal:Multiplayer|Multiplayer]]
|-
| [[Command-Line_Reference|Command-Line Reference]]
|-
| [[Development_Reference|Development Reference]]
|-
| [[Feature Requests|Feature Requests]]
|-
| [[Screenshots]]
|-
! style="color: white; height: 30px; background: #512020; 70%;"|''Modding FreeSpace''
|-
| [[Portal:Modding|Modding Portal]]
|-
| [[Mod Database]]
|-
| [[Portal:FRED|FRED]]
|-
| [[Campaign List|User-made Campaigns]]
|-
| [[User-made Ships|User-made Ships]]
|-
| [[Total conversions|Total Conversions]]
|-
! style="color: white; height: 30px; background: #512020; 70%;"|''FreeSpace Universe''
|-
| [[Portal:FreeSpace Universe|The Universe]]
|-
! style="color: white; height: 30px; background: #512020; 70%;"|''Other''
|-
| [[:Category:Campaign Walkthroughs|Campaign Walkthroughs]]
|-
| [[Various Terms|FreeSpace Jargon]]
|-
| [[FreeSpace Alpha]]
|-
| [[Freespace_Wiki:Community_Portal|FreeSpace Community]]
|-
| [[Getting FreeSpace]]
|-
| [[Guide to FS Open on Linux]]
|-
! style="color: white; height: 30px; background: #462424; 70%;"|Alternately, explore the '''FreeSpace''' universe through ''[[:Category:Main|categories]].''
|-
|}

<noinclude>[[Category:Templates|Main nav]]</noinclude>

Category:Campaign Walkthroughs

2011-06-08T15:10:54Z

Shade:

List of campaign walkthroughs on the FreeSpace wiki.

Ancient-Shivan War Campaign Walkthrough

2011-06-08T15:03:41Z

Shade: + walkthroughs category

==Act 1==
* [[Introduction (ASW)|Introduction]] (cutscene)
* [[A Legacy Begins]]
* [[The Sword of Damocles]]
* [[Roadblock]]
* [[The Battle of Aesdher]]
* [[Victory (ASW)|Victory]] (cutscene)
* [[A New Adversary]]
* [[Realm of the Guardians]]
* [[A bridge too far]]

[[Category:Ancient-Shivan_War]]
[[Category:Campaign Walkthroughs]]

Blue Planet: War in Heaven Campaign Walkthrough

2011-06-08T15:01:26Z

Shade: + walkthroughs category

{{BPArticle}}

* [[Artemis Station]]

==Act 1: Chrysalis==
* [[The Cost of War]]
* [[Collateral Damage]]
* [[Post Meridian]]
* [[Ken]]
* [[For the Wrong Reasons]]
* [[Darkest Hour]]
* [[My Brother, My Enemy]]

==Act 2: Apotheosis==
* [[The Intervention]]
* [[The Plunder]]
* [[Aristeia]]
* [[What Binds Us]]
* [[One Perfect Moment]]
* [[Deals in Shadows]]
* [[Pawns on a Board of Bone]]
* [[Delenda Est]]
* [[Sunglare]]

[[Category: Campaign Walkthroughs]]

Blue Planet: Age of Aquarius Campaign Walkthrough

2011-06-08T15:00:38Z

Shade: + walkthroughs category

* [[Departure]] (cutscene)
* '''A Blue Planet...With Vast Seas'''
** [[A Blue Planet...]]
** [[...With Vast Seas]]
* [[The Dragon Awakes]]
* [[Lucifer (BP)|Lucifer]] (cutscene)
* [[Journey of a Thousand Miles]]
* [[Journey of a Thousand Miles II]]
** [[Journey of a Thousand Miles III]]
* [[Wounded Prey]]
* [[Frankenstein's Monsters]]
* [[Finding Sanctuary]]
* [[Ceremony]]
* [[Forced Entry]]
* [[Curse of Prescience]]
* '''First Contact'''
** [[First Contact]]
** [[First Contact II]]
* [[Preserving the Balance]]
* [[Sacrifices]]
* [[The Great Preservers]]
* [[Keepers of Hell]]
* [[Fallen Angel]]
* [[Demons of the Past]]
* [[Find Your Way]]
* [[A Time for Heroes]]
* [[Universal Truth]]
* [[Journey's End]]

[[Category: Blue Planet]]
[[Category: Campaign Walkthroughs]]

Silent Threat: Reborn Campaign Walkthrough

2011-06-08T15:00:25Z

Shade: + walkthroughs category

*[[Silence All Voices (ST:R)|Silence All Voices]]
*[[More Than Meets the Eye]]
*[[Ghosts (ST:R)|Ghosts]]
*[[Field of Destruction (ST:R)|Field of Destruction]]
*[[Cloak and Dagger (ST:R)|Cloak and Dagger]]
*[[He Who Rides the Tiger]]
*[[The Wait (ST:R)|The Wait]]
*[[Hellfire (ST:R)|Hellfire]]
*[[The Return to Ross 128 (ST:R)|The Return to Ross 128]]
*[[The Last Hurrah]]
*[[Betrayed]]
*[[Exodus (ST:R)|Exodus]]
*[[Forced Hand]]
*[[Chasing Shadows]]
*[[Secrets Reborn]]
*[[Blood of the Innocents]]
*[[Abandon Hope]]
*[[Last Stand]]

[[Category:Silent Threat: Reborn]]
[[Category: Campaign Walkthroughs]]

Inferno: Release 1 Campaign Walkthrough

2011-06-08T15:00:11Z

Shade: + walkthroughs category

{{Inferno}}

==GTVA: Chapter 1==

* [[Brotherly feud]]
* [[One step at a time]]
* [[The great rebellion]]
* [[Old enemies]]
* [[El Diablo]]
* [[Showdown]]
* [[Needed Supplies]]
* [[Gateway]]
* [[Taking the Gate]]
* [[Fenced In]]
* [[The only possible outcome]]
* [[Intangible Factors]]
* [[Nemesis (INF)|Nemesis]]
* [[Gigas]]

[[Category: Inferno R1]]
[[Category: Campaign Walkthroughs]]

Derelict Campaign Walkthrough

2011-06-08T14:59:55Z

Shade: + walkthroughs category

{{Derelict}}

==Act 1==

* [[Welcome to the Boonies]]
* [[The Deep Patrol]]
* [[Marie Celeste]]
* [[Through the Looking Glass]]
* [[Last Leg]]
* [[Bait and Switch]]
* [[A Time for Penance]]
* [[The Horror in the Deep]]

{{stub}}

[[Category: Campaign Walkthroughs]]

FreeSpace 2 Campaign Walkthrough

2011-06-08T14:59:13Z

Shade: + walkthroughs category

==Act I==
*[[Surrender, Belisarius!]]
*[[The Place of Chariots]]
*[[The Romans Blunder]]
*[[A Lion at the Door]]
*[[Mystery of the Trinity]]
*[[The Great Hunt (FS2)|The Great Hunt]]
*[[Slaying Ravana]]
*[[The Sixth Wonder]]
*[[Into the Maelstrom]]
*[[Feint! Parry! Riposte!]]

==Act II==
*[[Battle of the Wilderness]]
*[[A Game of TAG]]
*[[Proving Grounds]]
*[[The King's Gambit]]
*[[The Sicilian Defense]]
*[[Endgame]]
*[[The Fog of War]]
*[[A Monster in the Mist]]
*[[Speaking in Tongues]]
*[[A Flaming Sword]]

==Act III==
*[[Bearbaiting]]
*[[High Noon]]
*[[Return to Babel]]
*[[Straight, No Chaser]]
*[[Argonautica]]
*[[Exodus (FS2)|Exodus]]
*[[Dunkerque]]
*[[Their Finest Hour]]
*[[Clash of the Titans II]]
*[[Apocalypse]]

==SOC Loop 1==
*[[Rebels & Renegades]]
*[[Love the Treason...]]
*[[...But Hate the Traitor]]

==SOC Loop 2==
*[[As Lightning Fall]]
*[[Into the Lion's Den]]
 
----
==FreeSpace 2 Demo==
*[[Crimson Sky]]
*[[Crisis in Capella]]

==FreeSpace 2 Colossus==
This limited single-CD version of FreeSpace 2 is included with some Logitech Force Feedback joysticks. It includes only Act 1 of the FreeSpace campaign (the training missions are present, but it does not include the SOC loop). FRED missions still work with it, but FreeSpace 2 Open does not. There are no printed manuals provided; all the material is found on the CD media.

==[[Operation Templar]]==
*Short and separate multiplayer co-op campaign included with FreeSpace 2
*Also available as an unbalanced, single player campaign with the GOTY version of FreeSpace 2

[[Category:Lists]]
[[Category:Main FreeSpace 2 Campaign]]
[[Category: Campaign Walkthroughs]]

Category:Campaign Walkthroughs

2011-06-08T14:58:32Z

Shade: New category

List of campaign walkthrough on the FreeSpace wiki.

FreeSpace 1 Campaign Walkthrough

2011-06-08T14:57:32Z

Shade: + walkthroughs category

===Act 1===

*[[Eve of Destruction]]
*[[The Field of Battle]]
*[[Small Deadly Space]]
*[[Avenging Angels]]
*[[Out of the Dark, Into the Night]]
*[[Paving the Way]]
*[[Pandora's Box (FS1)|Pandora's Box]]
*[[The Hammer and the Anvil]]
*[[The Darkness and the Light]]
*[[First Strike]]
 
----
===Act 2===

*[[The Aftermath]]
*[[The Big Bang]]
*[[La Ruota della Fortuna]]
*[[Where Eagles Dare]]
*[[Tenderizer]]
*[[Shell Game]]
*[[Enter the Dragon]]
*[[Playing Judas]]
*[[Evangelist]]
*[[Doomsday]]
 
----
===Act 3===

*[[Exodus (FS1)|Exodus]]
*[[Last Hope]]
*[[A Failure to Communicate]]
*[[Reaching the Zenith]]
*[[Running the Gauntlet]]
*[[Black Omega]]
*[[Clash of the Titans]]
*[[The Great Hunt]]
*[[Good Luck]]
 

[[Category:Lists]]
[[Category:Main FreeSpace 1 Campaign|*]]
[[Category: Campaign Walkthroughs]]

FreeSpace Wiki:Community Portal

2011-06-06T13:21:02Z

Shade: Reverted edits by Hey (Talk) to last revision by Snail

{| border=0 align=center cellpadding=4 cellspacing=0 width=95% style="margin: 0 0 1em 1em; background: #202020; border: 1px #AA2020 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #512020; 70%;"|<big>'''The FreeSpace Community Portal'''</big>
|}
 
{|border=0 align=right cellpadding=4 cellspacing=1 width=45% style="margin: 1 1 1em 1em; background: #301515; border: 1px #AA2020 solid; border-collapse: collapse; font-size: 95%;"
|-
! colspan=2 style="color: white; height: 30px; background: #512020; " width=95% | '''''Sites and Forums'''''
|-
! style="color: white; height: 30px; background: #202020; 70%;"|[http://www.hard-light.net Hard Light Productions]
| The largest of the FS-related forums on the net, and the site which hosts this wiki.
|-
! style="color: white; height: 30px; background: #202020; 70%;"| [http://www.sectorgame.com/f2s/ Freespace 2 Sector]
| Oldest remaining FS-related site and forum on the net.
|-
! style="color: white; height: 30px; background: #202020; 70%;"| [http://scp.indiegames.us/news.php Source Code Project]
| The FreeSpace 2 Source Code Project homepage. Mainly serves the developers of the FreeSpace Open.
|-
! style="color: white; height: 30px; background: #202020; 70%;"| [http://wiki.freespacegalaxy.de/doku.php FreeSpace Galaxy]
| This is another FreeSpace Wiki, written in German.
|-
! style="color: white; height: 30px; background: #202020; 70%;"| [http://freespacemods.net/news.php FreeSpaceMods]
| A site that has become the replacement of the Hades Combine. Provides Mods and Campaigns.
|-
|}

Welcome to the FreeSpace Community Portal. Through here, you can find links to the major FreeSpace-related sites and forums on the Web. If you have a site that deserves to be on here, go ahead and add it to the sidebar.

If you've come here looking to discuss wiki-related issues, you're also in luck. HLP has provided us with a [http://www.hard-light.net/forums/index.php/board,122.0.html forum] for the discussion of wiki matters, but if you don't want to register there for whatever reason, feel free to use the talk page for this portal.

==Volition Watch==
Volition Watch was once the FreeSpace community's hub, and several of its important articles are preserved in the wiki. Browse the [[VolitionWatch Articles List]].

''See also'' [[Fan sites]]

==Multiplayer Squadrons==
Since 2007, the FreeSpace multiplayer community is again going strong. View the [http://www.hard-light.net/forums/index.php/topic,49012.0.html Multiplayer Schedule] on Hard Light and browse the [[: Category: Multiplayer Squadrons|Multiplayer Squadrons category]].

Talk:Main Page

2011-04-12T12:20:07Z

Shade: Note on protection

==Categories==
Categories? Do you know how to make new categories? I thought I did, but it seems I did not. Is it possible to make categories at all? - [[User:TopAce|TopAce]] 23:51, 15 Nov 2005 (CET)

It's easy. You just need to add <nowiki>[[Category:Category name]]</nowiki> (without the nowiki tags, obviously) and then go to the Category:Category name page. The wiki will auto generate the basic page for you. [[User:Black Wolf|Black Wolf]] 11:53, 16 Nov 2005 (CET)

== Featured Article ==

Aren't there any other articles besides the one on Shivans? It kinda makes this place feel like it's dead.

:Sure there are lots of other articles than one on Shivans, and the article can be changed too, i just haven't really seen any propositions lately. - [[User:Wanderer|Wanderer]] 00:07, 7 April 2007 (CDT)

A big thanks to whoever made ASW the featured campaign of the moment! [[User:SpaceFreak|SpaceFreak]] 08:12, 15 January 2010 (UTC)

Just wondering - The Current Featured Article is about a Campaign ([[Terran-Vasudan War Project]]) that apparently is dead, seeing as I cannot find a single server that is currently hosting the files for download. Do we really want ot showcase a campaign for new players that they will be unable to play?--[[User:Krajerino|Krajerino]] 04:05, 22 June 2010 (UTC)

:Individual teams are supposed to take of their respective web pages that are outside of the FSwiki. We have no power nor means to change anything there. So if project's webpages are outdated we can't really help you or them other than notifying the respective project. In this case however you should be able to download the content via the forums [http://www.hard-light.net/forums/index.php?topic=69901.0]. I suppose same links could be added to TVWP wikipage. And given that TVWP just recently (June 2010) put out a new demo release i doubt that the project would actually be dead. - [[User:Wanderer|Wanderer]] 04:39, 22 June 2010 (UTC)

::The TVWP staff forgot to fix the links when we posted the release thread. Everything should be okay now. Thanks to Wanderer for the heads-up in our project board. - [[User:Goober5000|Goober5000]] 03:59, 23 June 2010 (UTC)

Could somebody do a Wings of Dawn page that is awesome so we can feature it? BP gets its fair share of the limelight already. [[User:General Battuta|General Battuta]] 00:40, 5 October 2010 (UTC)
*This would be very welcome. Might want to ask on the wiki board as well, though, as I suspect that gets more attention than a mere talk page. - [[User:Shade|Shade]] 11:39, 5 October 2010 (UTC)

==Admin Control?==
Do you have to be like...an Admin to change the main?
:ATM, AFAIK no. - [[User:Wanderer|Wanderer]] 15:04, 16 June 2007 (CDT)

==More features?==

Do you agree on having more than a "Featured Campaign of the Moment" section in the main page? Something like highlights on recent articles and such? --- [[User:Mobius|Mobius]]
:No thanks, I think the main page is fine as it is now. - [[User:Snail|Snail]] 16:35, 7 April 2009 (UTC)
::Agreed. - [[User:TopAce|TopAce]] 16:51, 7 April 2009 (UTC)
:::You have to admit that it's very poor compared to the average Wiki's Main Page. --- [[User:Mobius|Mobius]]
::::No, it's not. It's simple. It says what's needed. And that's all which is required of a Wiki Main Page. - [[User:Snail|Snail]] 08:26, 10 April 2009 (UTC)
While I wouldn't mind seeing the featured campaign cycle a little more often, my chief complaint about the "average" Wiki main page is that it's too busy. Less is more. -- [[User:BlueFlames|BlueFlames]] 15:32, 10 April 2009 (UTC)
:What do you mean? Are there too many links? - [[User:TopAce|TopAce]] 17:56, 10 April 2009 (UTC)
::I mean the FS Wiki's main page looks better than other Wikis because it doesn't have seventeen sections of useless, trivial clutter. -- [[User:BlueFlames|BlueFlames]] 03:25, 11 April 2009 (UTC)

==Adding "[[User-made Ships]]" to the main page nav list==
EDIT: I wanted to add the "[[User-made Ships]]" page to the nav menu on the right under ''Modding FreeSpace'', but I can't get to that section by just clicking the edit button on the main page. Can somebody with the ability add that for me?. --[[User:Scourge of Ages|Scourge of Ages]] 22:20, 25 December 2010 (UTC)

*You can't find it because it's in a navigation template rather than in the actual page itself. In the edit screen, you'll find a list of the templates used on the page right below the edit box. You'll want "Main nav". [[User:Shade|Shade]] 00:36, 26 December 2010 (UTC)

==Protection==
Main page now set to admin-only editing due to a spambot infestation. If you need any changes done, contact a [[FreeSpace_Wiki:Administrators|Wiki Administrator]] and we can allow edits while you work.

Main Page

2011-04-12T12:16:27Z

Shade: Changed protection level for "Main Page": Raised protection level to admin-only, as a spambot somehow managed to edit it despite the current protection level. Get hold of a wiki admin if you need any changes done. ([edit=sysop] (indefinite) [move=syso

<center>

{| style="width:500px; border:1px #AA2020 solid; background:;"
|style="width:500px; text-align:center; background: #302020; white-space:nowrap; color:#000;"|
<div style="font-size:162%; border:none; margin:0; padding:.1em; color:#FFF;">Welcome to the [[Main Page| FreeSpace Wiki]]</div>
<div style="top:+0.2em; font-size:95%; color:#FFF;">The ultimate source of FreeSpace info.</div>
<div id="articlecount&user count" style="width:100%; text-align:center; font-size:70%; color:#FFF;">There are [[Special:Statistics|{{NUMBEROFARTICLES}}]] articles and [[Special:Statistics|{{NUMBEROFUSERS}}]] registered users.</div>
|}

</center>

{{Main nav}}

The ''FreeSpace'' Wiki is designed to be a comprehensive source of data for the ''FreeSpace'' series of games, including information about the games themselves, the FreeSpace universe, and community activities such as modding and the Source Code Project. It also contains help with some of the more common problems, such as setting up multiplayer and obtaining the FreeSpace games, which can be quite difficult in stores.

Anyone can edit the FreeSpace Wiki, and we encourage you to do so, but please read our [[canon|Canon Policy]] for information on what sort of data should be submitted, and how to submit it, before you begin. You should also note that registration is required to edit the FreeSpace Wiki. If you want to contribute but can not decide where to begin then you could start with going through the [[Freespace_Wiki:Requested_Pages|requested pages]]. Another place you may want to look at is the [[Special:SpecialPages|Special pages]] listing.

Lastly, if you want to add a Veteran Comment, please read [[Veteran comments policy|our Veteran Comments policy.]] 

[[Category:Main]]

{| border=0 cellpadding=0 cellspacing=0 style="margin: 0 0 0 0; background: #000000; border: 0px #AA2020 solid; border-collapse: collapse; font-size: 95%;"
|-
|{{Featured Article}}
|-
| style="padding-top:2em;" | {{Main Screens}}
|-
|}

Diaspora

2011-04-06T14:25:26Z

Shade:

'''''Diaspora''''' is the second Battlestar Galactica-based total conversion for the FreeSpace Open engine. The core of the team originally worked on [[Beyond the Red Line]] before leaving due to creative differences. It's currently WIP.

==General==

Release Schedule: ''Release 1, [[Diaspora: Shattered Armistice|Shattered Armistice]], is currently under active development (See [[Diaspora#Current Status|Current Status]]). Further episodic releases to follow''

Release Date: ''When It's Done (Unknown)''

Mods Required: ''None - As a standalone game, no mods or even an installation of FreeSpace is required''

Team Members:

*''Hassan "'''Karajorma'''" Kazmi'' - Project Leader.
*'''''Ace'''''
*''Joel "'''Axem'''" Reimer''
*''Joey "'''Blowfish'''" Wong''
*''Cliff "'''chief1983'''" Gordon''
*''Benjamin "'''DaBrain'''" Suhr''
*'''''Flipside'''''
*''Tuomas "'''Lt. Cannonfodder'''" Kankola''
*''Gabor "'''Meleardil'''" Toth''
*''Tony "'''FUBAR-BDHR'''" Perun''
*'''''_Max_'''''
*''Tvrtko "'''newman'''" Kapetanović''
*''Quiet''
*''J. Eldridge "'''Scotchy'''" Davis''
*'''''Shade'''''
*''Michal "'''Shiv'''" Cywinski''
*''John "'''Starslayer'''" Benson''
*''Zack "'''Turambar'''" Derouiche''
*''Thomas "'''Turey'''" Hall''
*''Vesa "'''Wanderer'''" Puoskari''
*'''''WMCoolmon'''''
*''Chris "'''Sushi'''" Wilson''
*''Dominik "'''Agba'''" Sendt''
*''Martin "'''Eldain'''" Olde''
*''Rhys "'''Echelon9'''" Kidd''
*''Guy "'''Nighteyes'''" Tourgeman''
*''Samuel "'''Swifty'''" Cho''
*''Olivier "'''LuaPineapple'''" Hamel''
*"'''HerraTohtori'''"
*''Philippe "'''PhRey'''" Rey''

==Current Status==

The first release, Shattered Armistice, is currently at a point where it is fully playable, but still in need of tweaking and balancing as well as some art assets. The biggest single item still missing is the new interface, which is a fairly daunting task in a standalone game. The concept for that is done, as are some needed code changes, but there's a fair bit of work remaining before it is usable.

==Gallery==

<gallery>
Image:RScreen0008.jpg|The Colonial Bolitho.
Image:RScreen0058.png|A large dogfight.
Image:RScreen0059.jpg|A Viper Mk7 heading towards two Basestars.
Image:RScreen0060.jpg|Viper squadron launching a missile barrage.
Image:RScreen0061.png|Cylon Raider trying to escape a Flak barrage.
Image:RScreen0062.png|Cylon Raider with a Colonial Bolitho-class corvette.
Image:RScreen0063.png|Colonial Sobek-class battlestar.
Image:RScreen0064.png|Colonial Sobek-class battlestar.
Image:RScreen0065.png|Colonial Sobek-class battlestar.
</gallery>

==Releases==
===[[Diaspora: Shattered Armistice|Shattered Armistice]]===

==Related Links==
'''Websites'''
*[http://www.diaspora-game.com Official website | Hard-Light Productions.net]
*[http://www.moddb.com/games/diaspora Mod profile | ModDB.com]

'''Forums/Threads'''
*[http://www.hard-light.net/forums/index.php/board,175.0.html Main board | Hard-Light Productions.net]
*[http://www.hard-light.net/forums/index.php/board,182.0.html Developer Blog subforum | Hard-Light Productions.net]

'''Videos'''
*[http://www.youtube.com/user/DiasporaGame Youtube Channel]

{{stub}}

[[Category: Total_Conversions]]
[[Category: Diaspora|*]]

Diaspora: Shattered Armistice

2011-04-06T14:17:21Z

Shade: More infos

'''''Shattered Armistice''''' is the name of the first [[Diaspora]] release. It is currently under active development, with no official ETA on a release.

The release will feature a tutorial, a single-player campaign and a number of multiplayer missions, including both Coop, Team vs Team and Dogfight missions. The single-player campaign stations you on the Battlestar Theseus, a Sobek-class Battlestar, as you struggle to survive.

==Flyable Ships==
*Viper Mk-VII
*Viper Mk-VIIE
*Raptor
*Combat Raptor
*Possibly others, depending on status of certain art assets at the time of release.

==Capital Ships==
*Sobek-class Battlestar
*Bolitho-class Frigate
*Cylon Basestar
*Several civilian ships, including freighters, shuttles, passenger liners and more.

==Notes==
*Originally, more flyable ships were meant to be included, but with the decision to include 3D modelled cockpits it was necessary to cut the number to keep the workload manageble. The cut ships will still feature in later releases, and may also show up as non-flyable ships.

{{stub}}

[[Category: Diaspora]]
[[Category: User-made Campaigns]]

Diaspora

2011-04-06T14:05:44Z

Shade: Oh alright, but only cause you asked nicely.

'''''Diaspora''''' is the second Battlestar Galactica-based total conversion for the FreeSpace Open engine. The core of the team originally worked on [[Beyond the Red Line]] before leaving due to creative differences. It's currently WIP.

==General==

Release Schedule: ''Release 1, [[Diaspora: Shattered Armistice|Shattered Armistice]], is currently under active development (See [[Diaspora#Current Status|Current Status]]). Further episodic releases to follow''

Release Date: ''When It's Done (Unknown)''

Mods Required: ''None - As a standalone game, no mods or even an installation of FreeSpace is required''

Team Members:

*''Hassan "'''Karajorma'''" Kazmi'' - Project Leader.
*'''''Ace''''' - FREDder
*''Joel "'''Axem'''" Reimer''
*''Joey "'''Blowfish'''" Wong''
*''Cliff "'''chief1983'''" Gordon''
*''Benjamin "'''DaBrain'''" Suhr''
*'''''Flipside'''''
*''Tuomas "'''Lt. Cannonfodder'''" Kankola''
*''Gabor "'''Meleardil'''" Toth''
*''Tony "'''FUBAR-BDHR'''" Perun''
*'''''_Max_'''''
*''Tvrtko "'''newman'''" Kapetanović''
*''Quiet''
*''J. Eldridge "'''Scotchy'''" Davis''
*'''''Shade'''''
*''Michal "'''Shiv'''" Cywinski''
*''John "'''Starslayer'''" Benson''
*''Zack "'''Turambar'''" Derouiche''
*''Thomas "'''Turey'''" Hall''
*''Vesa "'''Wanderer'''" Puoskari''
*'''''WMCoolmon'''''
*''Chris "'''Sushi'''" Wilson''
*''Dominik "'''Agba'''" Sendt''
*''Martin "'''Eldain'''" Olde''
*''Rhys "'''Echelon9'''" Kidd''
*''Guy "'''Nighteyes'''" Tourgeman''
*''Samuel "'''Swifty'''" Cho''
*''Olivier "'''LuaPineapple'''" Hamel''
*"'''HerraTohtori'''"
*''Philippe "'''PhRey'''" Rey''

==Current Status==

The first release, Shattered Armistice, is currently at a point where it is fully playable, but still in need of tweaking and balancing as well as some art assets. The biggest single item still missing is the new interface, which is a fairly daunting task in a standalone game. The concept for that is done, as are some needed code changes, but there's a fair bit of work remaining before it is usable.

==Gallery==

<gallery>
Image:RScreen0008.jpg|The Colonial Bolitho.
Image:RScreen0058.png|A large dogfight.
Image:RScreen0059.jpg|A Viper Mk7 heading towards two Basestars.
Image:RScreen0060.jpg|Viper squadron launching a missile barrage.
Image:RScreen0061.png|Cylon Raider trying to escape a Flak barrage.
Image:RScreen0062.png|Cylon Raider with a Colonial Bolitho-class corvette.
Image:RScreen0063.png|Colonial Sobek-class battlestar.
Image:RScreen0064.png|Colonial Sobek-class battlestar.
Image:RScreen0065.png|Colonial Sobek-class battlestar.
</gallery>

==Releases==
===[[Diaspora: Shattered Armistice|Shattered Armistice]]===

==Related Links==
'''Websites'''
*[http://www.diaspora-game.com Official website | Hard-Light Productions.net]
*[http://www.moddb.com/games/diaspora Mod profile | ModDB.com]

'''Forums/Threads'''
*[http://www.hard-light.net/forums/index.php/board,175.0.html Main board | Hard-Light Productions.net]
*[http://www.hard-light.net/forums/index.php/board,182.0.html Developer Blog subforum | Hard-Light Productions.net]

'''Videos'''
*[http://www.youtube.com/user/DiasporaGame Youtube Channel]

{{stub}}

[[Category: Total_Conversions]]
[[Category: Diaspora|*]]

Sensor degradation with range or facing

2011-02-22T19:28:13Z

Shade: Fixed up to make it actually work. This time, tested!

The following event is based on an idea by SypheDMar, as proposed in #freespace. It will, in theory, make a set of fighters either be invisible, show up as a fuzzy radar blip, or be fully targetable, all depending on their range to the player as well as whether the player is facing them (or more specifically if he has them within a 60-degree forward cone).

==Nested 'when'-based event==

The following version of the event demonstrates a number of things, not the least of which are nested 'when' operators, shared argument list between the nested whens, and considerable use of and/or-operators to fine tune triggers. Detailed explanation below, but without further ado, the event itself:

- op when-argument
- op any-of
# <list of ships for which to apply range/facing-based targetability>
- op true
- op when
- op and
- op not
- op is-ship-stealthy
# <argument>
- op or
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 3000
- op facing
# <argument>
# 60
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op not
- op facing
# <argument>
# 60
- op ship-stealthy
# <argument>
- op when
- op and
- op or
- op =
# 2
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 3000
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op >
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-invisible
# <argument>
- op ship-unstealthy
# <argument>
- op when
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-visible
# <argument>
- op ship-unstealthy
# <argument>
Notte the use of nested 'when' operators to cover three distinct sets of possibilities (in this case, distance brackets, but anything goes) within the same event, which allows them to draw on the same argument list. This is not terribly important in this particular case, as no arguments are invalidated or revalidated, but it is kept as one event for demonstration purposes. If one prefers, the event could easily be split in three without any change in functionality (one for each distance bracket).

The trigger conditions for each distance bracket are complicated by the fact that for this example, the direction the player is facing is also taken into account - If a ship is within a 60-degree forward cone of the player, it can be targeted at a significantly greater distance than otherwise. To account for this, each distance bracket actually has two distinct sets of trigger conditions, one for when the player is facing the right way, and one for when he isn't. And each of those sets in itself may require multiple conditions. This is all accomplished with a combination of [[and]] operators and [[or]] operators, allowing very precise tuning of when an given action should be triggered.

Finally, each distance bracket has a further condition which checks whether the ship currently being looked at is already set up for the bracket. Why? There's no point changing anything if nothing needs to be changed, and it's a waste of resources to, say, go setting invisibility flags for twenty ships every frame if they already have it set. It isn't strictly necessary to include such a check, but optimising where you can is a good habit to get into.

==If-then-else-based Event==

Now, using the above event (or three seperate ones), every distance bracket will get checked every frame against the argument list. Which, on the surface of it, is exactly what you want. But what if you could make it so the distance brackets are checked in turn, the next one in line only checked if the first one fails? That would surely save some CPU cycles. The thing is, you can. FreeSpace_Open now includes an [[if-then-else]] operator, which will let us do precisely that:

- op when-argument
- op any-of
# <list of ships for which to apply range/facing-based targetability>
- op true
- op if-then-else
- op and
- op not
- op is-ship-stealthy
# <argument>
- op or
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 3000
- op facing
# <argument>
# 60
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op not
- op facing
# <argument>
# 60
- op ship-stealthy
# <argument>
- op if-then-else
- op and
- op or
- op =
# 2
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 3000
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op >
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op when
- op true
- op ship-invisible
# <argument>
- op ship-unstealthy
# <argument>
- op when
- op and
- op or
- op =
# 1
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-visible
# <argument>
- op ship-unstealthy
# <argument>

In the revised event above, [[if-then-else]] is used to check the three distance brackets in sequence. If a ship is shown to place within a bracket, it acts on that and breaks out, whereas if a ship is not within the bracket being checked, it moves on to the next bracket and checks that instead. This reduces the amount of checks that happen compared to the first version of the event, and as a result will place a slightly lower demand on system resources. And while this is generally not a noticable effect, every CPU cycle does count.

Note the use of an additional nested 'when' in the second 'if-then-else'. This is necessary as there is more than one action to be taken, and only the second argument of the 'if-then-else' operator is the action to be taken if it is true - Third and beyond is for when it is false. Hence, the 'when' is used to group two actions into one argument.

Also note that the last case is not an 'if-then-else', but a 'when', just as in the first version of the event. This is because it is the last case, and as such there is no 'else' if this fails as well. However, it is NOT a default case which will always be carried out should the other two fail. Were that the case, the actions in it could simply be tacked onto the third-and-beyond argument of the second 'if-then-else', with no need for the 'when'.

[[Category:FRED Examples]]

Sensor degradation with range or facing

2011-02-22T18:52:41Z

Shade: /* If-then-else-based Event */ layout

The following event is based on an idea by SypheDMar, as proposed in #freespace. It will, in theory, make a set of fighters either be invisible, show up as a fuzzy radar blip, or be fully targetable, all depending on their range to the player as well as whether the player is facing them (or more specifically if he has them within a 60-degree forward cone).

==Nested 'when'-based event==

The following version of the event demonstrates a number of things, not the least of which are nested 'when' operators, shared argument list between the nested whens, and considerable use of and/or-operators to fine tune triggers. Detailed explanation below, but without further ado, the event itself:

- op when-argument
- op any-of
# <list of ships for which to apply range/facing-based targetability>
- op true
- op when
- op and
- op not
- op is-ship-stealthy
# <argument>
- op or
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 3000
- op facing
# <argument>
# 60
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op not
- op facing
# <argument>
# 60
- op ship-stealthy
# <argument>
- op when
- op and
- op or
- op =
# 2
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 3000
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op >
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-invisible
# <argument>
- op ship-unstealthy
# <argument>
- op when
- op and
- op or
- op =
# 1
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-visible
# <argument>
- op ship-unstealthy
# <argument>

Note the use of nested 'when' operators to cover three distinct sets of possibilities (in this case, distance brackets, but anything goes) within the same event, which allows them to draw on the same argument list. This is not terribly important in this particular case, as no arguments are invalidated or revalidated, but it is kept as one event for demonstration purposes. If one prefers, the event could easily be split in three without any change in functionality (one for each distance bracket).

The trigger conditions for each distance bracket are complicated by the fact that for this example, the direction the player is facing is also taken into account - If a ship is within a 60-degree forward cone of the player, it can be targeted at a significantly greater distance than otherwise. To account for this, each distance bracket actually has two distinct sets of trigger conditions, one for when the player is facing the right way, and one for when he isn't. And each of those sets in itself may require multiple conditions. This is all accomplished with a combination of [[and]] operators and [[or]] operators, allowing very precise tuning of when an given action should be triggered.

Finally, each distance bracket has a further condition which checks whether the ship currently being looked at is already set up for the bracket. Why? There's no point changing anything if nothing needs to be changed, and it's a waste of resources to, say, go setting invisibility flags for twenty ships every frame if they already have it set. It isn't strictly necessary to include such a check, but optimising where you can is a good habit to get into.

==If-then-else-based Event==

Now, using the above event (or three seperate ones), every distance bracket will get checked every frame against the argument list. Which, on the surface of it, is exactly what you want. But what if you could make it so the distance brackets are checked in turn, the next one in line only checked if the first one fails? That would surely save some CPU cycles. The thing is, you can. FreeSpace_Open now includes an [[if-then-else]] operator, which will let us do precisely that:

- op when-argument
- op any-of
# <list of ships for which to apply range/facing-based targetability>
- op true
- op if-then-else
- op and
- op not
- op is-ship-stealthy
# <argument>
- op or
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 3000
- op facing
# <argument>
# 60
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op not
- op facing
# <argument>
# 60
- op ship-stealthy
# <argument>
- op if-then-else
- op and
- op or
- op =
# 2
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 3000
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op >
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op when
- op true
- op ship-invisible
# <argument>
- op ship-unstealthy
# <argument>
- op when
- op and
- op or
- op =
# 1
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-visible
# <argument>
- op ship-unstealthy
# <argument>

In the revised event above, [[if-then-else]] is used to check the three distance brackets in sequence. If a ship is shown to place within a bracket, it acts on that and breaks out, whereas if a ship is not within the bracket being checked, it moves on to the next bracket and checks that instead. This reduces the amount of checks that happen compared to the first version of the event, and as a result will place a slightly lower demand on system resources. And while this is generally not a noticable effect, every CPU cycle does count.

Note the use of an additional nested 'when' in the second 'if-then-else'. This is necessary as there is more than one action to be taken, and only the second argument of the 'if-then-else' operator is the action to be taken if it is true - Third and beyond is for when it is false. Hence, the 'when' is used to group two actions into one argument.

Also note that the last case is not an 'if-then-else', but a 'when', just as in the first version of the event. This is because it is the last case, and as such there is no 'else' if this fails as well. However, it is NOT a default case which will always be carried out should the other two fail. Were that the case, the actions in it could simply be tacked onto the third-and-beyond argument of the second 'if-then-else', with no need for the 'when'.

[[Category:FRED Examples]]

Sensor degradation with range or facing

2011-02-19T14:01:43Z

Shade: minor fix

The following event is based on an idea by SypheDMar, as proposed in #freespace. It will, in theory, make a set of fighters either be invisible, show up as a fuzzy radar blip, or be fully targetable, all depending on their range to the player as well as whether the player is facing them (or more specifically if he has them within a 60-degree forward cone).

==Nested 'when'-based event==

The following version of the event demonstrates a number of things, not the least of which are nested 'when' operators, shared argument list between the nested whens, and considerable use of and/or-operators to fine tune triggers. Detailed explanation below, but without further ado, the event itself:

- op when-argument
- op any-of
# <list of ships for which to apply range/facing-based targetability>
- op true
- op when
- op and
- op not
- op is-ship-stealthy
# <argument>
- op or
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 3000
- op facing
# <argument>
# 60
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op not
- op facing
# <argument>
# 60
- op ship-stealthy
# <argument>
- op when
- op and
- op or
- op =
# 2
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 3000
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op >
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-invisible
# <argument>
- op ship-unstealthy
# <argument>
- op when
- op and
- op or
- op =
# 1
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-visible
# <argument>
- op ship-unstealthy
# <argument>

Note the use of nested 'when' operators to cover three distinct sets of possibilities (in this case, distance brackets, but anything goes) within the same event, which allows them to draw on the same argument list. This is not terribly important in this particular case, as no arguments are invalidated or revalidated, but it is kept as one event for demonstration purposes. If one prefers, the event could easily be split in three without any change in functionality (one for each distance bracket).

The trigger conditions for each distance bracket are complicated by the fact that for this example, the direction the player is facing is also taken into account - If a ship is within a 60-degree forward cone of the player, it can be targeted at a significantly greater distance than otherwise. To account for this, each distance bracket actually has two distinct sets of trigger conditions, one for when the player is facing the right way, and one for when he isn't. And each of those sets in itself may require multiple conditions. This is all accomplished with a combination of [[and]] operators and [[or]] operators, allowing very precise tuning of when an given action should be triggered.

Finally, each distance bracket has a further condition which checks whether the ship currently being looked at is already set up for the bracket. Why? There's no point changing anything if nothing needs to be changed, and it's a waste of resources to, say, go setting invisibility flags for twenty ships every frame if they already have it set. It isn't strictly necessary to include such a check, but optimising where you can is a good habit to get into.

==If-then-else-based Event==

Now, using the above event (or three seperate ones), every distance bracket will get checked every frame against the argument list. Which, on the surface of it, is exactly what you want. But what if you could make it so the distance brackets are checked in turn, the next one in line only checked if the first one fails? That would surely save some CPU cycles. The thing is, you can. FreeSpace_Open now includes an [[if-then-else]] operator, which will let us do precisely that:

- op when-argument
- op any-of
# <list of ships for which to apply range/facing-based targetability>
- op true
- op if-then-else
- op and
- op not
- op is-ship-stealthy
# <argument>
- op or
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 3000
- op facing
# <argument>
# 60
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op not
- op facing
# <argument>
# 60
- op ship-stealthy
# <argument>
- op if-then-else
- op and
- op or
- op =
# 2
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 3000
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op >
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op when
- op true
- op ship-invisible
# <argument>
- op ship-unstealthy
# <argument>
- op when
- op and
- op or
- op =
# 1
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-visible
# <argument>
- op ship-unstealthy
# <argument>

In the revised event above, [[if-then-else]] is used to check the three distance brackets in sequence. If a ship is shown to place within a bracket, it acts on that and breaks out, whereas if a ship is not within the bracket being checked, it moves on to the next bracket and checks that instead. This reduces the amount of checks that happen compared to the first version of the event, and as a result will place a slightly lower demand on system resources. And while this is generally not a noticable effect, every CPU cycle does count.

Note the use of an additional nested 'when' in the second 'if-then-else'. This is necessary as there is more than one action to be taken, and only the second argument of the 'if-then-else' operator is the action to be taken if it is true - Third and beyond is for when it is false. Hence, the 'when' is used to group two actions into one argument.

Also note that the last case is not an 'if-then-else', but a 'when', just as in the first version of the event. This is because it is the last case, and as such there is no 'else' if this fails as well. However, it is NOT a default case which will always be carried out should the other two fail. Were that the case, the actions in it could simply be tacked onto the third-and-beyond argument of the second 'if-then-else', with no need for the 'when'.

[[Category:FRED Examples]]

Is-ship-visible

2011-02-19T13:52:45Z

Shade: New page. Can't believe this was missing from the wiki despite being a retail operator

is-ship-visible
is-ship-visible
Check whether ship is visible on Player's radar
Single Player Only! Returns 0 - not visible, 1 - partially visible, 2 - fully visible.
1: Name of ship to check

===Comments===

Note that despite the name, this SEXP is numerical, not boolean. As such you need to use numerical comparison to check the result.

Retail SEXPs

2011-02-19T13:50:22Z

Shade: /* Status */ Added is-ship-visible

This page is quick a reference of SEXPs available in the retail version of [[Portal:FRED|FRED]]. To see the list of SEXPs that have been added, moved or modified by the SCP, go to the [[SCP SEXPs]] page. For tips and examples for how to properly use a SEXP when building missions, as well as warnings about potential pitfalls, follow the link to the detail page for the SEXP you are interested in.

==Objectives==
===[[is-destroyed-delay]]===
Is destroyed delay (Boolean operator)
Becomes true <delay> seconds after all specified ships have been destroyed.

Returns a boolean value; Takes 2 or more arguments:
1: Time delay in seconds (see above).
Rest: Name of ship (or wing) to check status of.
===[[is-subsystem-destroyed-delay]]===
Is subsystem destroyed delay (Boolean operator)
Becomes true <delay> seconds after the specified subsystem of the specified ship is destroyed.

Returns a boolean value; Takes 3 arguments:
1: Name of ship the subsystem we are checking is on.
2: The name of the subsystem we are checking status of.
3: Time delay in seconds (see above).
===[[is-disabled-delay]]===
Is disabled delay (Boolean operator)
Becomes true <delay> seconds after the specified ship(s) are disabled. A ship is disabled when all of it's engine
subsystems are destroyed. All ships must be diabled for this function to return true.

Returns a boolean value; Takes 2 or more arguments:
1: Time delay is seconds (see above).
Rest: Names of ships to check disabled status of.
===[[Is-disarmed-delay]]===
Is disarmed delay (Boolean operator)
Becomes true <delay> seconds after the specified ship(s) are disarmed. A ship is disarmed when all of it's turret
subsystems are destroyed. All ships must be disarmed for this function to return true.

Returns a boolean value; Takes 2 or more arguments:
1: Time delay is seconds (see above).
Rest: Names of ships to check disarmed status of.
===[[has-docked-delay]]===
Has docked delay (Boolean operator)
Becomes true <delay> seconds after the specified ships have docked the specified number of times.

Returns a boolean value; Takes 4 arguments:
1: The name of the docker ship
2: The name of the dockee ship
3: The number of times they have to have docked
4: Time delay in seconds (see above).
===[[has-undocked-delay]]===
Has undocked delay (Boolean operator)
Becomes true <delay> seconds after the specified ships have undocked the specified number of times.

Returns a boolean value; Takes 4 arguments:
1: The name of the docker ship
2: The name of the dockee ship
3: The number of times they have to have undocked
4: Time delay in seconds (see above).
===[[has-arrived-delay]]===
Has arrived delay (Boolean operator)
Becomes true <delay> seconds after the specified ship(s) have arrived into the mission

Returns a boolean value; Takes 2 or more arguments:
1: Time delay in seconds (see above).
Rest: Name of ship (or wing) we want to check has arrived.
===[[has-departed-delay]]===
Has departed delay (Boolean operator)
Becomes true <delay> seconds after the specified ship(s) or wing(s) have departed from the mission by warping out. If any
ship was destroyed, this operator will never be true.

Returns a boolean value; Takes 2 or more arguments:
1: Time delay in seconds (see above).
Rest: Name of ship (or wing) we want to check has departed.
===[[are-waypoints-done-delay]]===
Waypoints done delay (Boolean operator)
Becomes true <delay> seconds after the specified ship has completed flying the specified waypoint path.

Returns a boolean value; Takes 3 arguments:
1: Name of ship we are checking.
2: Waypoint path we want to check if ship has flown.
3: Time delay in seconds (see above).
===[[ship-type-destroyed]]===
Ship Type Destroyed (Boolean operator)
Becomes true when the specified percentage of ship types in this mission have been destroyed. The ship type is a generic
type such as fighter/bomber, transport, etc. Fighters and bombers count as the same type.

Returns a boolean value; Takes 2 arguments:
1: Percentage of ships that must be destroyed.
2: Ship type to check for.
===[[percent-ships-departed]]===
percent-ships-departed
Boolean function which returns true if the percentage of ships in the listed ships and wings which have departed is
greater or equal to the given percentage. For wings, all ships of all waves are used for calculation for the total possible
ships to depart.

Takes 2 or more arguments:
1: Percentge of departed ships at which this function will return true.
2+: List of ships/wing whose departure status should be determined.
===[[percent-ships-destroyed]]===
percent-ships-destroyed
Boolean function which returns true if the percentage of ships in the listed ships and wings which have been destroyed
is greater or equal to the given percentage. For wings, all ships of all waves are used for calculation for the total possible
ships to be destroyed.

Takes 2 or more arguments:
1: Percentge of destroyed ships at which this function will return true.
2+: List of ships/wing whose destroyed status should be determined.
===[[depart-node-delay]]===
depart-node-delay
Returns true N seconds after the listed ships depart, if those ships depart within the radius of the given jump node.
The delay value is given in seconds.

Takes 3 or more arguments:
1: Delay in seconds after the last ship listed departed before this expression can return true.
2: Name of a jump node
3+: List of ships to check for departure within radius of the jump node
===[[destroyed-or-departed-delay]]===
destroyed-or-departed-delay
Returns true N seconds after all the listed ships or wings have been destroyed or have departed.

Takes 2 or more arguments:
1: Delay in seconds after the last ship/wing is destroyed or departed this expression can return true.
2+: Name of a ship or wing
==Time==
===[[time-ship-destroyed]]===
Time ship destroyed (Time operator)
Returns the time the specified ship was destroy.

Returns a numeric value; Takes 1 argument:
1: Name of ship we want to check.
===[[time-ship-arrived]]===
Time ship arrived (Time operator)
Returns the time the specified ship arrived into the mission.

Returns a numeric value; Takes 1 argument:
1: Name of ship we want to check.
===[[time-ship-departed]]===
Time ship departed (Time operator)
Returns the time the specified ship departed the mission by warping out. Being destroyed doesn't count departed.

Returns a numeric value; Takes 1 argument:
1: Name of ship we want to check.
===[[time-wing-destroyed]]===
Time wing destroyed (Time operator)
Returns the time the specified wing was destroy.

Returns a numeric value; Takes 1 argument:
1: Name of wing we want to check.
===[[time-wing-arrived]]===
Time wing arrived (Time operator)
Returns the time the specified wing arrived into the mission.

Returns a numeric value; Takes 1 argument:
1: Name of wing we want to check.
===[[time-wing-departed]]===
Time wing departed (Time operator)
Returns the time the specified wing departed the mission by warping out. All ships in the wing have to have warped out. If any are destroyed, the wing can never be considered departed.

Returns a numeric value; Takes 1 argument:
1: Name of ship we want to check.
===[[mission-time]]===
Mission time (Time operator)
Returns the current time into the mission.

Returns a numeric value.
===[[time-docked]]===
Time docked (Time operator)
Returns the time the specified ships docked.

Returns a numeric value; Takes 3 arguments:
1: The name of the docker ship.
2: The name of the dockee ship.
3: The number of times they must have docked to be true.
===[[time-undocked]]===
Time undocked (Time operator)
Returns the time the specified ships undocked.

Returns a numeric value; Takes 3 arguments:
1: The name of the docker ship.
2: The name of the dockee ship.
3: The number of times they must have undocked to be true.
==Logical==
===[[true]]===
True (Boolean operator)
A true boolean state

Returns a boolean value.
===[[false]]===
False (Boolean operator)
A false boolean state

Returns a boolean value.
===[[and]]===
And (Boolean operator)
And is true if all of its arguments are true.

Returns a boolean value. Takes 2 or more boolean arguments.
===[[and-in-sequence]]===
And in sequence (Boolean operator)
Returns true if all of its arguments have become true in the order they are listed in.

Returns a boolean value. Takes 2 or more boolean arguments.
===[[or]]===
Or (Boolean operator)
Or is true if any of its arguments are true.

Returns a boolean value. Takes 2 or more boolean arguments.
===[[not]]===
Not (Boolean operator)
Returns opposite boolean value of argument (True becomes false, and false becomes true).

Returns a boolean value; Takes 1 boolean argument.
===[[=]]===
Equals (Boolean operator)
Is true if all of it's arguments are equal.

Returns a boolean value; Takes 2 or more numeric arguments.
===[[greater-than|>]]===
Greater than (Boolean operator)
True if first argument is greater than the second argument.

Returns a boolean value; Takes 2 numeric arguments.
===[[less-than|<]]===
Less than (Boolean operator)
True if first argument is less than the second argument.

Returns a boolean value; Takes 2 numeric arguments.
===[[is-iff]]===
Is IFF (Boolean operator)
True if ship{s} are all of the specified team.

Returns a boolean value; Takes 2 or more arguments:
/t1: Team ("friendly", "hostile" or "unknown").
Rest: Name of ship to check.
===[[has-time-elapsed]]===
Has time elapsed (Boolean operator)
Becomes true when the specified amount of time has elapsed (Mission time becomes greater than the specified time).
Returns a boolean value; Takes 1 numeric argument:
1: The amount of time in seconds.
==Arithmetic==
===[[plus|+]]===
+
Plus (Arithmetic operator)
Adds numbers and returns results.

Returns a number. Takes 2 or more numeric arguments.
===[[minus|-]]===
-
Minus (Arithmetic operator)
Subtracts numbers and returns results.

Returns a number. Takes 2 or more numeric arguments.
===[[multiply|*]]===
*
Multiply (Arithmetic operator)
Multiplies numbers and returns results.

Returns a number. Takes 2 or more numeric arguments.
===[[divide|/]]===
/
Divide (Arithmetic operator)
Divides numbers and returns results.

Returns a number. Takes 2 or more numeric arguments.
===[[mod]]===
mod
Mod (Arithmetic operator)
Divides numbers and returns the remainer.

Returns a number. Takes 2 or more numeric arguments.
===[[rand]]===
rand
Rand (Arithmetic operator)
Gets a random number. This number will not change on successive calls to this sexp.

Returns a number. Takes 2 or 3 numeric arguments...
1: Low range of random number.
2: High range of random number.
3: (optional) A seed to use when generating numbers. (Setting this to 0 is the same as having no seed at all)
==Status==
===[[is-ship-visible]]===
is-ship-visible
is-ship-visible
Check whether ship is visible on Player's radar
Single Player Only! Returns 0 - not visible, 1 - partially visible, 2 - fully visible.
1: Name of ship to check
===[[is-cargo-known-delay]]===
is-cargo-known-delay
Is cargo known (delay) (Boolean operator)
Returns true if all of the specified objects' cargo is known by the player (i.e. they have scanned each one.

Returns a boolean value after seconds when all cargo is known. Takes 2 or more arguments...
1: Delay in seconds after which sexpression will return true when all cargo scanned. Rest: Names of ships/cargo
to check for cargo known..
===[[cap-subsys-cargo-known-delay]]===
cap-subsys-cargo-known-delay
Is capital ship subsystem cargo known (delay) (Boolean operator)
Returns true if all of the specified subsystem cargo is known by the player.
Note: Cargo must be explicitly named.

Returns a boolean value after seconds when all cargo is known. Takes 3 or more arguments...
1: Delay in seconds after which sexpression will return true when all cargo scanned.
2: Name of capital ship
Rest: Names of subsystems to check for cargo known..
===[[has-been-tagged-delay]]===
has-been-tagged-delay
Has ship been tagged (delay) (Boolean operator)
Returns true if all of the specified ships have been tagged.

Returns a boolean value after seconds when all ships have been tagged. Takes 2 or more arguments...
1: Delay in seconds after which sexpression will return true when all cargo scanned. Rest: Names of ships to check if tagged..
===[[is-tagged]]===
is_tagged
is-tagged
Returns whether a given ship is tagged or not
===[[num-kills]]===
num_kills
num-kills
Returns the # of kills a player has. The ship specified in the first field should be the ship the player is in.
So, for single player, this would be Alpha 1. For multiplayer, it can be any ship with a player in it. If, at any
time there is no player in a given ship, this sexpression will return 0
===[[num-type-kills]]===
num_type_kills
num-type-kills
Returns the # of kills a player has on a given ship type (fighter, bomber, cruiser, etc).
The ship specified in the first field should be the ship the player is in.
So, for single player, this would be Alpha 1. For multiplayer, it can be any ship with a player in it. If, at any
time there is no player in a given ship, this sexpression will return 0
===[[num-class-kills]]===
num_class_kills
num-class-kills
Returns the # of kills a player has on a specific ship class (Ulysses, Hercules, etc).
The ship specified in the first field should be the ship the player is in.
So, for single player, this would be Alpha 1. For multiplayer, it can be any ship with a player in it. If, at any
time there is no player in a given ship, this sexpression will return 0
===[[shield-recharge-pct]]===
shield-recharge-pct
shield-recharge-pct
Returns a percentage from 0 to 100
1: Ship name
===[[engine-recharge-pct]]===
engine-recharge-pct
engine-recharge-pct
Returns a percentage from 0 to 100
1: Ship name
===[[weapon-recharge-pct]]===
weapon-recharge-pct
weapon-recharge-pct
Returns a percentage from 0 to 100
1: Ship name
===[[shield-quad-low]]===
shield-quad-low
shield-quad-low
Returns true if the specified ship has a shield quadrant below
the specified threshold percentage
1: Ship name
2: Percentage
===[[secondary-ammo-pct]]===
secondary-ammo-pct
secondary-ammo-pct
Returns the percentage of ammo remaining in the specified bank (0 to 100)
1: Ship name
2: Bank to check (0, 1, 2 and 3 are legal banks. 4 will return the cumulative average for all banks)
===[[is-secondary-selected]]===
is-secondary-selected
is-secondary-selected
Returns true if the specified bank is selected (0 .. num_banks - 1)
1: Ship name
2: Bank to check (0 .. num_banks - 1)
===[[is-primary-selected]]===
is-primary-selected
is-primary-selected
Returns true if the specified bank is selected (0 .. num_banks - 1)
1: Ship name
2: Bank to check (0 .. num_banks - 1)
===[[shields-left]]===
shields-left
Shields left (Status operator)
Returns the current level of the specified ship's shields as a percentage.

Returns a numeric value. Takes 1 argument...
1: Name of ship to check.
===[[hits-left]]===
hits-left
Hits left (Status operator)
Returns the current level of the specified ship's hull as a percentage.

Returns a numeric value. Takes 1 argument...
1: Name of ship to check.
===[[hits-left-subsystem]]===
hits-left-subsystem
Hits left subsystem (Status operator)
Returns the current level of the specified ship's subsystem integrity as a percentage.

Returns a numeric value. Takes 1 argument...
1: Name of ship to check.
2: Name of subsystem on ship to check.
===[[distance]]===
distance
Distance (Status operator)
Returns the distance between two objects. These objects can be either a ship, a wing, or a waypoint.
When a wing or team is given (for either argument) the answer will be the shortest distance.

Returns a numeric value. Takes 2 arguments...
1: The name of one of the objects.
2: The name of the other object.
===[[is-ship-visible]]===
is-ship-visible
is-ship-visible
Check whether ship is visible on Player's radar
Single Player Only! Returns 0 - not visible, 1 - partially visible, 2 - fully visible.
1: Name of ship to check
===[[team-score]]===
team-score
team-score
Get the score of a multi team vs team game.
1: Team index (1 for team 1 and 2 for team 2)
===[[time-elapsed-last-order]]===
time-elapsed-last-order
Last order time (Status operator)
Returns true if seconds have elapsed since one or more ships have received a meaningful order from the player.
A meaningful order is currently any order that is not the warp out order.

Returns a boolean value. Takes 2 or more arguments...
1: Time in seconds that must elapse.
Rest: Name of ship or wing to check for having received orders.
===[[skill-level-at-least]]===
skill-level-at-least
Skill level at least (Boolean operator)
Returns true if the player has selected the given skill level or higher.

Returns a boolean value. Takes 1 argument...
1: Name of the skill level to check.
===[[num-players]]===
num-players
Num players (Status operator)
Returns the current number of players (multiplayer) playing in the current mission.

Returns a numeric value. Takes no arguments.
===[[special-warp-dist]]===
special-warp-dist
special-warp-dist
Returns distance to the plane of the knossos device in percent length of ship
(ie, 100 means front of ship is 1 ship length from plane of knossos device)
1: Ship name

==Change==
===[[modify-variable]]===
modify-variable
Modify-variable (Misc. operator)
Modifies variable to specified value

Takes 2 arguments...
1: Name of Variable.
2: Value to be set.
===[[special-warpout-name]]===
special-warpout-name
special-warpout-name
Sets the name of the knossos device to be used for warpout
1: Ship name to exit
2: Name of knossos device
===[[do-nothing]]===
do-nothing
Do-nothing (Action operator)
Does nothing. This is used as the default for any required action arguments of an operator.
===[[add-goals]]===
add-goal
Add goal (Action operator)
Adds a goal to a ship or wing.

Takes 2 arguments...
1: Name of ship or wing to add goal to.
2: Goal to add.
===[[clear-goals]]===
clear-goals
Clear goals (Action operator)
Clears the goals for the specified ships and/or wings.

Takes 1 or more arguments...
All: Name of ship or wing.
===[[change-iff]]===
change-iff
Change IFF (Action operator)
Sets the specified ship(s) or wing(s) to the specified team.
Takes 2 or more arguments...
1: Team to change to ("friendly", "hostile" or "unknown").
Rest: Name of ship or wing to change team status of.
===[[protect-ship]]===
protect-ship
Protect ship (Action operator)
Protects a ship from being attacked by any enemy ship. Any shipthat is protected will not come under enemy fire.

Takes 1 or more arguments...
All: Name of ship(s) to protect.
===[[unprotect-ship]]===
unprotect-ship
Unprotect ship (Action operator)
Unprotects a ship from being attacked by any enemy ship. Any shipthat is not protected can come under enemy fire.
This function is the oppositeof protect-ship.

Takes 1 or more arguments...
All: Name of ship(s) to protect.
===[[beam-protect-ship]]===
beam-protect-ship
Beam Protect ship (Action operator)
Protects a ship from being attacked with beam weapon. Any shipthat is beam protected will not come under enemy beam fire.

Takes 1 or more arguments...
All: Name of ship(s) to protect.
===[[beam-unprotect-ship]]===
beam-unprotect-ship
Beam Unprotect ship (Action operator)
Unprotects a ship from being attacked with beam weapon. Any shipthat is not beam protected can come under enemy beam fire.
This function is the oppositeof beam-protect-ship.

Takes 1 or more arguments...
All: Name of ship(s) to protect.
===[[send-message]]===
send-message
Send message (Action operator)
Sends a message to the player. Can be send by a ship, wing, or special source. To send it from a special source,
make the first character of the first argument a "#".

Takes 3 arguments...
1: Name of who the message is from.
2: Priority of message ("Low", "Normal" or "High").
3: Name of message (from message editor).
===[[self-destruct]]===
self-destruct
Self destruct (Action operator)
Causes the specified ship(s) to self destruct.

Takes 1 or more arguments...
All: Name of ship to self destruct.
===[[end-campaign]]===
end-campaign
end-campaign
Ends the builtin campaign. Should only be used by the main FreeSpace campaign
===[[sabotage-subsystem]]===
sabotage-subsystem
Sabotage subystem (Action operator)
Reduces the specified subsystem integrity by the specified percentage.If the percntage strength of the subsystem
(after completion) is less than 0%,subsystem strength is set to 0%.

Takes 3 arguments...
1: Name of ship subsystem is on.
2: Name of subsystem to sabotage.
3: Percentage to reduce subsystem integrity by.
===[[repair-subsystem]]===
repair-subsystem
Repair Subystem (Action operator)
Increases the specified subsystem integrity by the specified percentage.If the percntage strength of the subsystem
(after completion) is greater than 100%,subsystem strength is set to 100%.

Takes 4 arguments...
1: Name of ship subsystem is on.
2: Name of subsystem to repair.
3: Percentage to increase subsystem integrity by.
4: Repair turret submodel. Optional argument that defaults to true.
===[[set-subsystem-strength]]===
set-subsystem-strength
Set Subsystem Strength (Action operator)
Sets the specified subsystem to the the specified percentage.If the percentage specified is < 0, strength is set to 0.
If the percentage is > 100 % the subsystem strength is set to 100%.

Takes 3 arguments...
1: Name of ship subsystem is on.
2: Name of subsystem to set strength.
3: Percentage to set subsystem integrity to.
4: Repair turret submodel. Optional argument that defaults to true.
===[[invalidate-goal]]===
invalidate-goal
Invalidate goal (Action operator)
Makes a mission goal invalid, which causes it to not show up on mission goals screen, or be evaluated.
Takes 1 or more arguments...
All: Name of mission goal to invalidate.
===[[validate-goal]]===
validate-goal
Validate goal (Action operator)
Makes a mission goal valid again, so it shows up on mission goals screen.
Takes 1 or more arguments...
All: Name of mission goal to validate.
===[[send-random-message]]===
send-random-message
Send random message (Action operator)
Sends a random message to the player from those supplied. Can be send by a ship, wing, or special source.
To send it from a special source, make the first character of the first argument a "#".

Takes 3 or more arguments...
1: Name of who the message is from.
2: Priority of message ("Low", "Normal" or "High"). Rest: Name of message (from message editor).
===[[transfer-cargo]]===
transfer-cargo
Transfer Cargo (Action operator)
Transfers the cargo from one ship to another ship.

Takes 2 arguments...
1: Name of ship that cargo is being transferred from.
2: Name of ship that cargo is being transferred to.
===[[exchange-cargo]]===
exchange-cargo
Exchange Cargo (Action operator)
Exchanges the cargos of two ships. If one of the two ships contains no cargo, the cargo is transferred instead.
Takes 2 arguments...
1: Name of one of the ships.
2: Name of the other ship.
===[[good-rearm-time]]===
good-rearm-time
Good rearm time (Action operator)
Informs the game logic that right now is a good time for a given team to attempt to rearm their ships.
The time parameter specified how long the "good time" will last.

Takes 2 arguments...
1: Team Name
2: Time in seconds rearm window should last
===[[allow-ship]]===
allow-ship
Allow ship (Action operator)
This operator makes the given ship type available to the Terran team. Players will be able to have ships of this type
in their starting wings in all future missions of this campaign.

Takes 1 argument...
1: Name of ship type (or ship class) to allow.
===[[allow-weapon]]===
allow-weapon
Allow weapon (Action operator)
This operator makes the given weapon available to the Terran team. Players will be able to equip ships with
in all future missions of this campaign.

Takes 1 argument...
1: Name of weapon (primary or secondary) to allow.
===[[break-warp]]===
break-warp
break-warp
Break the warp drive on the specified ship. A broken warp drive can be repaired by a repair ship. Takes 1 or more arguments...
All: List of ships to break the warp drive on
===[[fix-warp]]===
fix-warp
fix-warp
Fixes a broken warp drive instantaneously. This option applies to warp drives broken with the break-warp sepxression.
Takes 1 or more arguments...
All: List of ships whose warp drive should be fixed
===[[never-warp]]===
never-warp
never-warp
Never allows a ship to warp out. When this sexpression is used, the given ships will never be able to warp out.
The warp drive cannot be repaired. Takes 1 or more arguments...
All: List of ships whose are not allowed to warp out under any condition
===[[allow-warp]]===
allow-warp
allow-warp
Allows a ship which was previously not allowed to warp out to do so. When this sexpression is used, the given ships
will be able to warp out again. Takes 1 or more arguments...
All: List of ships whose are allowed to warp out
===[[good-secondary-time]]===
good-secondary-time
Set preferred secondary weapons
This sexpression is used to inform the AI about preferred secondary weapons to fire during combat. When this expression
is evaulated, any AI ships of the given team prefer to fire the given weapon at the given ship. (Preferred over other
secondary weapons)

Takes 4 argument...
1: Team name which will prefer firing given weapon
2: Maximum number of this type of weapon above team can fire.
3: Weapon name (list includes only the valid weapons for this expression
4: Ship name at which the above named team should fire the above named weapon.
===[[ship-invisible]]===
ship-invisible
ship-invisible
Causes the ships listed in this sexpression to be invisible to player sensors.

Takes 1 or more arguments...
1+: Name of ships to make invisible to sensors.
===[[ship-visible]]===
ship-visible
ship-visible
Causes the ships listed in this sexpression to be visible with player sensors.

Takes 1 or more arguments...
1+: Name of ships to make visible to sensors.
===[[ship-invulnerable]]===
ship-invulnerable
ship-invulnerable
Causes the ships listed in this sexpression to be invulnerable to weapons. Use with caution!!!!

Takes 1 or more arguments...
1+: Name of ships to make invulnerable to weapons.
===[[ship-vulnerable]]===
ship-vulnerable
ship-vulnerable
Causes the ship listed in this sexpression to be vulnerable to weapons.

Takes 1 or more arguments...
1+: Name of ships to make vulnerable to weapons.
===[[red-alert]]===
red-alert
red-alert
Causes Red Alert status in a mission. This function ends the current mission, and moves to the next mission
in the campaign under red alert status. There should only be one branch from a mission that uses this expression

Takes no arguments.
===[[jettison-cargo-delay]]===
jettison-cargo-delay
jettison-cargo-delay
Causes a cargo carrying ship to jettison its cargo without the undocking procedure. Takes 2 or more arguments...
1: Ship to jettison cargo
2: Delay after which to jettison cargo (note that this isn't actually used)
Rest (optional): Cargo to jettison. If no optional arguments are specified, the ship jettisons all cargo.
===[[fire-beam]]===
fire-beam
beam-fire
Fire a beam weapon from a specified subsystem
1: Ship which will be firing
2: Turret which will fire the beam (note, this turret must have at least 1 beam weapon on it)
3: Ship which will be targeted
Use add-data to add a specific subsystem to target on the specified target ship
===[[beam-free]]===
beam-free
beam-free
Sets one or more beam weapons to allow firing for a given ship
1: Ship to be operated on
2, 3, etc : List of turrets to activate
===[[beam-free-all]]===
beam-free-all
beam-free-all
Sets all beam weapons on the specified ship to be active
===[[beam-lock]]===
beam-lock
beam-lock
Sets one or more beam weapons to NOT allow firing for a given ship
1: Ship to be operated on
2, 3, etc : List of turrets to deactivate
===[[beam-lock-all]]===
beam-lock-all
beam-lock-all
Sets all beam weapons on the specified ship to be deactivated
===[[turret-free]]===
turret-free
turret-free
Sets one or more turret weapons to allow firing for a given ship
1: Ship to be operated on
2, 3, etc : List of turrets to activate
===[[turret-free-all]]===
turret-free-all
turret-free-all
Sets all turret weapons on the specified ship to be active
===[[turret-lock]]===
turret-lock
turret-lock
Sets one or more turret weapons to NOT allow firing for a given ship
1: Ship to be operated on
2, 3, etc : List of turrets to deactivate
===[[turret-lock-all]]===
turret-lock-all
turret-lock-all
Sets all turret weapons on the specified ship to be deactivated
===[[add-remove-escort]]===
add-remove-escort
add-remove-escort
Adds or removes a ship from an escort list.
1: Ship to be added or removed
2: 0 to remove from the list, any positive value will be used as the escort priority
NOTE : it _IS_ safe to add a ship which may already be on the list or remove
a ship which is not on the list
===[[awacs-set-range]]===
awacs-set-radius
awacs-set-radius
Sets the awacs radius for a given ship subsystem. NOTE : does not work properly in multiplayer
1: Ship which has the awacs subsystem
2: Awacs subsystem
3: New radius
===[[send-message-list]]===
send-message-list
send-message-list
Sends a series of delayed messages. All times are accumulated 1: Name of who the message is from.
2: Priority of message ("Low", "Normal" or "High").
3: Name of message (from message editor).
4: Delay in ms
Use Add-Data for multiple messagesIMPORTANT : each additional message in the list MUST HAVE 4 entries;
any message without the 4 proper fields will be ignored, as will any
successive messages
===[[cap-waypoint-speed]]===
cap-waypoint-speed
cap-waypoint-speed
Sets the maximum speed of a ship while flying waypoints.
1: Ship name
2: Maximum speed while flying waypoints
NOTE: This will only work if the ship is already in the game
NOTE: Set to -1 to reset
===[[ship-guardian]]===
ship-guardian
ship-guardian
Causes the ships listed in this sexpression to not be killable by weapons. Use with caution!!!!

Takes 1 or more arguments...
1+: Name of ships to make unkillable.
===[[ship-no-guardian]]===
ship-no-guardian
ship-no-guardian
Causes the ships listed in this sexpression to be killable by weapons, if not invulnerable.

Takes 1 or more arguments...
1+: Name of ships to make killable.
===[[ship-vanish]]===
ship-vanish
ship-vanish
Makes the named ship vanish (no log and vanish)
Single Player Only! Warning: This will cause ship exit not to be logged, so 'has-departed', etc. will not work
1: List of ship names to vanish
===[[turret-tagged-only]]===
turret-tagged-only
turret-tagged-only
Makes turrets target and hence fire strictly at tagged objects
1: Ship name
NOTE: Will not stop a turret already firing at an untagged ship
===[[turret-tagged-clear]]===
turret-tagged-clear
turret-tagged-clear
Relaxes restriction on turrets targeting only tagged ships
1: Ship name
===[[subsys-set-random]]===
subsys-set-random
subsys-set-random
Sets ship subsystem strength in a given range
1: Ship name
2: Low range
3: High range
4: List of subsys names not to be randomized
===[[supernova-start]]===
supernova-start
supernova-start
1: Time in seconds until the supernova shockwave hits the player
===[[cargo-no-deplete]]===
cargo-no-deplete
cargo-no-deplete
Causes the named ship to have unlimited cargo.
Note: only applies to BIG or HUGE ships
Takes 1 or more arguments...
1: Name of one of the ships.
2: optional: 1 disallow depletion, 0 allow depletion.
==Conditionals==
===[[when]]===
when
When (Conditional operator)
Performs specified actions when a condition becomes true

Takes 2 or more arguments...
1: Boolean expression that must be true for actions to take place.
Rest: Actions to take when boolean expression becomes true.
==Debugging==
===[[error]]===
==Ai goals==
===[[ai-chase]]===
ai-chase
Ai-chase (Ship goal)
Causes the specified ship to chase and attack the specified target.

Takes 2 arguments...
1: Name of ship to chase.
2: Goal priority (number between 0 and 89).
===[[ai-dock]]===
ai-dock
Ai-dock (Ship goal)
Causes one ship to dock with another ship.

Takes 4 arguments...
1: Name of dockee ship (The ship that "docker" will dock with).
2: Docker's docking point - Which dock point docker uses to dock.
3: Dockee's docking point - Which dock point on dockee docker will move to.
4: Goal priority (number between 0 and 89).
===[[ai-undock]]===
ai-undock
Ai-undock (Ship goal)
Causes the specified ship to undock from who it is currently docked with.

Takes 1 or 2 arguments...
1: Goal priority (number between 0 and 89).
2 (optional): Ship to undock from. If none is specified, the code will pick the first docked ship.
===[[ai-warp-out]]===
ai-warp-out
Ai-warp-out (Ship/Wing Goal)
Causes the specified ship/wing to warp out of the mission. Currently, the ship will warp out at its current location.
This behavior will change. Currently, the first argument means nothing.

Takes 2 arguments...
1: Name of waypoint path to follow to warp out (not used).
2: Goal priority (number between 0 and 89).
===[[ai-waypoints]]===
ai-waypoints
Ai-waypoints (Ship goal)
Causes the specified ship to fly a waypoint path continuously.

Takes 2 arguments...
1: Name of waypoint path to fly.
2: Goal priority (number between 0 and 89).
===[[ai-waypoints-once]]===
ai-waypoints-once
Ai-waypoints once (Ship goal)
Causes the specified ship to fly a waypoint path.

Takes 2 arguments...
1: Name of waypoint path to fly.
2: Goal priority (number between 0 and 89).
===[[ai-destroy-subsystem]]===
ai-destroy-subsystem
Ai-destroy subsys (Ship goal)
Causes the specified ship to attack and try and destroy the specified subsystem on the specified ship.

Takes 3 arguments...
1: Name of ship subsystem is on.
2: Name of subsystem on the ship to attack and destroy.
3: Goal priority (number between 0 and 89).
===[[ai-disable-ship]]===
ai-disable-ship
Ai-disable-ship (Ship/wing goal)
This AI goal causes a ship/wing to destroy all of the engine subsystems on the specified ship.
This goal is different than ai-destroy-subsystem since a ship may have multiple engine subsystems requiring
the use of > 1 ai-destroy-subsystem goals.

Takes 2 arguments...
1: Name of ship whose engine subsystems should be destroyed
2: Goal priority (number between 0 and 89).
===[[ai-disarm-ship]]===
ai-disarm-ship
Ai-disarm-ship (Ship/wing goal)
This AI goal causes a ship/wing to destroy all of the turret subsystems on the specified ship.
This goal is different than ai-destroy-subsystem since a ship may have multiple turret subsystems requiring
the use of > 1 ai-destroy-subsystem goals.

Takes 2 arguments...
1: Name of ship whose turret subsystems should be destroyed
2: Goal priority (number between 0 and 89).
===[[ai-guard]]===
ai-guard
Ai-guard (Ship goal)
Causes the specified ship to guard a ship from other ships not on the same team.

Takes 2 arguments...
1: Name of ship to guard.
2: Goal priority (number between 0 and 89).
===[[ai-chase-any]]===
ai-chase-any
Ai-chase-any (Ship goal)
Causes the specified ship to chase and attack any ship on the opposite team.

Takes 1 argument...
1: Goal priority (number between 0 and 89).
===[[ai-evade-ship]]===
ai-evade-ship
Ai-evade ship (Ship goal)
Causes the specified ship to go into evade mode and run away like the weak sally-boy it is.

Takes 2 arguments...
1: Name of ship to evade from.
2: Goal priority (number between 0 and 89).
===[[ai-stay-near-ship]]===
ai-stay-near-ship
Ai-stay near ship (Ship goal)
Causes the specified ship to keep itself near the given ship and not stray too far away from it.

Takes 2 arguments...
1: Name of ship to stay near.
2: Goal priority (number between 0 and 89).
===[[ai-keep-safe-distance]]===
ai-keep-safe-distance
Ai-keep safe distance (Ship goal)
Tells the specified ship to stay a safe distance away from any ship that isn't on the same team as it.

Takes 1 argument...
1: Goal priority (number between 0 and 89).
===[[ai-ignore]]===
ai-ignore
Ai-ignore (Ship goal)
Tells all ships to ignore the given ship and not consider it as a valid target to attack.

Takes 2 arguments...
1: Name of ship to ignore.
2: Goal priority (number between 0 and 89).
===[[ai-stay-still]]===
ai-stay-still
Ai-stay still (Ship goal)
Causes the specified ship to stay still. The ship will do nothing until attacked at which time the ship will
come to life and defend itself.

Takes 2 arguments...
1: Ship or waypoint the ship staying still will directly face (currently not implemented)
2: Goal priority (number between 0 and 89).
===[[ai-play-dead]]===
ai-play-dead
Ai-play dead (Ship goal)
Causes the specified ship to pretend that it is dead and not do anything. This expression should be used to indicate
that a ship has no pilot and cannot respond to any enemy threats. A ship playing dead will not respond to any attack.
This should really be named ai-is-dead

Takes 1 argument...
1: Goal priority (number between 0 and 89).
==Event/Goals==
===[[is-goal-incomplete]]===
is-goal-incomplete
Mission Goal Incomplete (Boolean operator)
Returns true if the specified goal in the this mission is incomplete. This sexpression will only be useful
in conjunction with another sexpression likehas-time-elapsed. Used alone, it will return true upon misison startup.
Returns a boolean value. Takes 1 argument...
1: Name of the event in the mission.
===[[is-goal-true-delay]]===
is-goal-true-delay
Mission Goal True (Boolean operator)
Returns true N seconds after the specified goal in the this mission is true (or succeeded). It returns false otherwise.

Returns a boolean value. Takes 2 required arguments and 1 optional argument...
1: Name of the event in the mission.
2: Number of seconds to delay before returning true.
===[[is-goal-false-delay]]===
is-goal-false-delay
Mission Goal False (Boolean operator)
Returns true N seconds after the specified goal in the this mission is false (or failed). It returns false otherwise.

Returns a boolean value. Takes 2 required arguments and 1 optional argument...
1: Name of the event in the mission.
2: Number of seconds to delay before returning true.
===[[is-event-incomplete]]===
is-event-incomplete
Mission Event Incomplete (Boolean operator)
Returns true if the specified event in the this mission is incomplete. This sexpression will only be useful
in conjunction with another sexpression likehas-time-elapsed. Used alone, it will return true upon misison startup.
Returns a boolean value. Takes 1 argument...
1: Name of the event in the mission.
===[[is-event-true-delay]]===
is-event-true-delay
Mission Event True (Boolean operator)
Returns true N seconds after the specified event in the this mission is true (or succeeded). It returns false otherwise.

Returns a boolean value. Takes 2 required arguments and 1 optional argument...
1: Name of the event in the mission.
2: Number of seconds to delay before returning true.
3: (Optional) True/False which signifies this is a current event, whether true, false, or unknown, for use as a directive.
===[[is-event-false-delay]]===
is-event-false-delay
Mission Event False (Boolean operator)
Returns true N seconds after the specified event in the this mission is false (or failed). It returns false otherwise.

Returns a boolean value. Takes 2 required arguments and 1 optional argument...
1: Name of the event in the mission.
2: Number of seconds to delay before returning true.
3: (Optional) True/False which signifies this is a current event, whether true, false, or unknown, for use as a directive.
===[[is-previous-goal-true]]===
is-previous-goal-true
Previous Mission Goal True (Boolean operator)
Returns true if the specified goal in the specified mission is true (or succeeded). It returns false otherwise.

Returns a boolean value. Takes 2 required arguments and 1 optional argument...
1: Name of the mission.
2: Name of the goal in the mission.
3: (Optional) True/False which signifies what this sexpession should return when this mission is played as a single mission.
===[[is-previous-goal-false]]===
is-previous-goal-false
Previous Mission Goal False (Boolean operator)
Returns true if the specified goal in the specified mission is false (or failed). It returns false otherwise.

Returns a boolean value. Takes 2 required arguments and 1 optional argument...
1: Name of the mission.
2: Name of the goal in the mission.
3: (Optional) True/False which signifies what this sexpession should return when this mission is played as a single mission.
===[[is-previous-event-true]]===
is-previous-event-true
Previous Mission Event True (Boolean operator)
Returns true if the specified event in the specified mission is true (or succeeded). It returns false otherwise.

Returns a boolean value. Takes 2 required arguments and 1 optional argument...
1: Name of the mission.
2: Name of the event in the mission.
3: (Optional) True/False which signifies what this sexpession should return when this mission is played as a single mission.
===[[is-previous-event-false]]===
is-previous-event-false
Previous Mission Event False (Boolean operator)
Returns true if the specified event in the specified mission is false (or failed). It returns false otherwise.

Returns a boolean value. Takes 2 required arguments and 1 optional argument...
1: Name of the mission.
2: Name of the event in the mission.
3: (Optional) True/False which signifies what this sexpession should return when this mission is played as a single mission.
==Training==
===[[key-pressed]]===
key-pressed
Key-pressed (Boolean training operator)
Becomes true when the specified default key has been pressed. Default key refers to the what the key normally
is when not remapped. FreeSpace will automatically account for any keys that have been remapped.
If the optional delay is specified, becomes true that many seconds after the key has been pressed.

Returns a boolean value. Takes 1 or 2 arguments...
1: Default key to check for.
2: Delay before operator registers as true (optional).
===[[key-reset]]===
key-reset
Key-reset (Training operator)
Marks the specified default key as having not been pressed, so key-pressed will be false until the player presses it again.
See key-pressed help for more information about what a default key is.

Note that this sexp will not work properly in repeating events. Use key-reset-multiple if this is to be called
multiple times in one event.

Returns a boolean value. Takes 1 or more arguments...
All: Default key to reset.
===[[targeted]]===
targeted
Targeted (Boolean training operator)
Is true as long as the player has the specified ship (or ship's subsystem) targeted, or has been targeted for the
specified amount of time.

Returns a boolean value. Takes 1 to 3 arguments (first required, rest optional):
1: Name of ship to check if targeted by player.
2: Length of time target should have been kept for (optional).
3: Name of subsystem on ship to check if targeted (optional).
===[[speed]]===
speed
Speed (Boolean training operator)
Becomes true when the player has been within the specified speed range set by set-training-context-speed for the
specified amount of time.

Returns a boolean value. Takes 1 argument...
1: Time in seconds.
===[[facing]]===
facing
Facing (Boolean training operator)
Is true as long as the specified ship is within the player's specified forward cone. A forward cone is defined as
any point that the angle between the vector of the point and the player, and the forward facing vector is within
the given angle.

Returns a boolean value. Takes 2 argument...
1: Ship to check is withing forward cone.
2: Angle in degrees of the forward cone.
===[[facing-waypoint]]===
facing-waypoint
Facing Waypoint(Boolean training operator)
Is true as long as the specified first waypoint is within the player's specified forward cone.
A forward cone is defined as any point that the angle between the vector of the point and the player,
and the forward facing vector is within the given angle.

Returns a boolean value. Takes 2 argument...
1: Name of waypoint path whose first point is withing forward cone.
2: Angle in degrees of the forward cone.
===[[order]]===
order
Order (Boolean training operator)
Becomes true when the player had given the specified ship or wing the specified order.

Returns a boolean value. Takes 2 or 3 arguments...
1: Name of ship or wing to check if given order to.
2: Name of order to check if player has given.
3: Name of the target of the order (optional).
===[[waypoint-missed]]===
waypoint-missed
Waypoint-missed (Boolean training operator)
Becomes true when a waypoint is flown, but the waypoint is ahead of the one they are supposed to be flying.
The one they are supposed to be flying is the next one in sequence in the path after the last one they have hit.

Returns a boolean value. Takes no arguments.
===[[waypoint-twice]]===
waypoint-twice
Waypoint-twice (Boolean training operator)
Becomes true when a waypoint is hit that is before the last one hit, which indicates they have flown a waypoint twice.

Returns a boolean value. Takes no arguments.
===[[path-flown]]===
path-flown
Path-flown (Boolean training operator)
Becomes true when all the waypoints in the path have been flown, in sequence.

Returns a boolean value. Takes no arguments.
===[[training-msg]]===
training-msg
Training-msg (Action training operator)
Sends the player a training message. Uses the same messages as normal messages, only they get displayed differently
using this operator. If a secondary message is specified, it is sent the last time, while the primary message is
sent all other times (event should have a repeat count greater than 1).

Takes 1-3 arguments...
1: Name of primary message to send.
2: Name of secondary message to send (optional).
3: Delay (in seconds) to wait before sending message. (optional)
4: Amount of Time (in seconds) to display message (optional).
===[[flash-hud-gauge]]===
flash-hud-gauge
Ai-flash hud gauge (Training goal)
Causes the specified hud gauge to flash to draw the player's attention to it.

Takes 1 argument...
1: Name of hud gauge to flash.
===[[special-check]]===
special-check
Special-check
Mike K.'s special training sexp. Returns a boolean value. Takes 1 argument as follows:
0: Ship "Freighter 1" is aspect locked by the player
1: Player has fired Interceptor#Weak at Freighter 1
2: Ship "Freighter 1", subsystem "Weapons" is aspect locked by the player
3: Apply 10 points of damage to player's forward shields (action operator)
4: Player's front shields are nearly gone
5: Quickly recharge player's front shields (action operator)
6: Reduce all shield quadrants except front to 0 (action operator)
7: Front shield quadrant is near maximum strength
8: Rear shield quadrant is near maximum strength
9: Reduce left and right shield quadrants to 0 (action operator)
10: Player has fewer than 8 missiles left
11: Player has 8 or more missiles left
12: Player has fewer than 4 missiles left
13: Reduce front shield quadrant to 0 (action operator)
100: Player is out of countermeasures
2000: Training failed
===[[secondaries-depleted]]===
secondaries-depleted
secondaries-depleted
Returns true if ship is out of secondary weapons
1: Ship name
===[[set-training-context-fly-path]]===
set-training-context-fly-path
Set-training-context-fly-path (Training context operator)
Tells FreeSpace that the player is expected to fly a waypoint path. This must be executed before waypoint-missed,
waypoint-twice and path-flown operators become valid.

Takes 2 arguments...
1: Name of waypoint path player should fly.
2: Distance away a player needs to be from a waypoint for it to be registered as flown.
===[[set-training-context-speed]]===
set-training-context-speed
Set-training-context-speed (Training context operator)
Tells FreeSpace that the player is expected to fly within a certain speed range. Once this operator has been executed,
you can measure how long they have been within this speed range with the speed operator.

Takes 2 arguments...
1: Minimum speed of range player is to fly between.
2: Maximum speed of range player is to fly between.
[[Category:Lists]]
[[Category:FRED]]

Sensor degradation with range or facing

2011-02-19T13:44:36Z

Shade: Fixed an error in the event

The following event is based on an idea by SypheDMar, as proposed in #freespace. It will, in theory, make a set of fighters either be invisible, show up as a fuzzy radar blip, or be fully targetable, all depending on their range to the player as well as whether the player is facing them (or more specifically if he has them within a 60-degree forward cone).

==Nested 'when'-based event==

The following version of the event demonstrates a number of things, not the least of which are nested 'when' operators, shared argument list between the nested whens, and considerable use of and/or-operators to fine tune triggers. Detailed explanation below, but without further ado, the event itself:

- op when-argument
- op any-of
# <list of ships for which to apply range/facing-based targetability>
- op true
- op when
- op and
- op not
- op is-ship-stealthy
# <argument>
- op or
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 3000
- op facing
# <argument>
# 60
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op not
- op facing
# <argument>
# 60
- op ship-stealthy
# <argument>
- op when
- op and
- op or
- op =
# 2
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 3000
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op >
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-invisible
# <argument>
- op ship-unstealthy
# <argument>
- op when
- op and
- op or
- op =
# 0
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-visible
# <argument>
- op ship-unstealthy
# <argument>

Note the use of nested 'when' operators to cover three distinct sets of possibilities (in this case, distance brackets, but anything goes) within the same event, which allows them to draw on the same argument list. This is not terribly important in this particular case, as no arguments are invalidated or revalidated, but it is kept as one event for demonstration purposes. If one prefers, the event could easily be split in three without any change in functionality (one for each distance bracket).

The trigger conditions for each distance bracket are complicated by the fact that for this example, the direction the player is facing is also taken into account - If a ship is within a 60-degree forward cone of the player, it can be targeted at a significantly greater distance than otherwise. To account for this, each distance bracket actually has two distinct sets of trigger conditions, one for when the player is facing the right way, and one for when he isn't. And each of those sets in itself may require multiple conditions. This is all accomplished with a combination of [[and]] operators and [[or]] operators, allowing very precise tuning of when an given action should be triggered.

Finally, each distance bracket has a further condition which checks whether the ship currently being looked at is already set up for the bracket. Why? There's no point changing anything if nothing needs to be changed, and it's a waste of resources to, say, go setting invisibility flags for twenty ships every frame if they already have it set. It isn't strictly necessary to include such a check, but optimising where you can is a good habit to get into.

==If-then-else-based Event==

Now, using the above event (or three seperate ones), every distance bracket will get checked every frame against the argument list. Which, on the surface of it, is exactly what you want. But what if you could make it so the distance brackets are checked in turn, the next one in line only checked if the first one fails? That would surely save some CPU cycles. The thing is, you can. FreeSpace_Open now includes an [[if-then-else]] operator, which will let us do precisely that:

- op when-argument
- op any-of
# <list of ships for which to apply range/facing-based targetability>
- op true
- op if-then-else
- op and
- op not
- op is-ship-stealthy
# <argument>
- op or
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 3000
- op facing
# <argument>
# 60
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op not
- op facing
# <argument>
# 60
- op ship-stealthy
# <argument>
- op if-then-else
- op and
- op or
- op =
# 2
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 3000
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op >
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op when
- op true
- op ship-invisible
# <argument>
- op ship-unstealthy
# <argument>
- op when
- op and
- op or
- op =
# 0
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-visible
# <argument>
- op ship-unstealthy
# <argument>

In the revised event above, [[if-then-else]] is used to check the three distance brackets in sequence. If a ship is shown to place within a bracket, it acts on that and breaks out, whereas if a ship is not within the bracket being checked, it moves on to the next bracket and checks that instead. This reduces the amount of checks that happen compared to the first version of the event, and as a result will place a slightly lower demand on system resources. And while this is generally not a noticable effect, every CPU cycle does count.

Note the use of an additional nested 'when' in the second 'if-then-else'. This is necessary as there is more than one action to be taken, and only the second argument of the 'if-then-else' operator is the action to be taken if it is true - Third and beyond is for when it is false. Hence, the 'when' is used to group two actions into one argument.

Also note that the last case is not an 'if-then-else', but a 'when', just as in the first version of the event. This is because it is the last case, and as such there is no 'else' if this fails as well. However, it is NOT a default case which will always be carried out should the other two fail. Were that the case, the actions in it could simply be tacked onto the third-and-beyond argument of the second 'if-then-else', with no need for the 'when'.

[[Category:FRED Examples]]

Sensor degradation with range or facing

2011-02-19T13:22:31Z

Shade: Improved comments

The following event is based on an idea by SypheDMar, as proposed in #freespace. It will, in theory, make a set of fighters either be invisible, show up as a fuzzy radar blip, or be fully targetable, all depending on their range to the player as well as whether the player is facing them (or more specifically if he has them within a 60-degree forward cone).

==Nested 'when'-based event==

The following version of the event demonstrates a number of things, not the least of which are nested 'when' operators, shared argument list between the nested whens, and considerable use of and/or-operators to fine tune triggers. Detailed explanation below, but without further ado, the event itself:

- op when-argument
- op any-of
# <list of ships for which to apply range/facing-based targetability>
- op true
- op when
- op and
- op not
- op is-ship-stealthy
# <argument>
- op or
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 3000
- op facing
# <argument>
# 60
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op not
- op facing
# <argument>
# 60
- op ship-stealthy
# <argument>
- op when
- op and
- op or
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 3000
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op >
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-invisible
# <argument>
- op ship-unstealthy
# <argument>
- op when
- op and
- op or
- op not
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-visible
# <argument>
- op ship-unstealthy
# <argument>

Note the use of nested 'when' operators to cover three distinct sets of possibilities (in this case, distance brackets, but anything goes) within the same event, which allows them to draw on the same argument list. This is not terribly important in this particular case, as no arguments are invalidated or revalidated, but it is kept as one event for demonstration purposes. If one prefers, the event could easily be split in three without any change in functionality (one for each distance bracket).

The trigger conditions for each distance bracket are complicated by the fact that for this example, the direction the player is facing is also taken into account - If a ship is within a 60-degree forward cone of the player, it can be targeted at a significantly greater distance than otherwise. To account for this, each distance bracket actually has two distinct sets of trigger conditions, one for when the player is facing the right way, and one for when he isn't. And each of those sets in itself may require multiple conditions. This is all accomplished with a combination of [[and]] operators and [[or]] operators, allowing very precise tuning of when an given action should be triggered.

Finally, each distance bracket has a further condition which checks whether the ship currently being looked at is already set up for the bracket. Why? There's no point changing anything if nothing needs to be changed, and it's a waste of resources to, say, go setting invisibility flags for twenty ships every frame if they already have it set. It isn't strictly necessary to include such a check, but optimising where you can is a good habit to get into.

==If-then-else-based Event==

Now, using the above event (or three seperate ones), every distance bracket will get checked every frame against the argument list. Which, on the surface of it, is exactly what you want. But what if you could make it so the distance brackets are checked in turn, the next one in line only checked if the first one fails? That would surely save some CPU cycles. The thing is, you can. FreeSpace_Open now includes an [[if-then-else]] operator, which will let us do precisely that:

- op when-argument
- op any-of
# <list of ships for which to apply range/facing-based targetability>
- op true
- op if-then-else
- op and
- op not
- op is-ship-stealthy
# <argument>
- op or
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 3000
- op facing
# <argument>
# 60
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op not
- op facing
# <argument>
# 60
- op ship-stealthy
# <argument>
- op if-then-else
- op and
- op or
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 3000
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op >
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op when
- op true
- op ship-invisible
# <argument>
- op ship-unstealthy
# <argument>
- op when
- op and
- op or
- op not
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-visible
# <argument>
- op ship-unstealthy
# <argument>

In the revised event above, [[if-then-else]] is used to check the three distance brackets in sequence. If a ship is shown to place within a bracket, it acts on that and breaks out, whereas if a ship is not within the bracket being checked, it moves on to the next bracket and checks that instead. This reduces the amount of checks that happen compared to the first version of the event, and as a result will place a slightly lower demand on system resources. And while this is generally not a noticable effect, every CPU cycle does count.

Note the use of an additional nested 'when' in the second 'if-then-else'. This is necessary as there is more than one action to be taken, and only the second argument of the 'if-then-else' operator is the action to be taken if it is true - Third and beyond is for when it is false. Hence, the 'when' is used to group two actions into one argument.

Also note that the last case is not an 'if-then-else', but a 'when', just as in the first version of the event. This is because it is the last case, and as such there is no 'else' if this fails as well. However, it is NOT a default case which will always be carried out should the other two fail. Were that the case, the actions in it could simply be tacked onto the third-and-beyond argument of the second 'if-then-else', with no need for the 'when'.

[[Category:FRED Examples]]

Sensor degradation with range or facing

2011-02-16T17:23:06Z

Shade: Improved comments

The following event is based on an idea by SypheDMar, as proposed in #freespace. It will, in theory, make a set of fighters either be invisible, show up as a fuzzy radar blip, or be fully targetable, all depending on their range to the player as well as whether the player is facing them (or more specifically if he has them within a 60-degree forward cone). Detailed explanation below, but without further ado, the event itself:

- op when-argument
- op any-of
# <list of ships for which to apply range/facing-based targetability>
- op true
- op when
- op and
- op not
- op is-ship-stealthy
# <argument>
- op or
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 3000
- op facing
# <argument>
# 60
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op not
- op facing
# <argument>
# 60
- op ship-stealthy
# <argument>
- op when
- op and
- op or
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 3000
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op >
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-invisible
# <argument>
- op ship-unstealthy
# <argument>
- op when
- op and
- op or
- op not
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-visible
# <argument>
- op ship-unstealthy
# <argument>

Note the use of nested 'when' operators to cover three distinct sets of possibilities within the same event, which allows them to draw on the same argument list. This is not terribly important in this particular case, as no arguments are invalidated or revalidated, but it is kept as one event for demonstration purposes. If one prefers, the event could easily be split in three without any change in functionality (one for each distance bracket).

Now, using the above event (or three seperate ones), every distance bracket will get checked every frame against the argument list. Which, on the surface of it, is exactly what you want. But what if you could make it so the distance brackets are checked in turn, the next one in line only checked if the first one fails? That would surely save some CPU cycles. The thing is, you can. FreeSpace_Open now includes an [[if-then-else]] operator, which will let us do precisely that:

- op when-argument
- op any-of
# <list of ships for which to apply range/facing-based targetability>
- op true
- op if-then-else
- op and
- op not
- op is-ship-stealthy
# <argument>
- op or
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 3000
- op facing
# <argument>
# 60
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op not
- op facing
# <argument>
# 60
- op ship-stealthy
# <argument>
- op if-then-else
- op and
- op or
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 3000
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op >
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op when
- op true
- op ship-invisible
# <argument>
- op ship-unstealthy
# <argument>
- op when
- op and
- op or
- op not
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-visible
# <argument>
- op ship-unstealthy
# <argument>

In the revised event above, [[if-then-else]] is used to check the three distance brackets in sequence. If a ship is shown to place within a bracket, it acts on that and breaks out, whereas if a ship is not within the bracket being checked, it moves on to the next bracket and checks that instead. This reduces the amount of checks that happen compared to the first version of the event, and as a result will place a slightly lower demand on system resources. And while this is generally not a noticable effect, every CPU cycle does count.

Note the use of an additional nested 'when' in the second 'if-then-else'. This is necessary as there is more than one action to be taken, and only the second argument of the 'if-then-else' operator is the action to be taken if it is true - Third and beyond is for when it is false. Hence, the 'when' is used to group two actions into one argument.

Also note that the last case is not an 'if-then-else', but a 'when', just as in the first version of the event. This is because it is the last case, and as such there is no 'else' if this fails as well. However, it is NOT a default case which will always be carried out should the other two fail. Were that the case, the actions in it could simply be tacked onto the third-and-beyond argument of the second 'if-then-else', with no need for the 'when'.

[[Category:FRED Examples]]

Sensor degradation with range or facing

2011-02-16T17:15:28Z

Shade: Added an if-then-else version of the example event

The following event is based on an idea by SypheDMar, as proposed in #freespace. It will, in theory, make a set of fighters either be invisible, show up as a fuzzy radar blip, or be fully targetable, all depending on their range to the player as well as whether the player is facing them (or more specifically if he has them within a 60-degree forward cone). Detailed explanation below, but without further ado, the event itself:

- op when-argument
- op any-of
# <list of ships for which to apply range/facing-based targetability>
- op true
- op when
- op and
- op not
- op is-ship-stealthy
# <argument>
- op or
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 3000
- op facing
# <argument>
# 60
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op not
- op facing
# <argument>
# 60
- op ship-stealthy
# <argument>
- op when
- op and
- op or
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 3000
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op >
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-invisible
# <argument>
- op ship-unstealthy
# <argument>
- op when
- op and
- op or
- op not
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-visible
# <argument>
- op ship-unstealthy
# <argument>

Note the use of nested 'when' operators to cover three distinct sets of possibilities within the same event, which allows them to draw on the same argument list. This is not terribly important in this particular case, as no arguments are invalidated or revalidated, but it is kept as one event for demonstration purposes. If one prefers, the event could easily be split in three without any change in functionality (one for each distance bracket).

Now, using the above event (or three seperate ones), every distance bracket will get checked every frame against the argument list. Which, on the surface of it, is exactly what you want. But what if you could make it so the distance brackets are checked in turn, the next one in line only checked if the first one fails? That would surely save some CPU cycles. The thing is, you can. FreeSpace_Open now includes an [[if-then-else]] operator, which will let us do precisely that:

- op when-argument
- op any-of
# <list of ships for which to apply range/facing-based targetability>
- op true
- op if-then-else
- op and
- op not
- op is-ship-stealthy
# <argument>
- op or
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 3000
- op facing
# <argument>
# 60
- op and
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op not
- op facing
# <argument>
# 60
- op ship-stealthy
# <argument>
- op if-then-else
- op and
- op or
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 3000
- op >
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op >
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op when
- op true
- op ship-invisible
# <argument>
- op ship-unstealthy
# <argument>
- op when
- op and
- op or
- op not
- op is-ship-visible
# <argument>
- op is-ship-stealthy
# <argument>
- op or
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 1000
- op facing
# <argument>
# 60
- op and
- op <=
- op distance
# <argument>
# Alpha 1
# 300
- op not
- op facing
# <argument>
# 60
- op ship-visible
# <argument>
- op ship-unstealthy
# <argument>

In the revised event above, [[if-then-else]] is used to check the three distance brackets in sequence. If a ship is shown to place within a bracket, it acts on that and breaks out, whereas if a ship is not within the bracket being checked, it moves on to the next bracket and checks that instead. This reduces the amount of checks that happen compared to the first version of the event, and as a result will place a slightly lower demand on system resources. And while this is generally not a noticable effect, every CPU cycle does count.

Note the use of an additional nested 'when' in the second if-then-else. This is necessary as there is more than one action to be taken, and only the second argument of the if-then-else operator is the action to be taken if it is true - Third and beyond is for when it is false. Hence, the 'when' is used to group two actions into one argument.

[[Category:FRED Examples]]

Sensor degradation with range or facing

2011-02-16T16:52:47Z

Shade: minor fix

Sensor degradation with range or facing

2011-02-16T16:47:17Z

Shade: More grammar. Argh

Sensor degradation with range or facing

2011-02-16T16:46:36Z

Shade: grammar

Sensor degradation with range or facing

2011-02-16T16:44:19Z

Shade: Example event, currently untested. Will add more detailed explanation later.

The Horror in the Deep

2011-02-10T13:43:59Z

Shade: /* Walkthrough */ - More detailed walkthrough

{{Derelict}}

{|- cellpadding="8" style="background:#000000;" align="center"
| [[Derelict Campaign Walkthrough|Campaign Walkthrough]]
| [[A Time for Penance|Previous Mission]]
| [[Rites of Passage|Next Mission]]
|-
|}

'''ACT 1 MISSION 8'''

'''Fighter squadron:''' [[212th Silver Scythes]]

'''Description:'''

----

==Background==

*'''Inflight Briefing'''

:Presently, '''Alpha''' wing is flying close escort to the '''TRGS Meridian''' and the '''TRGF Haulian.''' You are flying in the subspace corridor between the '''Tau Sigma''' and '''Altair''' jump nodes.

*At present, there is no sign of the pirate craft, designated '''Long John''' wing. We know these to be eight '''Ares''' class fighters. They are more heavily armed than your '''Myrmidons.''' However, we expect them to be carrying armament intended for disabling ships. This may be to your advantage, but don't count on it.

:Remember that in subspace, your shields will not work. The only benefit in this situation is that neither will theirs.

*Because of their six forward gun mounts and heavier armor, it is recommended that you avoid attacking '''Long John''' wing head on. To aid you, we have dispatched the '''GTS Servicor''' to reload your weapons. The '''Servicor''' is carrying additional missile supplies, so you may change your missile configuration if you so desire.

*Due to the nature of this type of mission, we can expect that '''Long John''' wing will not be operating alone. You can be sure of additional support craft in the area, and possibly even another wing of fighters. Be on your guard.

*The '''Vasudans''' have dispatched '''Omicron,''' wing of '''Serapis''' class fighters. They have also dispatched the '''GVT Isiroth''' to aid you. We expect them shortly.

:This is a dangerous mission, pilot. Good luck.


==Walkthrough==

There's a ton of campaign-persistent variables in this mission. If you destroyed any of the Long John fighters in the last mission, they won't appear. The briefing sounds imposing, but killing unshielded AI fighters is actually ridiculously easy. Just stay safe and don't do anything stupid.

The "pirates" will try to disable the convoy and [[Mackie]]. Blow that Hygeia off Alpha 2 before they make off with him (actually, they never will). Mackie will probably be at 1% hull by then, although the explosion of the Hygeia right above his ship won't faze him one bit.

The Mudenerei will blow up, then, surprise surprise, the [[SD Nyarlathotep|Nyarlathotep]] will make a brief appearance. Fight off a few more enemy wings while the convoy gets its engines back on-line.

--

Quite tough on higher difficulties, as even a single missile hit will put a serious dent in your hull, and a single hit from an Ares can destroy an important subsystem. For that reason, certain ground rules apply: Let your AI wingmen go first, never go head-to-head, don't pursue a target being hit by flak, and be liberal in your use of countermeasures.

With that in mind, the Long John wing should make fairly easy killing. As long as you don't get in front of them, Ares fighters are gratifyingly easy targets, and even more so when they are unshielded. The real challenge comes later, as you will be harrassed by a wing of Ulysses fighters while Hygeia-class support ships try to make off with any disabled wingmen of yours. Not to mention a Triton sporting both flak and AAA, which you should definitely leave to the AI unless you can find a safe angle to approach.

The Ulysses are annoying even without shields as they are such a small target and love to fly evasive, and on higher difficulties are quite fond of lobbing missiles at you too. Ideally, try to let the AIs distract them while you pick off the support ships from a long enough distance to avoid the blast when they go up, and provide support to the AIs once they have the enemy's attention. This should see you through the mission in one piece, though it may not feel very brave.

==Notes==

==Notable ships present==

* GTS Servicor
* [[TRGS Meridian]]
* [[TRGF Haulian]]
* [[GVT Isiroth]]
* Blackbeard ("pirate" [[GTFr Triton|Triton]])
* Drake ("pirate" [[GTT Elysium|Elysium]])
* Mudenerei ("pirate" [[GTA Charybdis|AWACs]])
* [[SD Nyarlathotep]] (named "Unknown" in this mission)

A Time for Penance

2011-02-10T12:27:27Z

Shade: /* Walkthrough */ - argh, another typo

{{Derelict}}

{|- cellpadding="8" style="background:#000000;" align="center"
| [[Derelict Campaign Walkthrough|Campaign Walkthrough]]
| [[Bait and Switch|Previous Mission]]
| [[The Horror in the Deep|Next Mission]]
|-
|}

ACT 1 MISSION 7

Fighter squadron: [[212th Silver Scythes]] 
Description: After a botched raid on what turned out to be a civilian operation, Alpha Wing must escort two research vessels to the Tau Jump Node. A pirate attack is almost certain.

----

== Command Briefing ==

* Command Incident Report 08/28/2372 1510

After acting out on what we thought was accurate intelligence, Alpha wing and the GTC LoneWolf led a raid on what turned out to be a civilian operation.

In the attack, the GTC LoneWolf engaged the TRGC Sai, damaging it. Fortunately we managed to stand down before an attack group of pirates arrived for the clean-up.

Still, the Sai and the LoneWolf were damaged enough that they are now in repair.

*
The Tepoheh Raleigh Group has launched a formal complaint along with the Morgan Mining Corporation. They're saying the GTVA is incapable of providing security in the outer territories. This is especially pressing now that we have recieved word that one million Capellan refugees are coming our way.

End of Incident Report

Alright pilot, we've got our work cut out for us. A lot of people are mad at us, but it's not our fault, and we still have a job to do. Report to briefing.

==Background==

*While the GTC LoneWolf and the TRGC Sai are in repair at Tau Sigma Station, the TRGS Meridian and the TRGF Haulian demanded to return to their office on Altair. Until we hear otherwise, we are still responsible for their safety.
*Alpha wing, it is your job to make sure that the Meridian and the Haulian reach the Altair jump node in one piece. They are carrying research materials that would fetch a high price on the black market.
*Alpha, you will fly close escort to the Meridian. The Morgan Mining Corporation has contracted mercenaries, designated Tachyon wing, to fly patrol. They are not under our command. You are NOT to engage them.
*Given the recent attacks, another pirate raid is almost certain. Be on your guard, and good luck pilot.


==Walkthrough==

A fairly challenging one. You will encounter a lot of Lokis on this mission. The drone's AI is set at the lowest possible level, Coward, but there's a lot of them. You may want to stay a bit behind your wingmen so you won't take the brunt of the fire.

It's extremely difficult to catch Long John wing. There's a secondary goal that becomes true when Long John is destroyed, but this is pretty much impossible, and even if you destroy the whole wing it says nothing about it in your debrief. You will, however, get a bit of recognition for destroying at least one of the fighters. If you set engine power to max and head to the node before Long John arrives, you may be able to catch one or two Ares, but it's not worth it if the convoy gets destroyed.

--

You finally get a decent weapon to work with, in the [[Prometheus S]]. Definitely bring one in the four-gun bank of your Myrm. Other than that, a mix of Tempests and Rockeyes is recommended.

From the mission start, afterburn towards your two charges at maximum engine power, and you should catch up easily before anything important happens. During or shortly after your sprint, you'll see the friendly merc wing tussle with some pirates, but these are none of your concern.

Instead, you will shortly be set upon by rather a lot of Lokis, arriving in groups of four with little to no break in between. Keep yourself and your wingmen close enough to the two civilians that you can get there fast if needed, but otherwise feel free to engage them as they seem to target your wing rather than the ships you are protecting. While they make easy targets even on high difficulties, try to avoid getting into head-to-head passes with them as they can still do damage there. And the Myrmidon is a big target.

Eventually, Long John wing will arrive near the node and make a run for it, but trying to catch them while also keeping the convoy alive is an exercise in futility, as a wing of pirate Hercules fighters will arrive at about the same time. And unlike the Lokis, these DO target your civilians and can make short work of them if left unattended. If you do want to try though, save a bunch of Rockeyes and use those from long range before turning back to help. As the Long John wings are flying in a straight line and won't do any evading, you ''might'' bag one that way and still make it back before your civilians go boom.

==Notes==

==Notable ships present==

* [[GTC LoneWolf]]
* [[TRGC Sai]]
* [[TRGS Meridian]]
* [[TRGF Haulian]]

A Time for Penance

2011-02-10T12:25:36Z

Shade: /* Walkthrough */ typo

{{Derelict}}

{|- cellpadding="8" style="background:#000000;" align="center"
| [[Derelict Campaign Walkthrough|Campaign Walkthrough]]
| [[Bait and Switch|Previous Mission]]
| [[The Horror in the Deep|Next Mission]]
|-
|}

ACT 1 MISSION 7

Fighter squadron: [[212th Silver Scythes]] 
Description: After a botched raid on what turned out to be a civilian operation, Alpha Wing must escort two research vessels to the Tau Jump Node. A pirate attack is almost certain.

----

== Command Briefing ==

* Command Incident Report 08/28/2372 1510

After acting out on what we thought was accurate intelligence, Alpha wing and the GTC LoneWolf led a raid on what turned out to be a civilian operation.

In the attack, the GTC LoneWolf engaged the TRGC Sai, damaging it. Fortunately we managed to stand down before an attack group of pirates arrived for the clean-up.

Still, the Sai and the LoneWolf were damaged enough that they are now in repair.

*
The Tepoheh Raleigh Group has launched a formal complaint along with the Morgan Mining Corporation. They're saying the GTVA is incapable of providing security in the outer territories. This is especially pressing now that we have recieved word that one million Capellan refugees are coming our way.

End of Incident Report

Alright pilot, we've got our work cut out for us. A lot of people are mad at us, but it's not our fault, and we still have a job to do. Report to briefing.

==Background==

*While the GTC LoneWolf and the TRGC Sai are in repair at Tau Sigma Station, the TRGS Meridian and the TRGF Haulian demanded to return to their office on Altair. Until we hear otherwise, we are still responsible for their safety.
*Alpha wing, it is your job to make sure that the Meridian and the Haulian reach the Altair jump node in one piece. They are carrying research materials that would fetch a high price on the black market.
*Alpha, you will fly close escort to the Meridian. The Morgan Mining Corporation has contracted mercenaries, designated Tachyon wing, to fly patrol. They are not under our command. You are NOT to engage them.
*Given the recent attacks, another pirate raid is almost certain. Be on your guard, and good luck pilot.


==Walkthrough==

A fairly challenging one. You will encounter a lot of Lokis on this mission. The drone's AI is set at the lowest possible level, Coward, but there's a lot of them. You may want to stay a bit behind your wingmen so you won't take the brunt of the fire.

It's extremely difficult to catch Long John wing. There's a secondary goal that becomes true when Long John is destroyed, but this is pretty much impossible, and even if you destroy the whole wing it says nothing about it in your debrief. You will, however, get a bit of recognition for destroying at least one of the fighters. If you set engine power to max and head to the node before Long John arrives, you may be able to catch one or two Ares, but it's not worth it if the convoy gets destroyed.

--

You finally get a decent weapon to work with, in the [[Prometheus S]]. Definitely bring one in the four-gun bank of your Myrm. Other than that, a mix of Tempests and Rockeyes is recommended.

From the mission start, afterburn towards your two charges at maximum engine power, and you should catch up easily before anything important happens. During or shortly after your sprint, you'll see the friendly merc wing tussle with some pirates, but these are none of your concern.

Instead, you will shortly be set upon by rather a lot of Lokis, arriving in groups of four with little to no break in between. Keep yourself and your wingmen close enough to the two civilians that you can get there fast if needed, but otherwise feel free to engage them as they seem to target your wing rather than the ships you are protecting. While they make easy targets even on high difficulties, try to avoid getting into head-to-head passes with them as they can still do damage there. And the Myrmidon is a big target.

Eventually, Long John wing will arrive near the node and make a run for it, but trying to catch them while also keeping the convoy alive is an excersise in futility, as a wing of pirate Hercules fighters will arrive at about the same time. And unlike the Lokis, these DO target your civilians and can make short work of them if left unattended. If you do want to try though, save a bunch of Rockeyes and use those from long range before turning back to help. As the Long John wings are flying in a straight line and won't do any evading, you ''might'' bag one that way and still make it back before your civilians go boom.

==Notes==

==Notable ships present==

* [[GTC LoneWolf]]
* [[TRGC Sai]]
* [[TRGS Meridian]]
* [[TRGF Haulian]]

A Time for Penance

2011-02-10T12:25:13Z

Shade: /* Walkthrough */ - More detailed walkthrough

{{Derelict}}

{|- cellpadding="8" style="background:#000000;" align="center"
| [[Derelict Campaign Walkthrough|Campaign Walkthrough]]
| [[Bait and Switch|Previous Mission]]
| [[The Horror in the Deep|Next Mission]]
|-
|}

ACT 1 MISSION 7

Fighter squadron: [[212th Silver Scythes]] 
Description: After a botched raid on what turned out to be a civilian operation, Alpha Wing must escort two research vessels to the Tau Jump Node. A pirate attack is almost certain.

----

== Command Briefing ==

* Command Incident Report 08/28/2372 1510

After acting out on what we thought was accurate intelligence, Alpha wing and the GTC LoneWolf led a raid on what turned out to be a civilian operation.

In the attack, the GTC LoneWolf engaged the TRGC Sai, damaging it. Fortunately we managed to stand down before an attack group of pirates arrived for the clean-up.

Still, the Sai and the LoneWolf were damaged enough that they are now in repair.

*
The Tepoheh Raleigh Group has launched a formal complaint along with the Morgan Mining Corporation. They're saying the GTVA is incapable of providing security in the outer territories. This is especially pressing now that we have recieved word that one million Capellan refugees are coming our way.

End of Incident Report

Alright pilot, we've got our work cut out for us. A lot of people are mad at us, but it's not our fault, and we still have a job to do. Report to briefing.

==Background==

*While the GTC LoneWolf and the TRGC Sai are in repair at Tau Sigma Station, the TRGS Meridian and the TRGF Haulian demanded to return to their office on Altair. Until we hear otherwise, we are still responsible for their safety.
*Alpha wing, it is your job to make sure that the Meridian and the Haulian reach the Altair jump node in one piece. They are carrying research materials that would fetch a high price on the black market.
*Alpha, you will fly close escort to the Meridian. The Morgan Mining Corporation has contracted mercenaries, designated Tachyon wing, to fly patrol. They are not under our command. You are NOT to engage them.
*Given the recent attacks, another pirate raid is almost certain. Be on your guard, and good luck pilot.


==Walkthrough==

A fairly challenging one. You will encounter a lot of Lokis on this mission. The drone's AI is set at the lowest possible level, Coward, but there's a lot of them. You may want to stay a bit behind your wingmen so you won't take the brunt of the fire.

It's extremely difficult to catch Long John wing. There's a secondary goal that becomes true when Long John is destroyed, but this is pretty much impossible, and even if you destroy the whole wing it says nothing about it in your debrief. You will, however, get a bit of recognition for destroying at least one of the fighters. If you set engine power to max and head to the node before Long John arrives, you may be able to catch one or two Ares, but it's not worth it if the convoy gets destroyed.

--

You finally get a decent weapon to work with, in the [[Prometheus S]]. Definitely bring on in the four-gun bank of your Myrm. Other than that, a mix of Tempests and Rockeyes is recommended.

From the mission start, afterburn towards your two charges at maximum engine power, and you should catch up easily before anything important happens. During or shortly after your sprint, you'll see the friendly merc wing tussle with some pirates, but these are none of your concern.

Instead, you will shortly be set upon by rather a lot of Lokis, arriving in groups of four with little to no break in between. Keep yourself and your wingmen close enough to the two civilians that you can get there fast if needed, but otherwise feel free to engage them as they seem to target your wing rather than the ships you are protecting. While they make easy targets even on high difficulties, try to avoid getting into head-to-head passes with them as they can still do damage there. And the Myrmidon is a big target.

Eventually, Long John wing will arrive near the node and make a run for it, but trying to catch them while also keeping the convoy alive is an excersise in futility, as a wing of pirate Hercules fighters will arrive at about the same time. And unlike the Lokis, these DO target your civilians and can make short work of them if left unattended. If you do want to try though, save a bunch of Rockeyes and use those from long range before turning back to help. As the Long John wings are flying in a straight line and won't do any evading, you ''might'' bag one that way and still make it back before your civilians go boom.

==Notes==

==Notable ships present==

* [[GTC LoneWolf]]
* [[TRGC Sai]]
* [[TRGS Meridian]]
* [[TRGF Haulian]]

Bait and Switch

2011-02-08T15:06:40Z

Shade: /* Walkthrough */ - More detailed walkthrough

{{Derelict}}

{|- cellpadding="8" style="background:#000000;" align="center"
| [[Derelict Campaign Walkthrough|Campaign Walkthrough]]
| [[Last Leg|Previous Mission]]
| [[A Time for Penance|Next Mission]]
|-
|}

ACT 1 MISSION 6

Fighter squadron: [[212th Silver Scythes]] 
Description: Alpha and the LoneWolf attack a pirate base, but things are not as they seem...

----

=== Background ===

*With some help from the MMC's scans of the area, and from this latest attack near Tau Sigma Station, we now know that the pirates staged their raid from this remote location within the Tau Sigma system. If we move quickly, we may be able to surprise them, re-capture any stolen goods, and restore the confidence of the local business operations.
*The staging area is located on the outer rim of the system near a large ice debris belt. Central to the area is a large refuelling vessel along with several cargo containers and a Triton class freighter.
*Guarding the area is a Gunship of unknown configuration. There are at least two wings of fighters flying escort. These will be your primary target.
*Alpha wing and the GTC LoneWolf will jump in at close range for the element of surprise. Alpha, your primary target will be the fighter escort, while the LoneWolf will concentrate on neutralizing the gunship. Once disabled or destroyed, we should have little trouble apprehending the rest of these pirates. Good luck, pilot!

==Walkthrough==

Your first challenge of the campaign. Don't worry about killing the enemy fighters at the mission start, as they will soon turn friendly when Command recognizes its mistake. The pirates will then launch a massive fighter/bomber/cruiser attack on the LoneWolf. The Fenris is not nearly strong enough to withstand the assault, so you will probably have to loose the mission 5 times and then skip, unless you're playing on low difficulty.

Excellent voiceacting and script on this one.

--

As mentioned above, this is quite a tough mission. However, it is quite possible to beat it even on higher difficulties.

For loadout, you'll want a mix of tempests and rockeyes (with at least eight of the latter), plus whichever guns you prefer - not that you have a whole lot of choice there.

From the beginning of the mission, order your wingmen to ignore both Sai and the medical frigate, and then you can either fly around dodging the initial fighters for a few minutes until they change IFF, or you can start fighting them properly. Save your rockeyes regardless of which you choose. If you do the latter, you will get more kills, but the second part of the mission will be harder. If you can't seem to get past the second part, simply have your AI wingmen ignore ALL enemy fighters at the start and simply evade, and that should help some later.

Either way, it will eventually turn out that the supposed pirate staging ground was in fact no such thing, and the remains of the enemy will turn friendly. This is where it gets interesting. A pirate Leviathan accompanied by both fighter and bomber wings will jump in, with the bombers heading for Sai while the cruiser tends to duke it out with LoneWolf. The safest solution here is to order your wingmen to guard Sai, while you use your rockeyes to destroy the main beam of the cruiser from a safe distance and then hang back outside of beam range. You really do NOT want to get into AAA range of a Leviathan if you're playing on hard or above, as it can swat you out of the sky in an instant should it target you.

Feel free to engage any enemies which stray far enough from the cruiser for you to safely engage them, but at this point, you should mostly be directing your wingmen. When no bombers are left in the area, have the wingmen engage the pirate cruiser, or guard the LoneWolf if her hull is getting too low for comfort. Eventually, the cruiser will die (with no main beam, LoneWolf and Sai between them outmatch it easily) and you can mop up any remaining pirate fighters. Congratulations, you've won.

==Notes==

==Notable ships present==

* [[GTC LoneWolf]]
* [[TRGC Sai]]
* [[TRGF Haulian]]
* Redbeard (pirate [[GTC Leviathan|Leviathan]])
* [[TRGS Meridian]]

Last Leg

2011-02-06T21:56:25Z

Shade: /* Walkthrough */ - More detailed walkthrough

{{Derelict}}

{|- cellpadding="8" style="background:#000000;" align="center"
| [[Derelict Campaign Walkthrough|Campaign Walkthrough]]
| [[Through the Looking Glass|Previous Mission]]
| [[Bait and Switch|Next Mission]]
|-
|}

ACT 1 MISSION 5

Fighter squadron: [[212th Silver Scythes]] 
Description: Alpha completes the deployment of the beacons and fends off another pirate attack on Morgan freighters - BR

----

==Background==

*You're almost done, pilot. We trust that you're not having too many bad dreams in the sleep stages of your mission. Unfortunately, nightmares are an occassional side effect of deep space sleep. If you've had problems, you can see the station physician about them when you return to base.

:Now, down to business... We seem to have encountered a situation at your next destination. Two Morgan Mining freighters have jumped in too close to the asteroid field you're about to mark. Lack of navigational data is proving to be a liability.

:We have also picked up some transmissions from within the belt - it seems like you're flying into a pirate ambush. Be on your guard. While you will still lay the navigational buoys, your first task will be to guard the freighters by elminating any pirates, and clearing a path for them through the asteroid field.

:Once they have jumped to safety, you will then continue your mission to lay the navigational beacons.


==Walkthrough==

You'll encounter two wings of pirates on this mission making an attack on the Morgan Technologies freighters. They're Ulysses and should be easy kills. Even if the freighters are destroyed, you can still win the mission.

The fourth and final mission in this red alert chain, and the one you've been saving your missiles for up until now. The moment you get into the mission, start afterburning towards the two Triton freighters. While underway, check to see which is being targeted by the pirate attack wing, and order your wingmen to guard it.

Once you get within two clicks or so of the freighters, break off and intercept the pirates while your wingmen continue on to take up guard positions. The pirates are flying [[GTF Ulysses]] fighters, and as such will make most annoying targets on higher difficulties, but once hit they do go down fast. Your goal on the first pass with them is to distract as many of them as possible from their target and convince them to instead chase you - If you can manage to get two to break off, easily accomplished with a volley of Tempests and primaries to each, your wingmen should easily be able to keep the targeted freighter in good health. Once the first wave is dealt with, another four Ulysses will jump in, but these are simpler to deal with as you are already in position around the freighters.

When all pirate fighters are gone, your next job is to get the freighters through the asteroid field. Or rather, your job is to get '''''one''''' of them through (De Leon), as the other (Benzia) will suffer a malfunction and go kaboom no matter what you do. Help De Leon through the field and watch it jump, then deploy the buoys. After all, that's why you came here in the first place. With all that done, jump back home for a well deserved rest.

==Notes==

==Notable ships present==

Marie Celeste

2011-02-06T21:45:11Z

Shade: /* Walkthrough */ - More detailed walkthrough

{{Derelict}}

{|- cellpadding="8" style="background:#000000;" align="center"
| [[Derelict Campaign Walkthrough|Campaign Walkthrough]]
| [[The Deep Patrol|Previous Mission]]
| [[Through the Looking Glass|Next Mission]]
|-
|}

ACT 1 MISSION 3

Fighter squadron: [[212th Silver Scythes]] 
Description: Alpha continues their beacon deployment, and encounters a derelict ship along the way - BR

----

==Background==

* Okay, pilot, that first leg went reasonably smoothly. No surprises on the next stage of the journey. You are to place two navigational beacons in this area, and investigate any anomalies. We are reading some low power fluctuations in this sector, but nothing is else is known. Keep a sharp lookout.

:Once you have completed this leg, you will go into your sleep stage while your wingmates take the next shift.


==Walkthrough==

No combat in this mission, again. Deploy the nav buoys and follow orders. You'll encounter an unidentified derelict ship, but it has no future significance in the main plot.

The second mission in a red-alert mission chain. Once again, no threats other than asteroids. And once again, don't waste your missiles. This time round, you also get to scan a derelict ship and watch a boarding operation.

==Notes==

The [http://en.wikipedia.org/wiki/Mary_Celeste Mary Celeste] is a famous ghost ship.

==Notable ships present==

* Unidentified ([[GVFr Satis]])
* Omaha ([[GTT Elysium]])

The Deep Patrol

2011-02-06T21:42:47Z

Shade: /* Walkthrough */ - More detailed walkthrough

{{Derelict}}

{|- cellpadding="8" style="background:#000000;" align="center"
| [[Derelict Campaign Walkthrough|Campaign Walkthrough]]
| [[Welcome to the Boonies|Previous Mission]]
| [[Marie Celeste|Next Mission]]
|-
|}

ACT 1 MISSION 2

Fighter squadron: [[212th Silver Scythes]] 
Description: Alpha wing deploys nav beacons across Tau Sigma - BR

----

==Command Briefing==

*Tau Sigma Station
:Fortnight Update
I trust you are settling in well, pilot, now that you have been with us for more than two weeks. To be honest, aside from the recent excitement with the Blackbeard pirate raid near the Station, not much else happens out here. You're about to get a taste of the less exciting parts of life in the boondocks. Unfortunately, I am not much for motivational speeches, especially when we have work that needs to be done.
Welcome to Deep Patrol duty. You can thank me later.

* Tau Sigma Wildernesse

While Tau Sigma has been settled as a mining colony for over fifteen years, very little of the system has been marked for navigation. As a result, there are many hazardous regions of the star system that require navigational beacons, to ensure safe passage in these areas. Until now, only a small number of beacons have been set around the system. They mark the critical commercial lanes, particularly near the mining operations. However, GTVA Command informs us that in the coming months, the traffic to Tau Sigma will increase significantly. There is a need to step up the schedule of navigational beacon deployment.

Report to briefing for your specific assignment.

==Background==

*With a recent shipment of Mark IV Pharos-Class navigational systems, we are ready to proceed with their deployment as soon as possible. Your Myrmidon fighters are being modified to carry several of these beacons. They will become available to deploy under your control when you reach the designated area for that marker. In order to make room to carry these navigation beacons, your primary weapons have been limited, and your secondary banks have been reduced in capacity.
*Due to the length of this mission, you and your wingmates will be flying in shifts. You will take turns sleeping as you make your patrol rounds. While asleep, your navigation systems will be locked into your wingmates'. In the event of any danger, you will be automatically alerted, and your systems brought online.
*Each fighter wing has been assigned to lay markers in three different locations in the star system. Alpha, your task is simple. In each designated area, you are to make a clean sweep, noting any hazards, and dropping the navigational beacon in their appropriate area. Your onboard computer will automatically determine the best location for deployment, marking it with a computer-generated Pharos beacon on your HUD.
*Our knowledge of these areas is very limited, Alpha. The Mark IV Pharos beacons have two functions - to transmit navigational data, but also to provide limited sensor scans of their immediate area. Once this is all over, we hope to make Tau Sigma much more accessible to those wishing to develop this region.
*On the first leg of your patrol, you will be placing beacons near an ice-belt further out of system. If we are lucky, these beacons may be able to use the reflective surfaces of the ice-belt to amplify their own scanning range. Once you successfully place the beacons, your computer will automatically download the next stage of your mission. Despite your remote location, you are still well within communication range of Tau Sigma Station. Command will be monitoring your progress.

:Good luck, pilots.

==Walkthrough==

No combat in this mission. Drop the nav bouys and continue on. Derelict was the very first campaign to really use this linked-mission idea. It made the red-alert SEXP seem even more useful.

The first in a moderately long chain of red-alert missions. The only threat in this mission is accidentally bumping into asteroids. With a bit of care, you should move on to the next mission with 100% hull. Don't waste any missiles taking potshots at the asteroids, as you will need them later on in the chain.

==Notes==

==Notable ships present==

Welcome to the Boonies

2011-02-06T21:40:22Z

Shade: /* Walkthrough */ - More detailed walkthrough

{{Derelict}}

{|- cellpadding="8" style="background:#000000;" align="center"
| [[Derelict Campaign Walkthrough|Campaign Walkthrough]]
| [[The Deep Patrol|Next Mission]]
|-
|}

'''ACT 1 MISSION 1'''

'''Fighter squadron:''' [[212th Silver Scythes]]

'''Description:''' Alpha wing patrols the area around Tau Sigma Station, and meets their first pirate wing - BR

----

==Command briefing==

*'''Aftermath'''

Five years have passed since the jump nodes to the Capella system were collapsed, sealing off a massive wave of Shivan juggernaughts and preventing them from pushing further into GTVA space. The supernova and subsequent nebula hang like a growing scar throughout the GTVA as light from that event continues to spread across our worlds.

*'''The Ripple Effect'''

The loss of Capella created serious economic hardship throughout the Alliance - a new Great Depression is upon us. The complete loss of the planetary resources and economic foundation of a rich world was devastating in its own right, but that is not all. Two hundred million refugees continue to walk the stars, seeking a new home. Some have settled, while others have been forced to move from place to place, hoping that the next place may welcome them with open arms.

*'''The Fall of Reason'''

While the Galactic Terran-Vasudan Alliance continues to hold, the current depression has given way to political instability. Local governments rise and fall as often as lunar tides, organized crime and piracy have prospered in a black market environment. It seems no one is immune. Radical voices are raising echoes not heard since the blood cries of the Neo-Terran Front. The ghosts of the past are catching up with us.

*'''Response of the Alliance'''

Since collapsing the Capella jump nodes, the recovering GTVA fleets have spent much of their time and resources in police actions. Our own resources are taxed to the limit, and yet still we have the courage to live up to our calling. Even so, it is alarming that there are those who are starting to take matters into their own hands.

*''' Problems and Difficulties'''

This is not an easy assignment, pilot. You will often be working in less-than-ideal conditions, but we trust that your skill will help to bring some much needed relief to this region.

==Background==

*Welcome to the '''Tau Sigma''' mining colonies, pilot. We are the boondocks at its finest. You may be used to high tech fighter wings and the latest weaponry where you come from, but now it's time to forget all of that. It is a poor space jockey that blames their lack of skill on their equipment.

*'''Alpha''' wing will be flying a routine patrol with the '''GTC LoneWolf''', a Great War vintage cruiser. She may not look like much, but she has a proud heritage.

*'''Tau Sigma Station''' functions as a receiving point for both inbound materials, and outgoing mined ores. The minerals in this region include high grade fissionables, and are valuable in many parts of the '''Alliance'''. The '''Morgan Mining Company''' has been the first to develop the '''Tau Sigma''' resources for shipments to '''Altair''' and ''Aldebaran'''.

*Your job is to make sure all shipments go smoothly. Keep an eye out for '''pirates'''. We are not well armed, so you may be forced to rely on your skill and wits. Good luck, pilot.

==Walkthrough==

The first mission of Derelict. You'll get introduced to [[Mackie]], the character who Snipes was supposed to be. Fly around and look at the pretty nebulae, this is the first mission, no challenge.

To save everything (which is not required to win the mission, nor is even recognized, but feels good), send your wingmen off to protect the two far-off Tritons while you go hang near the station. Don't bother actually guarding the LoneWolf, as it will not come under attack. When you get the objective to scan the Poseidon 7 freighter, do so, and then immediately destroy it when it turns hostile.

Meanwhile, enemies will be attacking the two Tritons you send your wingmen to guard earlier, and will be easily held off by them while you cover the distance to join them. If you max out engine power and afterburn as much as possible, you should just arrive in time to grab a fighter kill before the hostiles are wiped out and the mission is over. Make sure the hostile Triton dies, either by your hand or by ordering in your wingmen while you are still in underway - They can easily handle it.

Alternatively, you can keep your wingmen with you and let the two Tritons die, which is probably what your are 'supposed' to do, and then hightail it there and kill the enemies after the fact. This will let you get more kills as your wingmen haven't done most of the work by the time you get there. As long as you manage to kill the hostile Triton, you won't get in any trouble for losing the two friendly freighters, as they were never really intended to be saved.

==Notes==

==Notable ships present==

Screenshots

2011-01-23T14:45:32Z

Shade: Added an image

<gallery widths=150px perrow=5>
File:RScreen0001.jpg|The bow of a mighty [[GTD Orion]].
File:RScreen0002.jpg|A [[GTF Pegasus|Pegasus]] pursued through the Nebula.
File:RScreen0003.jpg|The [[GTC Fenris]].
File:RScreen0004.jpg|The deadly, nigh-invulnerable [[SD Lucifer]].
File:RScreen0005.jpg|The most vital mission of [[The Great War]] launches from the [[GTD Bastion]]
File:RScreen0006.jpg|A [[GTD Orion]] approaching an inhospitable planet.
File:RScreen0007.jpg|Activity around [[Earth]].
File:RScreen0008.jpg|The Colonial Bolitho from the [[Diaspora]] Battlestar Galactica TC for FreeSpace Open.
File:RScreen0009.jpg|A [[Terran]] fleet, in green.
File:RScreen0010.jpg|The [[GTVA]] fleet from the [[Blue Planet: Age of Aquarius]] campaign.
File:RScreen0011.jpg|Three [[GVF Thoth]]-class fighters flying in formation.
File:RScreen0012.jpg|An [[Ancient]] vessel from the [[Ancient-Shivan_War_(campaign)|Ancient-Shivan War]] campaign.
File:RScreen0013.jpg|A Cylon Raider from the [[Beyond the Red Line]] demo.
File:RScreen0014.jpg|The [[SD Ravana]] hides in the [[Nebula System|nebula beyond Gamma Draconis]].
File:RScreen0015.jpg|A [[GTF Ulysses]] in the [[Sol]] system.
File:RScreen0016.jpg|The [[GVI Karnak]].
File:RScreen0017.jpg|The [[GTC Fenris]] on patrol.
File:RScreen0018.jpg|The [[GTC Aeolus]].
File:RScreen0019.jpg|Three [[SB Seraphim|Seraphim-class bombers]] emerge from subspace.
File:RScreen0020.jpg|A Shivan [[SD Ravana|Ravana]] meets its end.
File:RScreen0021.jpg|A lone [[GTF Loki]] in the dark of space.
File:RScreen0022.jpg|Ships from the [[Blue Planet]] mod near Saturn.
File:RScreen0023.jpg|The [[SD Lucifer]] in the [[Ribos]] system.
File:RScreen0024.jpg|The GTCv Warspite from the mission [[Battle of the Wilderness]].
File:RScreen0025.jpg|Admiral Koth engages the [[GTVA Colossus]].
File:RScreen0026.jpg|The GTCv Parapet from the mission [[Into the Maelstrom]].
File:RScreen0027.jpg|Fighting the [[Shivans]] in the [[Homesick]] campaign.
File:RScreen0028.jpg|The [[SJ Sathanas]] makes its way inexorably towards [[GTVA]] space.
File:RScreen0029.jpg|A pitched battle from [[The Procyon Insurgency]].
File:RScreen0030.jpg|Combat in the [[Earth Defense]] campaign.
File:RScreen0031.png|Boom!
File:RScreen0032.png|The [[FreeSpace_2_Terran_Ship_Database#GTD_Carthage|GTD Carthage]], the [[FreeSpace_2_Vasudan_Ship_Database#GVCv_Dahshor|GVCv Dahshor]], and some bloom.
File:RScreen0033.png|Limited visibility
File:RScreen0034.png|The [[NTD Repulse]] swats a fly- err, fighter.
File:RScreen0035.png|Feint, Parry, Riposte!
File:RScreen0036.png|The NTF Iceni and my horrendously dark lighting settings.
File:RScreen0037.png|The bloomiest ship in the NTF Armada.
File:RScreen0038.png|Love the Treason...
File:RScreen0040.png|The Bloom capabilities of newer FreeSpace Open builds demonstrated beautifully with an atmospheric skybox.
File:RScreen0041.jpg|A lone [[GVCv Sobek]] cruises through space.
File:RScreen0042.jpg|A Terran Gas Refinery in the upper atmosphere of an Epsilon Pegasi gas giant.
File:RScreen0043.jpg|A [[GTD Orion]] watches over a busy installation.
File:RScreen0044.png|The mighty [[GTVA Colossus]].
File:RScreen0045.jpg|The [[FreeSpace_2_Terran_Ship_Database#GTD_Carthage|GTD Carthage]] dwarfs the [[FreeSpace_2_Vasudan_Ship_Database#GVCv_Dahshor|GVCv Dahshor]].
File:RScreen0046.png|A [[GTF Hercules Mark II|Herc II]] fighter defending a [[GTCv Deimos]].
File:RScreen0047.png|The end of the [[GTVA Colossus]] courtesy of SJ Sathanas 17, with the latter's main beams causing blowouts in the Allied warship's hull.
File:RScreen0048.png|A lone jetpacker trails a little-known alien species in an alien system.
File:RScreen0049.png|A [[GTCv Deimos|Deimos]], off in the distance.
File:RScreen0050.png|The [[NTF Iceni]], charging its frontal beams.
File:RScreen0051.png|In an alternate universe, the Lucifer as we know it is engaged by the GTVA and [[Vishnans]] in Delta Serpentis.
File:RScreen0052.png|A wing of [[SF Manticore|Manticore fighter]]s fly through a flak cloud.
File:RScreen0053.png|An [[SD Ravana]], demonstrating a shock-jump attack.
File:RScreen0054.png|A combination of good lighting, background and normal maps makes this [[GTF Perseus|Perseus interceptor]] look pretty even from the underside.
File:RScreen0055.jpg|A Vasudan asteroid base in [[Deneb]], during the 14 year war.
File:RScreen0056.jpg|Aesdherian capital ships from the [[Ancient-Shivan_War_(campaign)|Ancient-Shivan War]] campaign, moving to defend their homeworld.
File:Rscreen0057.jpg|A European battle fleet in formation over Scandinavia in [[Wings]].
File:RScreen0058.png|A large dogfight in the BSG-themed [[Diaspora]] total conversion.
File:RScreen0059.jpg|A Viper Mk7 heading towards two Basestars in the BSG-themed [[Diaspora]] total conversion.
File:RScreen0060.jpg|Viper squadron launching a missile barrage in the BSG-themed [[Diaspora]] total conversion.
File:RScreen0061.png|Cylon Raider trying to escape a Flak barrage in the BSG-themed [[Diaspora]] total conversion.
File:RScreen0062.png|Cylon Raider with a Colonial Bolitho-class corvette as seen in the BSG-themed [[Diaspora]] total conversion.
File:RScreen0063.png|Colonial Sobek-class battlestar as seen in the BSG-themed [[Diaspora]] total conversion.
File:RScreen0064.png|Colonial Sobek-class battlestar as seen in the BSG-themed [[Diaspora]] total conversion.
File:RScreen0065.png|Colonial Sobek-class battlestar as seen in the BSG-themed [[Diaspora]] total conversion.
File:RScreen0066.jpg|A [[GVD Hatshepsut]] leads a Vasudan battlegroup through the darkness.
File:RScreen0067.jpg|A massive Terran installation in orbit of Earth.
File:RScreen0068.png|The [[GTD Orion]] passes an inhabited Terran world.
File:RScreen0069.jpg|The [[GVD Hatshepsut]], in all its glory.
File:RScreen0070.png|A [[GTF Pegasus|Pegasus-class stealth fighter]] in the [[Vassago's Dirge]] campaign.
File:RScreen0071.jpg|An [[GTD Orion|Orion]]-class Destroyer.
File:RScreen0072.jpg|The GTD Neya, an [[GTD Orion|Orion]]-class Destroyer.
</gallery>
[[Category:Images]]

Screenshots

2011-01-23T13:39:23Z

Shade: Added an image

File:RScreen0071.jpg

2011-01-23T13:28:52Z

Shade: Orion-class Destroyer

Orion-class Destroyer

Template:Featured Campaign

2011-01-10T17:26:57Z

Shade: and fixed a link

{| border=0 align=left cellpadding=4 cellspacing=0 width=65% style="margin: 0 0 0 0; background: #000; border: 1px #AA2020 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #512020; 70%; font-size: 125%;"|''[[Ancient-Shivan War (campaign)|Featured Campaign of the Moment]]''
|-
| align="left"|
{|border=0 cellpadding=4 cellspacing=0 style="margin: 0 0 1em 1em; background: #000; border: 0px #000 solid; border-collapse: collapse;"
|-
| align="left"|

[[Image:ASW.jpg|center|480px|Ancient-Shivan War (campaign)]]

''The Ancient-Shivan War takes place in the distant past, putting the player in the role of one of the many Ancients as they fight desperately, and ultimately futilely, to save their empire and home from the Shivans. The player has the opportunity to pilot numerous Ancient ships as they take their part in the epic struggle for survival. 

Released on December 28th 2009, the Ancient-Shivan War is a take on the grand conflict which forms such a large part of the the background of the FreeSpace universe. It is said to have a very different feel and atmosphere to most campaigns, and features new effects, interface, ships and more, making it essentially a total conversion rather than a 'mere' mod. The first act has recently been updated for compatibility with FreeSpace_Open v3.6.12. ([[Ancient-Shivan War (campaign)|more...]])
|-
|}
|}

<noinclude>[[Category:Templates|Featured Campaign]]</noinclude>

Template:Featured Campaign

2011-01-10T17:24:39Z

Shade: Changed the campaign

{| border=0 align=left cellpadding=4 cellspacing=0 width=65% style="margin: 0 0 0 0; background: #000; border: 1px #AA2020 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #512020; 70%; font-size: 125%;"|''[[Blue Planet|Featured Campaign of the Moment]]''
|-
| align="left"|
{|border=0 cellpadding=4 cellspacing=0 style="margin: 0 0 1em 1em; background: #000; border: 0px #000 solid; border-collapse: collapse;"
|-
| align="left"|

[[Image:ASW.jpg|center|480px|Ancient-Shivan War]]

''The Ancient-Shivan War takes place in the distant past, putting the player in the role of one of the many Ancients as they fight desperately, and ultimately futilely, to save their empire and home from the Shivans. The player has the opportunity to pilot numerous Ancient ships as they take their part in the epic struggle for survival. 

Released on December 28th 2009, the Ancient-Shivan War is a take on the grand conflict which forms such a large part of the the background of the FreeSpace universe. It is said to have a very different feel and atmosphere to most campaigns, and features new effects, interface, ships and more, making it essentially a total conversion rather than a 'mere' mod. The first act has recently been updated for compatibility with FreeSpace_Open v3.6.12. ([[Ancient-Shivan War|more...]])
|-
|}
|}

<noinclude>[[Category:Templates|Featured Campaign]]</noinclude>

Talk:Main Page

2010-12-26T00:36:34Z

Shade: Reply to Scourge of Ages

The Die is Cast (Multiplayer Mission)

2010-12-23T22:06:16Z

Shade: Walkthrough for first half of mission, some loadout advice

'''Medal given:''' SOC Service Medallion.

'''Minimum difficulty for medal:''' Hard.

----

==Background==

Operation Alea Iacta Est. You are members of a SOC team ordered to capture NTF Rear Admiral Vidar under all circumstances.

==Walkthrough==

'''Important Note: Initially, everything is peaceful in this mission. Do not shoot at anything until things go hostile unless your job specifically requires it, or you may cause an instant mission failure.'''

For much of this mission, your force will effectively be split into a Fighter force and a Bomber force, each with their own objectives as described below.

While it is peaceful at the start of the mission, one Fighter equipped with a Maxim and Trebs should scan the cargo of the two freighters heading away from the station, and then take out three specific AAA turrets on the station with its Maxim (and ONLY its Maxim. '''No missiles'''). This is the ONLY ship allowed to fire before the battle is joined, and only at these specific targets as it will not cause the enemies to go hostile if done right. The turrets to take out are the following:

* One near the radar dish
* One just above the hole in the Arcadia
* One just above the fighter bay

Following this, the same Fighter should take up position near the fighter bay and wait for the arrival of an Argo transport. Note that this may arrive before you get there, but that's ok as long as you can catch up.

While all this is taking place, Bombers should rush to take up positions near the Orion (near the engine subsystem is a good spot). As soon as hostilities commence, their job is to kill that Orion as close to instantly as they can possibly manage. Failure to do this makes the mission significantly harder.

Once Bombers are in position and the Fighter mentioned above is trailing its Argo, that fighter will open hostilities by disabling the Argo. Two pairs of dumbfired Trebs into the engine subsystem (switch banks to launch the second pair faster), plus a little Maxim fire, is enough to stop it dead in a few seconds. As soon as this happens and everything goes hostile, the Bomber force must Helios the Orion into vapour. The Orion will launch escape pods, which must be destroyed quickly - If left alone for a little while, they jump out and you lose the medal. Trebs and Maxims work well.

Following the death of the Orion, there are three potential targets remaining for the Bombers. Two Deimos-class corvettes, of which one is moving and one is stationary, and the Arcadia installation. The first target is the Arcadia. Concentrate on it until it launches escape pods, and then, as with the pods from the Orion, get them fast - These too will jump. Once the station dies, the last target in this part of the mission is the moving Deimos. Do not touch the stationary one, or you will be in serious trouble later.

Meanwhile, the Fighter force will be working to disable the Argos which have been appearing. All of them must be disabled and then left alone, though disarming is also a good idea as they carry flak - Just be very careful when disarming so as not to accidentally destroy a transport. When no transports are in need of attention, disarming any live warships as well as general fighter suppression are the orders of the day.

When the area is clear except for the stationary and by now hopefully completely disarmed Deimos (again, do NOT kill), scan the Argos and ''carefully'' disarm them is that hasn't been done already.

==Tips==

*Loadout advice: Most people should be assigned to the Bomber force, which will NOT be flying bombers. Instead, they will want Myrmidons with Helios for the capitals and at least one bank of Trebs for the escape pods. Fighters (only two needed) should grab an Erinyes, at least one of which should bring a Maxim and two banks of Trebs for the disarming of the first Argo.

==Notes==
* The SOC Service Medallion is regarded by several veteran pilots to be the most difficult multiplayer medal to obtain.

==Key Ships==

Insert list of key ships in the mission here.

==Technical information==
{{MissionInfo|Filename|File Size|Author|Number of objects|Number of wings|Number of events|Number of messages|Mission Music|Briefing Music}}

[[Category:Multiplayer Medal Missions]]

TBP shiplist

2010-10-17T11:33:31Z

Shade: Unprotected "TBP shiplist": Unprotected

{{TBP}}

==EA Ships==
===Fighters===
*[[EA Aurora]]
*[[EA Tiger]]
*[[EA Aurora Mk I]]
*[[EA Escort Aurora]]
*[[EA Badger]]
*[[EA Thunderbolt]]
*[[EA 109 Zephyr]]
*[[EA PSI Aurora]]
*[[EA PSI Thunderbolt]]
*[[EA Valkyrie]]

===Capital Ships===
*[[EA Olympus]]
*[[EA Hyperion]]
*[[EA Midwinter]]
*[[EA Nova]]
*[[EA Omega]]
*[[EA Poseidon]]
*[[EA Warlock]]
*[[EA Omega-X]]

===Stations===
*[[EA Orion]]
*[[EA Babylon 5]]
*[[EA G.O.D. Satellite]]
*[[EA Defense Platform]]
*[[EA Asteroid Base]]

===Misc Ships===
*[[EA Explorer]]
*[[EA Kestrel]]
*[[EA Skylark]]
*[[EA Freighter 1]]
*[[EA Freighter 2]]
*[[EA Tanker]]
*[[EA Breaching Pod]]
*[[EA Crew Shuttle]]
*[[PSI Crew Shuttle]]
*[[PSI Commmand Ship]]
*[[Starliner Asimov]]
*[[Earth Force One]]

==Centauri Republic Craft==
===Fighters===
*[[CR Sentri]]
*[[CR Rutarian]]

===Capital Ships===
*[[CR Vorchan]]
*[[CR Primus]]
*[[CR Secundus]]

===Stations===
*[[CR Marcanos]]

===Misc Ships===
*[[CR Ritan]]
*[[CR Brezebel]]
*[[CR Scarab]]

==Narn Craft==
===Fighters===
*[[NR Frazi]]
*[[NR Gorith]]

===Capital Ships===
*[[NR G'Quan]]
*[[NR Bin'Tak]]
*[[NR Th'Nor]]
*[[NR T'Loth]]

===Misc. Ships===
*[[NR Freighter]]

===Stations===
*[[NR Defense Platform]]
*[[NR Ja'Stat]]
*[[NR Ja'Dul]]

==Minbari Craft==
===Fighters===
*[[MF Nial]]
*[[MF Tishat]]

===Capital Ships===
*[[MF Tinashi]]
*[[MF Sharlin]]

===Stations===
*[[MF Shn'Tan]]

===Misc. Craft===
*[[MF Lintira]]

==League Craft==
===Fighters===
*[[BI Falkosi]]
*[[BI Halik]]
*[[DF Sky Serpent]]

===Capital Ships===
*[[BI Tashkat]]
*[[DF Firehawk]]
*[[BI Avioki]]
*[[VF Xill]]
*[[VF Xorr]]

===Stations===
*[[League Base]]

==ISA Craft==
===Fighters===
*[[ISA Whitestar]]
*[[ISA Bluestar]]

===Capital Ships===
*[[ISA Victory]]

==Drakh Horde Craft==
===Fighters===
*[[DH Fighter]]
*[[DH Raider]]

===Capital Ships===
*[[DH Cruiser]]
*[[DH Destroyer]]
*[[DH Carrier]]
*[[DH Heavy Carrier]]
*[[DH Mothership]]

==Vorlon Craft==
===Fighters===
* [[VE Fighter]]
===Capital Ships===
* [[VE Cruiser]]
* [[VE Dreadgnouth]]
===Misc. Craft===
* [[VE Transport]]

The Babylon Project

2010-10-17T11:33:11Z

Shade: Unprotected "The Babylon Project": Unprotected

{{TBP}}

'''''The Babylon Project''''' (TBP) is a stand-alone total conversion based on the Babylon 5 universe created by J. Michael Straczynski. It features large amount of ship and different species from the Babylon 5 universe.

The Babylon Station is a dream given form. It is a 5 mile long space station built in neutral territory orbiting the planet of Epsilon 3. A place for commerce and diplomacy where diverse populations can gather calmly without the threat of war and discuss their differences with the hope of understanding each other and settling their disagreeements peacefully. But not all disputes can be solved peacefully...

The Babylon Project features over 120 Ships of over 11 species or factions including the Earth Alliance Omega Class Destroyer, the Centauri Primus Class Battle Cruiser or the Vorlon Star Dreadnought. It also features the latest effects from the Source Code Project (high detailed textures and graphics and the "Glide-Mode" for some fighters).
High quality soundeffects and the original soundtrack from the famous TV-show are also included.

A increasing number of fan-made campaigns and dozens of single player missions are available for download. Multiplayer missions and campaigns have been made too.

 
'''Release Info:'''
:[http://www.hard-light.net/forums/index.php/topic,51780.0.html The Babylon Project FINAL]

'''Homepage:'''
:[http://babylon.hard-light.net/ Link to TBP homepage]

'''Mods:'''
:[[TBP shiplist]]

[[Category:Total Conversions]]