FreeSpace Wiki - User contributions [en]

The King's Gambit

2013-11-01T11:49:08Z

FelixJim: /* Walkthrough */ You actually need to destroy more than half of the NTF ships

{{Mission|next=The Sicilian Defense|previous=Proving Grounds|campaign=FreeSpace 2 Campaign Walkthrough}}

'''ACT 2, MISSION 4'''

'''Fighter squadron:''' [[64th Raptors]]

'''Description:''' The GTVA 3rd Fleet and 11th Vasudan Battle Group blockade the [[Gamma Draconis]] jump node, destroying any NTF warship that enters.

----
==Background==
[[Aken Bosch|Admiral Bosch]] sends his forces on a charge to the [[Knossos]] subspace portal. The 3rd Terran fleet and 11th Vasudan Battle Group attempt to hold him off with the help of Alpha, Beta and Gamma wings from the 64th, as well as the combined firepower of four [[GTSG Mjolnir|Mjolnir remote beam cannons (RBCs)]].

==Walkthrough==
This is a bombing run mission. Your objective is to destroy at least 4 of the 6 hostile ships that jump in. The [[GTB Artemis]], armed with the [[GTW Prometheus S]] and three banks of [[GTM Cyclops]] is ideal for this mission, as the Artemis is the most maneuverable [[GTVA]] bomber you can use. A Vasudan [[GVD Typhon]]-class destroyer and several Mjolnir RBCs will assist you with their firepower.

Alternatively, you can choose a fighter from another wing and let your wingmen do the bombing runs. With good instructions, the RBCs, the Typhon and your wingmen can destroy the [[Neo-Terran Front|NTF]] ships without much difficulty. Hunt down fighters if you choose this path, and be sure to loadout with a bank of [[GTM Harpoon|Harpoons]].

The first NTF ship that arrives on the scene is the [[GTD Orion|Orion-class destroyer]] NTD Uhuru. You have to fire a few Cyclops at it to ensure its destruction. The Uhuru jumps in with a complement of [[GTF Hercules|Hercules fighters]] will head after the Mjolnir sentry guns. Your fighter assistance can handle them most of the time, but you should engage the NTF fighters after you have delivered a few bombs at the Uhuru. Losing the Mjolnir cannons or the Vasudan destroyer can mean a serious loss of firepower as you won't have the firepower to neutralize other enemy warships that jump in. If the Hedetet is destroyed, it will be replaced by other warships with inferior firepower.

Order your bomber wings to attack the next series of warships that jump in. The messaging system in FreeSpace 2 is a little rudimentary, so you will need to order them to destroy a warship every time one jumps in.

Damaging the engines of the warships immediately gains you more time before they jump out. If you manage to disable one of the warships, it will not be able to escape at all. Acquiring quick lock on a moving target with Cyclops requires time. If you practice more, and understand the targeting engine of FreeSpace, you will have the advantage.

==Tips==
* It is noted that when the Uhuru jumps in, it does so at a speed of over 150m/s, reaching its waypoint faster than the other ships. One way to take down this destroyer is to target its engines as soon as it jumps in, launch a salvo of Cyclops torpedoes and follow it. Alternatively, you can order your wingmen to destroy it for you.
* If you completed SOC Loop 1, you will also be given a choice to fly the [[GTB Artemis D.H.]] in this mission, on top of the other ships available for choice by default.

==Notes==
* This mission has the following glitches caused by using a pilot, created in FS2_Open 3.6.7 or older, in this mission on FS2_Open 3.6.9. You will need to downgrade your copy of FS2_Open, create a new pilot on FS2_Open 3.6.9, or make do with whatever you have, in order to rectify these problems. Keep in mind that creating a new pilot will cause you to lose all your progress.
** At times, the weapon selection screen may not offer bombs of any type, although missiles are still available;
** Odd readouts for secondary weapons;
** No simulated voice in the tech room.
* If any of the NTF ships escape, they will not make any further appearance in the campaign.
* In the event that the Hedetet is destroyed, more GTVA warships arrive to replace the destroyer, starting with the Unut, then the York and Warwick if the Unut is destroyed. Oddly enough, Command doesn't get upset if the Hedetet and its replacements get destroyed.

==Notable ships present==
* [[FreeSpace_2_Terran_Ship_Database#GTC_Warwick|GTC Warwick]]
* [[FreeSpace_2_Terran_Ship_Database#GTCv_York|GTCv York]]
* [[FreeSpace_2_Rebel_Ship_Database#NTC_Liberty|NTC Liberty]]
* [[FreeSpace_2_Rebel_Ship_Database#NTC_Undaunted|NTC Undaunted]]
* [[FreeSpace_2_Rebel_Ship_Database#NTCv_Pax|NTCv Pax]]
* [[FreeSpace_2_Rebel_Ship_Database#NTCv_Perseverance|NTCv Perseverance]]
* [[FreeSpace_2_Rebel_Ship_Database#NTD_Uhuru|NTD Uhuru]]
* [[FreeSpace_2_Rebel_Ship_Database#NTT_Inspiration|NTT Inspiration]]
* [[FreeSpace_2_Vasudan_Ship_Database#GVC_Unut|GVC Unut]]
* [[FreeSpace_2_Vasudan_Ship_Database#GVD_Hedetet|GVD Hedetet]]

==New equipment==
* [[GTB Artemis]]
* [[GTB Artemis D.H.]] if you complete SOC Loop 1
* [[GTW Prometheus S]]

==Technical information==
{{MissionInfo|SM2-04.fs2|70.7 KB|Brad Johnson|44 (+1 waypoint)|9|47|20|4: Numbers|Brief5}}

==Videos==
===QuantumDelta===
 <videoflash>meEgqEukNLQ</videoflash> 
===TheOneTrueRenairen===
 <videoflash>PBgdtoz1cYY</videoflash> 

[[Category:Main FreeSpace 2 Campaign]]

Modular Construction Kit

2013-05-07T22:15:05Z

FelixJim: /* Components */

{{User-made Ships|'''Modular Construction Kit'''}}

The '''Modular Construction Kit''' is a series of models designed to be docked together in FRED to produce larger structures, or to be added to existing models to add an addition level of detail or functionality.

==Components==

Currently, the kit contains the following pieces:

*A single girder "cell", for connecting other girders together.
*A five-cell girder.
*An eleven-cell girder.
*A twenty three-cell girder.
*A blank cap-plate for ending girders.
*A docking ring.
*A larger docking pad.
*A six way girder connector.
*An 'umbilical' tube, to either connect ships inside the drydock with the ouside world, or to run through girders as an access tube.
*A small umbilical piece, to connect larger umbilicals.
*A 90 degree bend, for turning corners with the umbilicals, and creating intersections.
*A cylindircal gas tank, with a set of "habitation pod"textures.
*A cargo docking platform.
*A Sensor Dish
*A Multi-Part Turret
*A set of Cables
*A Set of Solar Panels
*A Biodome
*A [[Cargo Platform]] (missing table)

==Current Status==
Version 1.2 of the kit has been released. Future releases will focus on modular installation type pieces, habitable pods, fighterbays, etc.

==Useful Links==
*Release Thread:
**[http://www.hard-light.net/forums/index.php?topic=74116.0 Release thread | Hard-light forums]
*Download Version 1.2:
**[http://www.freespacemods.net/download.php?view.875 Download | FSMods.net]
**[http://www.mediafire.com/?xhrz4dh5znndwxn Download | Mediafire]

==Gallery==
Here are some applications of the Kit in-game.

<gallery>
Image:MCKReinforcements.jpg | An exploration unit during the TV-War, for jumping fighters through nodes.
Image:MCKLeviDock.jpg | A Leviathan in a custom designed drdock.
Image:MCKOutpost.jpg | A small modular outpost.
Image:MCKCargoDepot.jpg | A large cargo depot, built with kit parts and utilizing texture replacement.
</gallery>

[[Category:User-made Ships]]

Cargo Platform

2013-05-07T22:14:08Z

FelixJim:

{{User-made Ships|''Cargo '''Platform'''''}} 

{{shipimage|image=[[Image:Platform.png|300px]]|caption=The Cargo Platform}}

The '''Cargo Platform''' is a small-capacity, stationary docking platform for cargo containers. 

==Description:==

===Tech Description===
None included

===Credits List===
*Model by '''[[User:Black Wolf|Black Wolf]]'''

===Designer's Comments===
This was released without a table file, but given the simplicity of the model, it's quite easy to make. Copy an existing table from, for example, a cargo container, give it a "drydock" flag, change the hitpoints and adjust the zoom position to something like 0, 0, 300. An up-to date version of the cargo platform is available as a part of the [[Modular Construction Kit]].

An example table:
<pre>$Name: Cargo Platform
$Short name: TPForm1
$Species: Terran
+Tech Description: Cargo Platform.
$end_multi_text
$POF file: Platform1.pof
$Detail distance: (0, 300, 500, 1300)
$Show damage: YES
$Density: 1
$Damp: 0.2
$Rotdamp: 0.2
$Max Velocity: 0.0, 0.0, 0.0
$Rotation time: 20.0, 20.0, 20.0
$Rear Velocity: 0.0
$Forward accel: 0.0
$Forward decel: 0.0
$Slide accel: 0.0
$Slide decel: 0.0
$Expl inner rad: 50.0
$Expl outer rad: 100.0
$Expl damage: 10.0
$Expl blast: 100.0
$Expl Propagates: NO
$Shockwave Speed: 0.0
$Default PBanks: ()
$Default SBanks: ()
$SBank Capacity: ()
$Shields: 0
$Power Output: 0.0
$Max Oclk Speed: 0.0
$Max Weapon Eng: 0.0
$Hitpoints: 5000
$Flags: ( "drydock" )
$AI Class: none
$Afterburner: NO
$Countermeasures: 0
$Scan time: 2000
$EngineSnd: -1
$Closeup_pos: 0.0, 0.0, -363
$Closeup_zoom: 0.55
$Score: 0</pre>

==Gallery==
<gallery>
Image:Mefistofele9.png | An abandoned depot.
</gallery>

==Veteran Comments==
{{comment|}}

==Download link:==
*Mediafire mirror (OUTDATED) - http://www.mediafire.com/download.php?81ad2abez0dif25
*Release thread (OUTDATED) - http://www.hard-light.net/forums/index.php?topic=73588.msg1453504#msg1453504
*As part of the modular construction kit (lacks table file) (FSMods mirror) - http://www.freespacemods.net/download.php?view.875
*As part of the modular construction kit (lacks table file) (Mediafire mirror) - http://www.mediafire.com/?xhrz4dh5znndwxn

[[Category:User-made Ships]]
[[Category:Installation]]

Variable

2010-06-21T16:58:08Z

FelixJim: /* Four Types of Variables */

'''Variables''', implemented in retail FS2, allow you to store pieces of information that you can use later in a mission or a campaign. Normally, SEXP trees use fix values. Consider this basic one:

is-destroyed-delay
2
GTT Spomer
send-message
#Command
High
Spomer destroyed

All these values are fixed. If you wanted Command to send a message five (not two) seconds after the Spomer is destroyed, you would need a second Event with 5 instead of 2. If, however, the "delay" value (2) were a variable, you could manipulate the delay between the Spomer's death and Command sending the message in a more convenient and flexible way in one Event. Variables are dynamic values that can be changed during the course of the mission.

==Basics==
Right-click on any argument in the Events list and look at the three options at the bottom of the menu, '''Add Variable''', '''Modify Variable''', and '''Replace Variable'''. If your Events window is empty, create an Event.

*'''Add Variable''' allows you to create a new variable. If you're using FreeSpace Open, your Add Variable window looks somewhat like [[:Image:AddVariable.JPG|this]]. You can add a number or a string-based variable. Number-based variables must contain numbers only, while string-based values can use letters. From a technical point of view, it's unimportant how you name your variable. Then set your variable's default value.
**In our example, let's create a number-based variable that is named "MessageDelay" and its default value is 2.
*'''Modify Variable''' allows you to change a variable that you've already created. You can modify only one variable at a time. This feature is not to be confused with the [[modify-variable]] one.
*'''Replace Variable''' replaces the currently selected SEXP argument with the variable of your choice.
**If you clicked on "2" in the example, you could change it to MessageDelay using Replace Variable --> MessageDelay. If the "2" is changed to MessageDelay (which receives a red icon), then you've been successful.

Variable values can be changed using the [[modify-variable]] SEXP, which you can find under Add Operator --> Change --> Special. A sample Event that adds 1 to a number-based variable looks like [[:Image:VariableEvent.JPG|this]].

== Four Types of Variables ==

There are four types of variables.

'''Standard variables''' This type of variables are used in one mission only. If the player ends the mission in any way (jumping out, dying, restarting, etc.), all the standard variables will be reset to their default values. Whether the player is allowed to progress in the campaign or not is inconclusive (compare campaign-persistent variables).

'''Player-persistent:''' Player-persistent variables always retain the last value you gave them, regardless of the outcome of the mission. They are reset upon the reset of the current campaign, or the selection of a new campaign.

'''Campaign-persistent:''' These persistent variables are stored in the campaign file, and are only stored when a campaign progresses to a new mission. So if the player is killed or quits during a mission, and changes made to a campaign-persistent variable are not stored.

'''Network variables''' are only relevant in a multiplayer game. Non-network variables are only ever altered on the server. This means that they can not be used in messages or scripting because all the client machines will only ever have the default value. If you need to have the value of a variable display in a message you will need to mark it as a network variable. ''

== Variables and Messages ==
Variables can also be used in messages. To do this, use the variable's name preceded by the '$' token (for example "$killcount"), and in-game this will be replaced with the value of the variable. Input is case-sensitive. It works for both numeric and string variables.

==Example Mission==
:''Main Article: [[Variables example mission]]''

This is a mission in which the player must take down all four of the Sathanas's main beam weapons to win the mission. This is like [[Bearbaiting]], except this mission is solely made as a variables tutorial. The juggernaut will not fire at you or jump out.

==Links==

*[http://homepage.ntlworld.com/karajorma/FAQ/fredretail.html#variables Karajorma's FreeSpace FAQ on variables]
* Fred Zone examples for variables [http://fredzone.hard-light.net/cetanu_adv-fred-lessons.shtml] [http://fredzone.hard-light.net/cetanu_adv-fred-lessons-2.shtml]

[[Category:FRED]]