FreeSpace Wiki - User contributions [en]

ModelView

2005-12-11T19:37:51Z

128.235.249.80:

Descent Manager's ModelView32 is the most popular program for the viewing and editing of Freespace POF files. Its features include the ability to edit turrets, subsystems, shield meshes, weapon banks, gunpoints and texture names, as well as providing a wealth of information about the model. A stable, intuitive interface and the ability to categorize and browse the models of VP files have seen Modelview become a foundation of Freespace modding.

You can download Modelview from the Descent Network, http://www.descent-network.com/
There is a version of Modelview with extended limits for the viewing and editing of high-poly models, available in this thread:
http://www.hard-light.net/forums/index.php/topic,36980.0.html

{{stub}}

[[Category:Tools]]

Orion

2005-12-09T21:53:47Z

128.235.249.80:

#REDIRECT [[GTD Orion]]

Argo

2005-12-09T21:53:27Z

128.235.249.80:

#REDIRECT [[GTT Argo]]

Styxx's POF Conversion plugin for 3D Studio Max

2005-12-09T21:53:02Z

128.235.249.80: Restructured format, removed redundancy, added misc information and checked grammar and spelling.

Still a work in progress, Styxx has created a Freespace 2 model exporter plugin for 3D Studio Max versions 4 through 6. Available here: [[http://www.hard-light.net/forums/index.php/topic,26260.0.html]] There is no model importing function; to import POFs into Freespace 2 for reference or editing, it is necessary to convert them to COBs and then use Truespace or another program to convert them to a 3DS or other file.

Despite being available for well over a year, not many people actually know how to make this plugin work correctly. To that end, the following is intended to be a complete walkthrough of using the plugin to create a simple ship that makes use of all of the plugin's features.

Please note that this is not a tutorial for actually creating models. There are plenty of Max tutorials out there that have far better information in them than what can be provided here. It is, however, a guide to getting a model out of 3ds Max and into the Freespace 2 object format, POF, with minimal complications. If this is your first model we recommend you explore the functions of [[ModelView]]'s POF editor and the various View functions in FRED to get a feel for what goes into a Freespace model.

This tutorial is for the current exporter version as of November 13, 2003.

To start off, load all of the components of your model into a single Max scene file, and make sure that everything is unlinked so that you have no hierarchy to start off with. If you have already set up a hierarchy, go back and unlink it, as having things grouped too early may cause trouble later. From here, preparing the model for conversion involves a specific sequence of actions.

==Naming Convention==
Ideally, you should be following these conventions while building your model, but before you convert you should double check that all of these are correct. One by one, select each subobject and assign it a conversion name. Most subobjects require specific naming conventions:
===LODs===
Level of detail (LOD) objects are named "detail-0", "detail-1", etc, where detail-0 is the parent geometry for LOD0, detail-1 is the parent for LOD1, and so on. Do not skip levels.
===Debris===
Debris chunks are similarly named "debris-0", "debris-1", ... debris-n, where n is one less than the total number of debris chunks. Again, do not skip numbering, as the converter parses these in order and will break if a number is missed.
===Turrets===
Turrets are named "turretXX", where XX is a number between 01 and 99 that corresponds to the turret number that this model represents. If you have additional LODs for turrets (for example, the prominant triple-barreled turrets on the [[Orion]]) name them "turretXXa" for LOD0, "turretXXb" for LOD1, etc.
* Turret barrels are named "turretXX-arm", where turretXX is the name of the turret's base. Barrels (and any other object consisting of more than one connected element) should be one object, not several, so attach multiple barrels together with the attach tool.
===Shields===
The shield mesh should be named "shield" (and similarly, any and all geometry not supposed to be a sheild should not be named "shield"). Models should only have one shield.
===Other Subobjects===
* Geometry that's acting as a 'standard' Freespace subsystem should be named according to the final subsystem name. A physical Comm system would be "communications", a physical hangar would be "fighterbay", and so on.
* Geometry representing non-standard displaying subsystems should be given the name you want them to appear with. If this subobject geometry is to appear on the lower LODs it should be named "SUBOBJECTa" for LOD0, "SUBOBJECTb" for LOD1, etc. where SUBOBJECT is the desired subobject name.
* Hidden subobjects should be given a name that's meaningful to their function, such as "hangardoor" for a hangar door.
* Live debris, the ugly chunks of stuff left over when a turret or other subsystem is destroyed, are specified by naming the subobject for the destroyed component the same as the healthy version but with an added "-destroyed" on the end, like 'turret03a-destroyed'.
* For all other subsystems, any name is valid as long as Freespace can parse it from the POF chunk (so no Cylinder,3) but remember that what you name the subobject will be what it is called in the POF itself. No subobject should ever be converted with its Max-generated default name.

==Geometry Preparation==
Once your objects are named, you need to set them up so that they appear and behave properly in the game.
* All faces on all geometry '''except the shield''' must have a texture assigned to them. Missing this on as little as a single face will cause the plugin to crash. Shields never have textures assigned to them.
* Scale your scene to the size you want it to appear in-game. This may vary depending on your current Units settings, so once you do a test export, a little math should help you find the desired scale.
* Orient everything so that the front of the ship points towards the top of the screen in 'top' view mode.
* Change all your model geometry to 'Editable Poly' mode, as the converter seems to work best with poly models.

===Pivots===
* Position the primary model where it is supposed to be in the converted file so that its pivot point is at the origin. If you were converting the [[Colossus]], you would put the model in such a location that the middle of its rear engines, the point about which it rotates in-game, at (0,0,0).
* When the ship is in the exact place you want it, select the 'Hierarchy' tab, click 'Affect Pivot Only' and make sure that the pivot is at location 0,0,0. The location of the pivot on the root geometry for a level of detail MUST be at the origin, and this is important, so '''do not skip this step.'''
* Position all turrets and other subobjects where you want them in relation to the detail-X object that they will be attached to (this will usually be detail-0), making sure to follow Freespace conventions in terms of turret orientation. Topside multipart turrets should face forward with their barrels pointing straight up, multipart turrets on the bottom of the ship should face towards the ship's rear and their barrels should point straight down. Default resting positions can be assigned in tables, so don't try to do anything fancy with these in the model.
* When these subobjects are in the positions you want them, one by one select your rotating subobjects (turret bases, turret arms, radar dishes etc.), select the 'Hierarchy' tab, click 'Affect Pivot Only' and move the pivots to their rotation points. Turret arms should pivot at their bases.

===Transparent Faces===
Glass, transparency-blended nameplates, and other transparent textures should come last in the model. An easy way to accomplish this is to select all faces that use the material of your glass texture, detach them from the model, re-attach them with the attach tool, select the faces near the edge (all faces in the model may be appropriate) and perform a vertex weld with a threshold of 0.01. This will move the transparent faces to the end of the model's face list and will ensure proper rendering in-game.
* If you have a single map that is partially transparent, do this on the specific faces that will end up transparent.
* All transparent textures should be part of the root geometry (detail-0), without exception. Faces behind transparent textures, such as a pilot, are more likely to work correctly when these faces are a seperate subobject.

===Properties===
Assign properties to physical subobjects. Turrets are the most common case, but rotating subobjects like radar dishes and geometry representing a game subsystem like engines also need some extra data. To assign text properties to an object, open the object properties dialogue (right-click on the object, and select properties) and go to the 'User Defined' tab.
* All objects that will be subsystems will need "$special=subsystem" added to their user-defined properties tabs.
* Turrets (turret bases) should have "$fov=XXX" where XXX is the field of view for the turret and "$name=gunturret" added at the end. (Field of view is like a cone extending out from the turret's firing point normal, between 0 and 360 degrees. Most button turrets have a FOV between 100 and 180.)
* Other subsystems also need the "$name=somename" field, but only turrets require "gunturret". Rotating objects need "$rotate=X" where X is rotation time in seconds. Negative values indicate reverse rotation.

===Reset X-Form===
This is the step that has given people the most trouble. Now would be a good time to make a backup of the scene, so that you can restore to the un-rigged state if something goes wrong.
* Select all objects in the scene and open the Utilities tab. Select the "Reset X-Form" tool in the rollout that appears. Click the button of the same name to reset the transforms on all objects in the scene.
* If something in the scene moves in a strange way when you perform this action, there was still hierarchy set up in the scene so load up the backup and unlink the object(s) that moved from whatever they are attached to with the schematic editor. Then update the backup and try Reset X-form again, repeating as necessary.
* If you're having difficulty using the Reset X-Form tool, there is an alternate way to reset the pivot. Create a sphere with its pivot point where you want the subobject's pivot to be, Attach your subobject to it, delete the sphere's geometry and rename the resulting object appropriately.

====Test Exporting====
At this point it is recommended that you attempt an export with only "detail levels", "debris objects", and "glows" checked. "Glows" won't do anything yet, but the converter crashes if it is not selected. If it converts and everything is in the right place afterwards, then the geometry is sound and you can be sure that later errors were not caused by geometry issues. See the converting section for details and debugging info.

==Points, Lines and Dummies==
If you prefer editing all subsystem, turret, gun/missile point, dockpoint, engine glow, and glowpoint data in PCS, you can safely skip this section. However, as this is perhaps the greatest strength of the MAX converter, it is strongly recommended that you actually use these features. (Insignias don't work properly, so this tutorial will not address them.) Here you will create invisible objects that will define the model's in-game properties.

===Turrets and Weapons===
* To define a turret's firing points, place Point helper objects in the scene at the desired location for these points. It's a good idea to name these points something meaningful (if it's a firepoint for turret03, perhaps call it "turret03fp") so that you can figure out what goes where when rigging.
* To define a weapon bank, create a container dummy object. The dummy must take the name "gunbank-X", if it is to be a gun bank, or "missilebank-X" if it is to be a missile bank. X in both of these is the number of the bank, so start with zero and work your way up for both. The count of gunbanks is not related to the count of missilebanks, so start both at 0 and don't skip numbers. The location of the container dummy does not matter, so it can be dropped down anywhere. However, to prevent serious oddities in conversion, it is strongly recommended to define '''all''' dummy objects in either a top-down or perspective view. That rule applies to more than just weapon banks as well.
* To define a weapon bank's firing points, create point helper objects where each specific firepoint should be. Naming them something representative of their bank is helpful if you do multiple banks at a time.

===Subsystems===
* To define the standard subsystems used in FS2, create a dummy object at the location and with the size of the special point you want to create. This point should have a name starting with '$' and should be named what you want the point to display as otherwise.
* To define an engine glow, place dummies centered where the engine glows should be and set their size to the size of the glow.

===Paths and Docks===
Create your paths using the create line tool and modify the editable splines to suit each path you want in the model. Paths are always defined TOWARD the ship, so the first point (where you first click when you start an editable spline with the create line tool) should be the most distant from the ship, and the last the closest. All editable splines will become paths on conversion, but name them according to the Freespace convention anyway. Typically, the paths needed for a 'complete' model are paths for each subsystem (main subsystems and turret subobjects) so it's usually a good idea to know in advance where things like the weapons subsystem will be defined.
* Turret and subsystem paths are fine with just two points. These paths should be named "$pathXX" where XX is a number.
* Fighterbay paths normally have 3, 4, or more points. Fighterbay paths should be named "$bayXX" where XX is a number.
* Dock paths should have at least 4 points. Dock paths must have "dock" in the name, so "$dockXX" is preferable. Dock paths should also have "$name=somename", where somename is the display name of the dock in FRED, added to their user-defined properties tab. The final point of a docking path should come very close to the first dockpoint.
* To define a docking point, place one point helper where you want the dockpoint, and place a second point helper a short distance away towards the 'top' of the dock. If you want an [[Argo]] to dock in a certain alignment, the second point should be above the first from the orientation of the Argo.

===Glowpoints===
Glowpoints are very similar to gun/missile banks in setup, except that instead of point helpers for each point, they use dummys. The size of each individual dummy will determine the size of the glowpoint it creates.
* Glow banks are specified with a container dummy helper (which has multiple dummy helpers attached to it as children) with the name "glow-X" where X is the number of the glow bank (start with 0 and don't skip numbers).
* The string "$glow_texture=texturename" should be placed into the user properties tab for the parent helper.

==Rigging the Scene==
Now that all geometry and paths are set up properly, it's time to start putting things together. Setting up the hierarchy can be done in two ways: through the Schematic view, or in the scene itself.
* If you're using the Schematic view and you can't make out anything, try zooming in; Max does a particularly poor job of initially displaying a large number of objects in this view. Objects are connected in a hierarchy with the Link tool. To link one object to another, select the link tool, click on the to-be child object and drag to the intended parent.
* If you're linking objects together in the main scene, be sure to Hide whatever objects you're not working on. To link units together, select the Link tool, click on the to-be child object and drag to the intended parent geometry. You can also select the child geometry, select the Link tool, then use the Select By Name tool to link to an object. Select By Name also has an option to 'Display Subtree' showing you your hierarchy at a glance.

The connection hierarchy is essential to making the game display your model correctly. Child objects cannot be rendered if their parent is not rendered, so keep this in mind when setting up your hierarchy groupings. Child objects also rotate with their parents, so if you are setting up an animated model you must keep this in mind. In general, all subobjects that the game can access as a submodel get assigned as direct children of detail-0, with the possible exception of some weird model animations you might want to do. Turret barrels, however, are '''always''' children of their base, even if you don't intend to use autogeneration to set the turret up for you. It's usually a good idea to link subobjects like turrets together before linking the object itself to the main LOD.

===Subassemblies===
* The standard button turrets consist of the turret geometry, with the turret path and the firepoint(s) attached as children.
* Multipart turrets are assembled with the turret base as the parent and with the firepoint(s), path, and barrels all attached as children.
* Multipart turrets on LODs consist of the turret base with the barrels attached as a child.
* Attach all firepoints for a particular weapon bank to the container dummy helper as children.
* Glows associated with an engine subsystem should be linked to that subsystem as children.
* For docking points, attach the two dockpoints, in their creation order, to the dock path as children. The dock point normals will be set as the direction from the dockpoints to the first point in the path, which is often wrong, but this must be corrected after conversion using an external POF editor such as PCS.

===Final Assembly===
* Attach each turret base, physical subsystem, and extra subobjects intended to be direct subobjects of detail-0 to their parent LOD.
* Additional LODs should be set up the same way. Low-detail turret or subobject counterparts should be linked to their appropriate LOD. LODs should themselves be at the top level of the scene, not attached to any other piece of geometry or helper.
* All paths not assigned to a turret or subobject (subsystem paths for non-geometry subsystems, fighterbay paths, and dock paths) should be at the root level of the scene.
* Debris pieces be at the scene root as well, not attached to any parent object.
* The shield mesh (if one is being used) should also be at the top level of the scene.

==Converting==
Converting is a relatively simple process in comparison to actually setting everything up. It is, however, not foolproof and actually quite failure prone. It should be as simple as doing a file->export, choosing Freespace 2 POF as your export filetype, and selecting only the components that you actually have in your scene. The only exception is the glows box, which must ALWAYS be checked or a crash will result.

===What can go wrong===
The simple answer is a lot. The usual result is that 3DS Max will crash while exporting, sometimes leaving behind a half-finished POF. By looking at this POF you may be able to narrow down the problem area.
* Did you skip a number in any sequence that requires a -X at the end? Debris is the most common place for this to occur now, though there are other places that it may also come up.
* Does your model have polygons on any mesh other than the shield that have no texture?
* Did you try to convert with the glow box is unchecked? There isn't any good reason why this happens.

Finally, the converter will occasionally crash for no reason whatsoever, so always save before you convert and load it up and try again if it fails once. Failing twice in a row is usually indicative of a real problem.

If the converter doesn't crash but your model is behaving incorrectly, go thorough this tutorial again and ensure that all the steps have been followed.

==Known issues==
There are still some things that the POF converter cannot do properly.
* It makes a mess out of the header; the mass values are about two orders of magnitude higher than they would be for an equivalent stock model. The Moment of Inertia is also a complete mess and doesn't output anything useful. Both of these values should be changed before the model is used in game. Unfortunately, if glowpoints were used, there is not a good mainstream way to correct the MoI data without losing the glow chunk, and PCS won't import glows, so you're sort of stuck unless you are willing to copy it by hand.
* The converter miscalculates the radius of the model by approximately a factor of 2, which creates some strange behavior during subspace warps and when viewing externally from the model. Again, there is not a good way to correct this, so it may just be something you have to live with.
If these problems become issues, please contact the user StratComm through the HLP PM system for assistance.

[[Category:Modding]]

Sandbox

2005-11-21T19:54:15Z

128.235.249.80:

'''Welcome to the Freespace Wiki, the ultimate source for Freespace info on the web.'''


{| border=0 align=right cellpadding=4 cellspacing=0 width=30% style="margin: 0 0 1em 1em; background: #404040; border: 1px

#CC0500 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #613030; 70%;"|''Retail Freespace''
|-
| [[Portal:Freespace 1|Freespace 1]]
|-
| [[Portal:Freespace 2|Freespace 2]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|''Freespace Source Code Project''
|-
| [[Getting Started(Main)|Getting Started]]
|-
| [[Multiplayer(Main)|Multiplayer]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|''Modding Freespace''
|-
| [[Portal:Modding|General Modding]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|''Freespace Universe''
|-
| [[Universe General(Main)|General]]
|-
| [[Universe Specific(Main)|Specific]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|''Other''
|-
| [[Freespace Lingo]]
|-
| [[Portal:Community|Freespace Community]]
|-
| [[Getting Freespace]]
|-
| [[BitTorrent(Main)|BitTorrent]]
|}

This is trying to do colored text:
 red text green text blue text 

Or use preview?

It's just a sandbox... but yeah, point taken. :p

 Canon event and date Canon event, non-canon date Non-canon event, extrapolated date.

Sandbox

2005-11-21T19:51:00Z

128.235.249.80:

Sandbox

2005-11-21T19:49:50Z

128.235.249.80:

Sandbox

2005-11-21T19:44:41Z

128.235.249.80:

'''Welcome to the Freespace Wiki, the ultimate source for Freespace info on the web.'''


{| border=0 align=right cellpadding=4 cellspacing=0 width=30% style="margin: 0 0 1em 1em; background: #404040; border: 1px

#CC0500 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #613030; 70%;"|''Retail Freespace''
|-
| [[Portal:Freespace 1|Freespace 1]]
|-
| [[Portal:Freespace 2|Freespace 2]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|''Freespace Source Code Project''
|-
| [[Getting Started(Main)|Getting Started]]
|-
| [[Multiplayer(Main)|Multiplayer]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|''Modding Freespace''
|-
| [[Portal:Modding|General Modding]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|''Freespace Universe''
|-
| [[Universe General(Main)|General]]
|-
| [[Universe Specific(Main)|Specific]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|''Other''
|-
| [[Freespace Lingo]]
|-
| [[Portal:Community|Freespace Community]]
|-
| [[Getting Freespace]]
|-
| [[BitTorrent(Main)|BitTorrent]]
|}

The Freespace Wiki is designed to be a comprehensive source of data for the Freespace series of games, includding 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.

This is trying to do colored text:
<html><color=white>White</color> <color=AAAAAA>A grey</color> <color=777777>7 grey</color></html>

Sandbox

2005-11-21T19:41:50Z

128.235.249.80:

'''Welcome to the Freespace Wiki, the ultimate source for Freespace info on the web.'''


{| border=0 align=right cellpadding=4 cellspacing=0 width=30% style="margin: 0 0 1em 1em; background: #404040; border: 1px

#CC0500 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #613030; 70%;"|''Retail Freespace''
|-
| [[Portal:Freespace 1|Freespace 1]]
|-
| [[Portal:Freespace 2|Freespace 2]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|''Freespace Source Code Project''
|-
| [[Getting Started(Main)|Getting Started]]
|-
| [[Multiplayer(Main)|Multiplayer]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|''Modding Freespace''
|-
| [[Portal:Modding|General Modding]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|''Freespace Universe''
|-
| [[Universe General(Main)|General]]
|-
| [[Universe Specific(Main)|Specific]]
|-
! style="color: white; height: 30px; background: #613030; 70%;"|''Other''
|-
| [[Freespace Lingo]]
|-
| [[Portal:Community|Freespace Community]]
|-
| [[Getting Freespace]]
|-
| [[BitTorrent(Main)|BitTorrent]]
|}

The Freespace Wiki is designed to be a comprehensive source of data for the Freespace series of games, includding 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.

{| border=0 align=left cellpadding=4 cellspacing=0 width=65% style="margin: 0 0 1em 1em; background: #404040; border: 1px

#CC0500 solid; border-collapse: collapse; font-size: 95%;"
! style="color: white; height: 30px; background: #613030; 70%;"|''Featured Article of the Moment''
|-
|{{Featured Article}}
|}

This is trying to do colored text:
<color=white>White</color> <color=AAAAAA>A grey</color> <color=777777>7 grey</color>

Timeline

2005-11-21T19:29:26Z

128.235.249.80: Added notes...

Please note that the Unification War and 14-Year War timelines are non-canon, developed by Eishtmo for the TVWP campaign. For the sake of consitency and due to the lack of anything official, they are being included here for completeness.

*2300-2320: [[Unification]] - Not Canon
*2320-2335: [[The 14-Year War]] - Data within may not be canon
*----2335--- : [[The Great War]]
*2335-2366: [[Reconstruction]] - Data within may not be canon
*2366-2367: [[The NTF Rebellion]]
*----2367--- : [[The Second Shivan Incursion]]
*2367-2400: [[Post-Capella]] - Not Canon

The above is being left in place as A)I'm curious where the author got the dates for the NTF and Shivan Incursion stuff and B) some of it is actually pretty correct. The Unification and 14 Year War sections are NOT canon and are background information for the Terran-Vasudan War Project. Below is the closest to a canon timeline, sans the game time lines, that can be compiled. - Eishtmo
Most of it is extrapolation; I put it together during my tenure at FSURP, before the Wiki came online. I'll work with you on this but let's move the discussion to the Talk page. -Galemp

{| border="2" cellpadding="4" cellspacing="0" style="margin: 1em 1em 1em 0; background: #101010; border: 1px #aaa solid; border-collapse: collapse;"
|-
| valign="top" style="width:100px" | '''~8000 BC:'''
| style="width:350px" | Dynasty of 10,000 Years established on Vasuda Prime
|-
| valign="top"| '''~6000 BC:'''
| Ancients Civilization destroyed by Shivans
|-
| valign="top"| '''2313:'''
| Subspace discovered by Terrans
|-
| valign="top"| '''?:'''
| Galactic Terran Alliance formed
|-
| valign="top"| '''~2317:'''
|Ma'at transport enters service
|-
| valign="top"| '''2321:'''
|Terran-Vasudan War (14 Year War) begins
|-
| valign="top"| '''?:'''
|Leviathan construction ordered Probably "a few months" after start of war
|-
| valign="top"| '''2323:'''
| Battle of Rexis 4 GTD Goliath destroyed Anubis fighter confirmed First use of Anubis as kamikaze fighters
|-
| valign="top"| '''?:'''
| Battle of Gulnara Victory for Terrans Leviathan production halted
|-
| valign="top"| '''?:'''
| Battle of Talania System Terran Defeat Leviathan production restarted
|-
| valign="top"| '''?:'''
| Aldebaran Encounter Satis freighter enters service
|-
| valign="top"| '''~2327:'''
| Elysium transport enters service ''Contradiction: FS1 says since colonization began'' Thoth fighter production begun ''Contradiction: FS1 says built with Ulysses fighter, 2335'' 107th Ravens Founded
|-
| valign="top"| '''2333:'''
| Vega Engagement Typhon class destroyer appears GTD Eisenhower and 4th fleet destroyed
|-
| valign="top"| '''2335:'''
| 14 Year War ends Great War begins in Jan, ends Dec Lucifer destroyed in March GTA Provisional Government established in Delta Serpentis Hades Rebellion 
|-
| valign="top"| '''?:'''
| Terrans divide into four groups: Adhara Coalition Antares Federation Regulus Syndicate Luyten New Alliance
|-
| valign="top"| '''2339:'''
| Emperor Khonsu II dissolves Vasudan Parliament
|-
| valign="top"| '''2345:'''
| Galactic Terran-Vasudan Alliance established
|-
| valign="top"| '''2347:'''
| GTVA Colossus construction started Bes freighter enters service
|-
| valign="top"| '''2352:'''
| GTSC Erikson visits Gamma Draconis Cyclops bomb enters service
|-
| valign="top"| '''?:'''
| Operation Templar
|-
| valign="top"| '''~2353:'''
| Hecate class destroyer commissioned
|-
| valign="top"| '''2358:'''
| Beta Aquilae Convention Formal dismantling of Terran blocs Formation of General Assembly, Security Counsel and Vasudan Imperium
|-
| valign="top"| '''2360:'''
| Hatshepsut class destroyer commissioned
|-
| valign="top"| '''2365:'''
| Neo-Terran Front Rebellion begins Aeolus class cruiser production halted
|-
| valign="top"| '''2366:'''
| Lieutenant Commander Christopher Snipes 'defects' to the NTF
|-
| valign="top"| '''2367:'''
| Second Shivan Incursion
|-
|}

[[Category:History|*]]

Post-Capella

2005-11-21T19:24:56Z

128.235.249.80: Added PREVIOUS link.

This time period is unclear, and can only be speculated on. However, several things are clear: the millions of Capellan refugees must find a new home, and the [[Knossos]] technology can be used to re-open the jump node to [[Sol]] and re-establish contact. Speculations on the state of Sol, after having been severed from the rest of the GTA in 2335, vary widely. Presumably, the timeline of [[Freespace3]] would have concentrated on this area. Arguments and any probable timelines will be posted here.

===Two weeks after Capella incident===
Starting point for the Technological Superiority campaign.

===2371===
Starting point of the Twisted Infinities campaign.

===2374===
Starting point of the BlackWater Operations campaign

===2375?===
Construction of the Terran Knossos device completed.

===2375===
Starting point of the Scroll of Atankharzim campaign.

===2400===
Starting point of the Inferno campaign. Approximate starting point of the Machina Terra Project.

===4021===
Starting point of the Starforce Mod.

NB: Many of these mods do not reference each others timelines, and so conflicting storylines can, and frequently do occur.

[[The Second Shivan Incursion]]''' :PREVIOUS

[[Category: History]]

Second Shivan Incursion

2005-11-21T19:23:27Z

128.235.249.80:

Shortly after the discovery of the [[Knossos]] subspace portal, a Rakshasa-class Shivan cruiser emerged. A short-lived offensive against the Shivans in the nebula beyond the portal also saw the end of [[The NTF Rebellion]] with the deployment of the [[GTVA Colossus]]. Bosch, however, made contact with the Shivans and vanished into the nebula. Meanwhile, dozens of six-kilometer long Shivan Sathanas juggernauts began pouring from the portal, and started converging on the [[Capella]] star. A plan to collapse the jump nodes to Capella using [[Meson Bomb]]s was hatched and technically successful, but during the final stages of evacuation, the Sathanas juggernauts triggered a supernova in Capella. This timeline will give a battle-by-battle account of the offensive and defensive action against the Shivans.

==2367==

August 16th: Rakshasa class Shivan cruiser and several wings of Maras appear through the Knossos portal, destroying the Vigilant. GTVA command deploys the GTD Carthage and the GVCv Dashor to neutralize the immediate threat.

August 20th: NTC Trinity discovered adrift in the nebula.

August 21st: GTCv Lysander destroyed by SD Ravana.

August 22nd: SD Ravana destroyed by bombers in the nebula.

August 28th: NTF launches a major offensive in Epsilon Pegasi. Rear Admiral Koth and the NTF 6th Fleet inflict 75% causalties to the GTVA forces. First Nebular Retreat.

August 29th: First combat deployment of the GTVA Colossus, at the Battle of Enif Station.

November 2nd: With Epsion Pegasi secured, the GTD Aquitaine spearheads the exploration of the nebula.

November 7th: Sirius falls to the GTVA. Bosch orders the rest of the NTF fleet to Gamma Draconis and the Nebula to make contact with the Shivans.

November 11th: First appearance of the SJ Sathanas. Second Nebular Retreat.

November 14th: The Knossos portal is destroyed by Meson bombs, but the SJ Sathanas emerges in Gamma Draconis through the now-stabilized node.

November 15th: Sathanas main beams and the SD Beleth destroyed by Bakha bombers near the Gamma Draconis-Capella node. Destruction of the SJ Sathanas by the GTVA Colossus in Capella.

November 18th: Admiral Bosch and his immediate subordinates captured by the Shivans. GTVA recovers the schematics for the ETAK device. NTF Iceni self-destructs. End of the NTF rebellion.

November 22nd: Discovery of the second Knossos portal by the GVD Psamtik. Multiple Sathanas juggernauts encountered in the nebula. GVD Psamtik destroyed by the second Sathanas.

November 23rd: Terran SOC pilots, flying captured Mara fighters, scout the system beyond the second Knossos and encounter a third Knossos as well as several additional juggernauts. Third Nebular Retreat.

November 24th: Massive evacuations of the densely-populated Capella system begin. Millions of refugees flood into Epsilon Pegasi and Vega.

November 29th: 90 Sathanas juggernauts surround the Capella sun and begin emitting quantum subspace pulses of increasing intensity. GTVA Colossus destroyed by Sathanas 17 while defending the Capella-Gamma Draconis node.

November 30th: GTD Nereid and GTD Bastion, packed with meson bombs, detonate inside the Vega-Capella and Epsilon Pegasi-Capella nodes. Sathanas juggernauts destabilize the Capella star. Capella goes supernova.

[[The NTF Rebellion]]''' :PREVIOUS | NEXT: '''[[Post-Capella]]

[[Category:History|Second Shivan Incursion]]

NTF Rebellion

2005-11-21T19:22:14Z

128.235.249.80: Added PREVIOUS and NEXT links.

In 2366, Admiral Aken Bosch of the GTVA 4th Fleet declared his scission with the rest of the GTVA and the formation of a new government based in [[Polaris]], the [[Neo-Terran Front]]. The governments of [[Regulus]] and [[Sirius]] also defected, leading to heavy fighting in the front lines of [[Alpha Centauri]], [[Deneb]], and [[Epsilon Pegasi]]. This timeline will span between the initial fall of [[Polaris]] to the escape of Bosch and destruction of the Iceni in the nebula.

===2366:===
=====March 17th:===== Admiral Aken Bosch of the GTVA 4th Fleet secedes from the GTVA and forms his own government, Neo-Terra, in [[Polaris]].
=====March 23rd:===== The government of Regulus defects to the NTF.
=====March 25th:===== [[Sirius]] swears allegience to the Neo-Terran Front.
=====April 19th:===== NTF successfully invades Alpha Centauri.
=====April 23rd:===== NTF gains a foothold in Epsilon Pegasi.
=====May 3rd:===== NTF takes control of most of Deneb. Construction of the Iceni begins as Bosch plunders Ancient archeological sites.

===2367:===
=====February 12th:===== Bosch learns the location of the Knossos subspace portal.
=====July 20th:===== NTF Iceni launches from a hidden asteroid base in Deneb.
=====August 1st:===== GTVA Colossus construction completed.
=====August 10th:===== GTC Trinity defects to the NTF.
=====August 14th:===== NTF presence detected in Gamma Draconis. GTC Vigilant sent to patrol node.
=====August 16th:===== Rakshasa class Shivan cruiser and several wings of Maras appear through the Knossos portal, destroying the Vigilant. GTVA command deploys the GTD Carthage and the GVCv Dashor to neutralize the immediate threat.
=====August 20th:===== NTC Trinity discovered adrift in the nebula.
=====August 22nd:===== SD Ravana destroyed in the nebula.
=====August 25th:===== A GTVA two-pronged offensive in Sirius fails, allowing the NTF to maintain their grip on that system.
=====August 28th:===== NTF launches a major offensive in Epsilon Pegasi. Rear Admiral Koth and the NTF 6th Fleet inflict 75% causalties to the GTVA forces.
=====August 29th:===== First combat deployment of the GTVA Colossus, at the Battle of Enif Station.
=====November 1st:===== NTD Repulse destroyed by ramming the Colossus. NTF 6th Fleet defeated. GTVA gains full control of Epsilon Pegasi.
=====November 2nd:===== GTVA forces take Alpha Centauri and Deneb.
=====November 7th:===== Sirius falls to the GTVA. Bosch orders the rest of the NTF fleet to Gamma Draconis and the Nebula to make contact with the Shivans.
=====November 8th:===== GTVA Colossus, Terran and Vasudan warships, sentry guns and bombers annihilate much of the NTF's fleet.
=====November 9th:===== NTF Iceni, NTC Alexandria, and NTT Grall escape to the nebula. SOC operatives, posing as NTF saboteurs, deactivate the beam cannons on the Colossus to allow the Iceni's escape.
=====November 11th:===== First appearance of the SJ Sathanas. Testing of the ETAK device successful between the NTF Iceni and the SD Chemosh.
=====November 15th:===== Destruction of the SJ Sathanas by the GTVA Colossus in Capella.
=====November 18th:===== Admiral Bosch and his immediate subordinates captured by the Shivans. GTVA recovers the schematics for the ETAK device. NTF Iceni self-destructs. End of the NTF rebellion.

[[Reconstruction]]''' :PREVIOUS | NEXT: '''[[The Second Shivan Incursion]]

[[Category: History]]

NTF Rebellion

2005-11-21T19:21:22Z

128.235.249.80:

Reconstruction

2005-11-21T19:18:16Z

128.235.249.80: Added PREVIOUS and NEXT links.

After the destruction of the [[SD Lucifer]], the Terran and Vasudan species were faced with having to rebuild their respective civilizations. A coup by rogue members of [[Galactic Terran Intelligence]] was only the first in a series of splinterings in the former [[Galactic Terran Alliance|GTA]]. This timeline will cover the campaigns Silent Threat and [[Operation Templar]], as well as the formation of the [[Galactic Terran-Vasudan Alliance|GTVA]], up to the beginning of [[The NTF Rebellion]].

http://freespace.volitionwatch.com/techfs/jeremy/reconstruction.jpg
===2335:===
=====March 29th:===== [[SD Lucifer]] destroyed by pilots from the GTD Bastion while exiting subspace in [[Sol]]. [[Sol]]-[[Delta Serpentis]] jump node collapses, severing Earth from the rest of the [[Galactic Terran Alliance|GTA]].

===2336:===
[[GTD Hades]], a rebel GTI superdestroyer, destroyed. Fragmented GTA regional governments collapse into independent groups, including the Adhara Coalition, the Antares Federation, the Regulus Syndicate, and the Luyten New Alliance.

===2339:===
Vasudan Emperor Khonsu II ascends to the throne and immediately begins a restructuring of the Vasudan government. The corrupt Vasudan parliament is disbanded and replaced with a constitutional monarchy, with the multiple checks on the Emperor's power. Khonsu proves to be a brilliant leader, and brings his people into a new renaissance.

===2341:===
Vasudan engineers develop the flak gun as a bomb-interception screen for the [[GVD Typhon|Typhon]] destroyer. The success of the project leads to deployment on all new Terran and Vasudan warship classes.

===2345:===
Several Terran governments approach the Vasudan Imperium and propose the formation of a new unified government, the [[Galactic Terran-Vasudan Alliance]]. Over the next few years the prosperity of this body leads many of the Terran blocs to join the GTVA. Khonsu II proposes the construction of a joint [[GTVA Colossus|Terran-Vasudan juggernaut]] to counter any future Shivan threat.

===2346:===
Construction of the [[GTVA Colossus]] begins. The last remains of the Hammer of Light are crushed in Operation Templar.

===2355:===
GTVA engineers make the first successful deployment of beam cannon technology after the Hades Rebellion, on board the GTD Repulse. A massive refit program for all warships is begun to integrate this new weaponry. The [[GVCv Sobek]] design is completed and manufacture begins immediately.

===2358:===
The [[GTVA]] convenes for several weeks in [[Beta Aquilae]] for a complete restructuring of the GTVA. The [[Beta Aquilae Convention]], or BETAC, disbands all former Terran blocs, centralizes power in the GTVA and organizes the military, political, and economic systems of the member systems.

===2360:===
The first [[GVD Hatshepsut]]-class destroyer is commissioned. [[GVCv Deimos|Terran Deimos]] corvettes go into production and construction of [[GTC Leviathan|Leviathan]] cruisers is stopped.

===2365:===
[[GTC Aeolus]] production is halted after only 24 are built, due to the extreme cost and limited effectiveness.

===2366:===
=====March 17th:===== Admiral Aken Bosch of the GTVA 6th Fleet secedes from the GTVA and forms his own government, [[Neo-Terra Front|Neo-Terra]], in [[Polaris]].

[[The Great War]]''' :PREVIOUS | NEXT: '''[[The NTF Rebellion]]

[[Category: History]]

Great War

2005-11-21T19:17:18Z

128.235.249.80: Added PREVIOUS and NEXT links.

The appearance of a third sentient species, designated [[Shivans]], caused the [[Terrans]] and [[Vasudans]] to set aside their differences and combat the mutual threat. The Shivan armada, led by the shielded superdestroyer [[SD Lucifer]], marched through the Terran and Vasudan lines of defense, destroyed the Vasudan homeworld of [Vasuda] Prime, then set a course for Earth. Fortunately ancient artifacts discovered in [[Deneb]] and [[Altair]] led to the Lucifer's destruction while exiting the jump node to [[Sol]], collapsing it.

===2335:===

=====January 7th:===== Shivans first sighted in [[Ross 128]]. Contact lost with Rivera Station.
=====January 8th:===== GTA launches Operation Thresher, also known as the Fifth Battle of the Vasuda-Antares Node. Initial losses cause Thresher to be declared a failure only two days after it started.
=====January 9th:===== [[Laramis]] system discovered.
=====January 15th:===== Traitor Alexander McCarthy captured by the [[GTA|Galactic Terran Alliance]] while attempting to sell the [[Avenger]] prototype cannon to the [[Vasudans]].

=====January 16th:===== The [[Shivans]] attack Vasudan and Terran forces near the Antares-Ribos node. PVC Taurus and GTSC Plato destroyed. First Shivan fighter destroyed.
=====January 18th:===== PVE proposes cease-fire based on the [[Pan-Galactic Treaty]]. Shivans inflict heavy casualties in [[Beta Cygni]] and [[Vega]].
=====January 20th:===== Lt. [[Alexander McCarthy|McCarthy]] is tried for treason, but released on the condition he divulges all knowledge of the Shivan activity in [[Ross 128]]. The McCarthy trials go down as an historical precedent.
=====January 23rd:===== [[GTA|Galactic Terran Alliance]] and [[PVE|Parliamentary Vasudan Empire]] sign the Treaty of 2335. The 14-Year War officially comes to an end. GTD Amadeus destroyed by Shivan forces. GTA and PVE declare open states of war against the Shivans.
=====January 24th:===== [[Hammer of Light]] secedes from the PVE and begins willfully aiding the Shivans. Terran and Vasudan scientists perform the first successful test of energy shielding aboard the GTSC Feynman.
=====January 25th-29th:===== [[HoL|Hammer of Light]] attacks disrupt many of the convoys carrying shielding systems, and capture many prototypes.
=====January 31st:===== HoL cruiser Ramses is destroyed by the Shivan Cain-class cruiser Taranis during a [[GTA|Galactic Terran Alliance]] capture attempt.
=====February 10th:===== Terran fighters and bombers from the GTD Galatea capture the [Taranis] in [Ikeya]. It is towed to Tombaugh Installation in [[Ribos]].
=====February 11th:===== [[SD Lucifer]] destroys captured Taranis and Tombaugh Station. Analysis of the attack reveals powerful beam weaponry and invulnerable shielding. PVD Pinnacle assists in the recovery of refugees and survivors in the system.
=====February 14th:===== PVD Prophecy and PVD Tanis captured in [[Vega]] by the [[Hammer of Light]]. Terran-Vasudan tensions are strained by the joint occupation of [[Antares]].
=====February 15th-19th:===== GTD Galatea leads a strike force against [[HoL|Hammer of Light]] forces in the system.
=====February 20th:===== Shivan [[Dragon-class fighter|SF Dragon]] captured in [[Deneb]].
=====February 22nd:===== Shivan fighter refitted with Terran weaponry. Covert reconnaissance acquires crucial scans of several Shivan ships, including the Lucifer.
=====February 28th:===== Battle of Deneb, a last-ditch effort to hold off the Shivans as long as possible to evacuate [[Vasuda]] Prime. Combatants include the [[SD Lucifer]], SD Eva, GTD Galatea, GTD Legion, and PVD Hope. Of these, only the Lucifer and the Hope, badly damaged, survive the intense battle.

=====March 1st:===== [[SD Lucifer]] arrives in orbit around [Vasuda] Prime and bombards it for thirteen straight hours. Most escaping transport ships were destroyed. All major Vasudan cities were leveled, and most of the landmass was rendered uninhabitable. It's estimated that four billion innocent Vasudans lost their lives in the attack.
=====March 2nd:===== GTD Bastion and PVD Hedetet assist in evacuation and rescue efforts in Vasuda and Beta Aquilae.
=====March 5th:===== Vasudan scientists discover [[Ancient|Ancients]] remains on [[Altair]] IV. The GTSC Rosetta and pilots from the GTD Bastion help recover the artifacts and destroy the [[HoL|Hammer of Light]] flagship Anvil.
=====March 17th:===== [[Ancient|Ancients]] artifacts reveal the method of tracking the [[Lucifer|SD Lucifer]] through [[subspace|Subspace]], where its shields will be inoperative.
=====March 22nd:===== Miniaturization technology on intrasystem subspace drives perfected. Drives are installed on all remaining fighters and bombers.
=====March 29th:===== [[SD Lucifer]] destroyed by pilots from the GTD Bastion while exiting subspace in [[Sol]]. [[Sol]]-[[Delta Serpentis]] jump node collapses, severing Earth from the rest of the [[GTA|Galactic Terran Alliance]].

[[14-Year War]]''' :PREVIOUS | NEXT: '''[[Reconstruction]]

[[Category: History|Great War]]

Eishtmo's Terran-Vasudan War timeline

2005-11-21T19:15:45Z

128.235.249.80: Added PREVIOUS and NEXT links.

Shortly after first contact, the Terran-Vasudan War, or The 14-Year War, broke out. Heavy and sustained casualties were suffered on both sides, but both species learned valuable lessons in adaptation and the development of new technologies. This timeline will span from the first Vasudan contact to the first contact with the [[Shivans]] in [[Ross 128]].

===2320:===

=====March:===== First official contact with the [[Vasudan Parliamentary Empire]].
=====April:===== First diplomatic meeting in Antares.
=====July:===== The [[Pan-Galactic Treaty]] is agreed to by diplomats. Taken to respective governments. GTD Gaia completed.
=====December:===== [[Pan-Galactic Treaty]] rejected by legislators on both sides.

===2321:===

=====January:===== Prince Mihos killed during drug gang battle. Vasudan politicians blame GTA outright.
=====February:===== Diplomats Knum and Andrews meet. Meeting ends in bloodshed. War declared by both sides the next day.
=====April:===== Vasudans launch raid on Sol system. Crushed by GTD Gaia and 1st Fleet.
=====May:===== Vasudans begin construction on their own destroyer, the Thanatos class.
=====September:===== First Thanatos, PVD Thanatos, completed.

===2322:===

=====November:===== GTA officials determine the war will not be short. Authorizes the construction of the [[GTC Leviathan]] cruiser.

===2323:===

=====March:===== First Battle of the Vasuda-Antares node. Marks the first time Terran warships enter the Vasuda system. Terrans only managed to hold the node for a week before being driven back.

===2324:===

=====June:===== Battle of Vega III. In an attempt to get around the Terran hold on Antares, the PVN launches its first major assault on a Terran system at Vega. The battle was the bloodiest to date, with the loss of nearly 50,000 on both sides. The Terrans managed to drive the Vasudans back to Deneb, but didnâ€™t have the strength for a counter-attack.

===2326:===

=====August:===== The first Savior class destroyer, PVD Savior, come off the lines. Over the next two years, the Vasudans would completely replace their Thanatos class destroyers with these powerful ships.
=====October:===== First Battle of Antares-Vasuda node. To show off the new ship, Vasudan Prince Amon organizes an attack on Antares. The PVD Savior tears through Terran lines. The Vasudans gain a powerful foothold in Antares.
=====November:===== Battle of Gulnara. As the Vasudans poured into the system, the [[Terrans]] launched a massive counter-attack. Near the Antares IV moon, Gulnara, the [[Vasudans|Vasudan]] fleet is beaten back to the node. This defeat leads GTA command to believe that victory is on the horizon. Leviathan production is halted, and the GTA initiates a major offensive.

===2327===

=====January:===== Realizing the end is coming, the Vasudan parliament â€œunofficiallyâ€ moves to Alpha Centauri where it would stay until after the Great War. The Third Battle of the Vasuda-Antares node happens days later. [[Terrans]] establish a strong foothold in Vasuda.
=====February:===== The last element of the Vasudan navy is forced out of Vasuda. The GTA begins building up forces for the invasion of Vasuda Prime.
=====March:===== Battle of Talnia. In an attempt to avenge the invasion of Vasuda, a group of Vasudan Admirals, under the leadership of Prince Imhotep, launch an attack on Talnia, destroying the Terran 6th fleet and the supply base there. After the raid, PVN command realized that the attack had crippled GTA supply lines, and orders the group to capitalize on their initial success. By then, the GTA had reinforced Talnia, and the fighting was much fiercer.
=====April:===== With their defenses weakened, the Vasudans launch a renewed attack on the Terrans in Vasuda, finally driving them out by May. The GTA orders Leviathan production resumed with new weapons and technologies.

===2328:===

=====February:===== First Cease-Fire established. After regaining lost territory, the Vasudans prepare for an assault on Terran systems when a rare Vasudan holiday comes up. Forced by religious leaders, the Vasudans offer the GTA a short cease-fire. The GTA eagerly accepts, and uses this time to establish new defensive lines. The cease-fire is ended before the treaty is half over with no progress toward a lasting peace.
=====March:===== Battle of Ribos. Using information gotten via a spy amongst the Vasudans, the GTA counters an invasion of Ribos by easily destroying the pride of the PVN fleet, the PVD Savior.

===2329:===

=====January:===== Second Cease-Fire established. Following a series of crushing defeats, the Vasudan parliament offers the GTA terms for a cease-fire during which a lasting peace treaty would be discussed. Negotiations lasted only an hour before breaking down, but the cease fire held until the beginning of February, during which the Vasudans strengthen their own lines.
=====August:===== Battle of Deneb-Sirius Node. After surprising Vasudan forces in Deneb, the GTA attempts to take the Deneb-Sirius node. The defeat at this battle begins a chain of defeats for Terran forces that would eventually force them into Beta Aquilea.
=====December:===== Third Cease-Fire established. In an attempt to stave off certain defeat, the GTA asks for a cease-fire during the holiday season. It is agreed to, and lasts the five days after Christmas. The GTA uses this time to reinforce its lines and prepare a counter attack it launches on New Yearâ€™s Eve day.

===2330:===

=====June:===== Betelgeuse Siege. After a dramatic counter-offensive, the Vasudans had managed to capture and hold Antares and Beta Cygni. It is decided by Prince Imhotep to lay siege to Betelgeuse and force the system to surrender. The siege lasts nearly six months, costing the Vasudans dearly. While they busied themselves trying to starve out Betelgeuse, the rest of the GTA attacked multiple supply bases in Antares, crippling PVN supply lines. By December, the Vasudans are forced to withdraw from Beta Cygni.

===2331:===

=====January:===== The Collapse of the [Talina] Nodes. Though known for their instability, the nodes to the Talina system had been stable enough for the GTA to use the system as a major supply dump. In late December 2330, however, the system was contested when a PVN fleet entered via the Vega system forcing the GTA to withdraw key equipment and personnel. By January Vasudan and Terran scientists had independently determined that both nodes into the system were due to collapse to an unusable state within only a few weeks. The commanding officers of both the GTA and PVN fleet called a cease-fire and jointly organized an evacuation of the system. By late February, the nodes were no longer stable for anything to travel through. For years it was hoped that the nodes would restabilize, but hopes would be dashed after the destruction of the Sol-Delta Serprentis node and the system was finally removed from maps.
=====March:===== Fourth Cease-Fire established. Considered the last serious attempt at peace, Vasudan and Terran officials meet for the bulk of the one-month cease-fire. Serious talks of an end to the war come up, but are dashed when no agreement is made.
=====November:===== Fifth Cease-Fire established. By odd coincidence, Terran and Vasudan election dates overlapped during 2331, encouraging the ruling groups to ask each other for a cease-fire so they could remain in power. The cease-fire lasts two days, and the ruling parties were both soundly defeated. There would be no further cease-fires until the arrival of the Shivans.

===2332:===

=====January:===== After being sworn in, Senator Williams makes a speech proclaiming that the Vasudans should be â€œbled whiteâ€ as the only way to win the war. Similar statements by Vasudan legislators trigger a stalemate in the war that lasts for the next three years.
=====March:===== Designs for the new Vasudan destroyer, the Typhon, are approved and construction begins in Altair. Any Saviors currently in production are scrapped and used to build the new warship.

====2333:====

=====March:===== Nearly one year to the day, the first Typhon, PVD Typhon, leaves the Altair shipyards. Its first assignment is to take Vega.
=====April:===== The Vega Engagement. The GTAâ€™s first encounter with the Typhon class destroyer ends with the destruction of the GTD Eisenhower and the 4th Fleet. The GTA launches a counter attack on Vega, forcing the Typhon to retreat but taking horrendous losses in the process.

====2334:====

=====June:===== Battle of Vega-Deneb Node. The last major battle of the 14-Year War sees the Terrans take the Vega side of the node. The first Typhon destroyed in combat occurs during the battle.
=====September:===== In an attack that surprised both sides, a second Typhon is destroyed in Antares.

====2335:====

=====January 8th:===== GTA launches Operation Thresher, also known as the Fifth Battle of the Vasuda-Antares Node. Initial losses cause Thresher to be declared a failure only two days after it started.

=====January 15th:===== The Shivans attack Vasudan and Terran forces near the Antares-Ribos node. The loss of the PVC Taurus and GTSC Plato lead towards cease fire proposal on the 18th by the Vasudans.

=====January 25th:===== GTA and PVE sign a cease-fire and non-aggression pact based on the [[Pan-Galactic Treaty]]. The 14-Year War officially comes to an end.

[[Unification]]''' :PREVIOUS | NEXT: '''[[The Great War]]

[[Category:History|14-Year War]]

Unification

2005-11-21T19:12:48Z

128.235.249.80: Added NEXT link.

Sometime during this period, [[Terrans]] discovered subspace, unified under the [[Galactic Terran Alliance]], explored the galaxy, and set up colonies in several systems. This timeline will cover from the discovery of [[Subspace]] to the first contact with the [[Vasudans]].

====2313:====
Discovery of Inter-system subspace travel. Start of the Unification War.
====2316:====
End of the Unification War. [[Galactic Terran Alliance]] formed.
====2319:====
September: First Orion class destroyer, [[GTD Orion]], completed.
====2320:====
March: First official contact with the [[Vasudan Parliamentary Empire]].

'''NEXT:''' [[The 14-Year War]]

Great War

2005-11-21T18:58:12Z

128.235.249.80: Removed Pinnacle. We're not sure about this and want to keep our options open, but we can assume there was another Typhon destroyed in the battle.