Difference between revisions of "Node Inconsistencies"
Goober5000 (talk | contribs) (→Ribos - Betelgeuse) |
Goober5000 (talk | contribs) m (update name) |
||
| (17 intermediate revisions by 6 users not shown) | |||
| Line 1: | Line 1: | ||
| + | [[Image:DuncanMacPhersonNodeMap.png|thumb|right|360px|From the notes of Duncan MacPherson]] | ||
Those continuation flaws that occur regarding jump nodes between FreeSpace: The Great War and FreeSpace 2 are called '''node inconsistencies'''. | Those continuation flaws that occur regarding jump nodes between FreeSpace: The Great War and FreeSpace 2 are called '''node inconsistencies'''. | ||
| − | There are a number of jump node connections that are used in [[Portal: | + | There are a number of jump node connections that are used in [[Portal:FreeSpace 1|FreeSpace]] but are not illustrated on the [[Official Volition Node Map]]. They are listed below, along with their references and how valid you should consider them. [[Volition]] says that the [[Official Volition Node Map|node map]] should overrule other references. |
| − | ==Pseudocanon | + | Some of these node inconsistencies can be explained by referring to a slightly different node map drawn by Duncan MacPherson during FS1's development, as seen to the right. |
| + | |||
| + | ==Pseudocanon== | ||
These connections are used in-game and would be considered canon if it weren't for the official map. | These connections are used in-game and would be considered canon if it weren't for the official map. | ||
| − | ===[[Beta Cygni]] - [[Ikeya]] | + | ===[[Beta Cygni]] - [[Ikeya]]=== |
| − | Used in First Strike (SM1-10). [[Famous | + | Used in [[First Strike]] (SM1-10). [[Famous persons|Admiral Wolf]] says that the [[SC Taranis|Taranis]] has been chased from the [[Beta Cygni]] system back to the [[Ikeya]] system, and the [[SC Taranis|Taranis]] is fleeing to the [[Beta Cygni]] node during the mission itself. It is very likely, however, that this is a mistake. The cutscene immediately preceding this mission (not to mention the official node map itself) shows that the only subspace node out of [[Ikeya]] leads to [[Ribos]]. Additionally, during the mission, Freighter Halkins tows the cruiser to Tombaugh Installation, which is located in [[Ribos]]. It is probable that the mission designer just confused [[Ribos]] with [[Beta Cygni]]. |
===[[Beta Cygni]] - [[Ribos]]=== | ===[[Beta Cygni]] - [[Ribos]]=== | ||
| − | Used by the shield prototype convoy in The Hammer and the Anvil (SM1-08). The shield prototypes are escorted from the Cygni Installation in [[Beta Cygni]] to the [[Ribos]] node. | + | Used by the shield prototype convoy in [[The Hammer and the Anvil]] (SM1-08). The shield prototypes are escorted from the Cygni Installation in [[Beta Cygni]] to the [[Ribos]] node. |
===[[Deneb]] - [[Altair]]=== | ===[[Deneb]] - [[Altair]]=== | ||
| − | Used by the player's squadron and Omega wing. The node is seen in Reaching the Zenith (SM3-04) and used in Running the Gauntlet (SM3-05) and Black Omega (SM3-06). Xenolinguists are transported to [[Altair]] to retrieve the ancient records and back to [[Deneb]] to rejoin the Terran fleet. | + | Used by the player's squadron and Omega wing. The node is seen in [[Reaching the Zenith]] (SM3-04) and used in [[Running the Gauntlet]] (SM3-05) and [[Black Omega]] (SM3-06). Xenolinguists are transported to [[Altair]] to retrieve the ancient records and back to [[Deneb]] to rejoin the Terran fleet. |
===[[Sirius]] - [[Delta Serpentis]]=== | ===[[Sirius]] - [[Delta Serpentis]]=== | ||
| − | Used by the [[GTD Bastion]] in Clash of the Titans (SM3-07). The Bastion tries to intercept the [[SD Lucifer]] before it can reach [[Sol]]. Also seen in CB_starmap13 and CB_starmap14. | + | Used by the [[GTD Bastion]] in [[Clash of the Titans]] (SM3-07). The Bastion tries to intercept the [[SD Lucifer]] before it can reach [[Sol]]. Also seen in CB_starmap13 and CB_starmap14. |
| − | + | ==Command Briefing Animation== | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | ==Command Briefing Animation | ||
These connections are shown in the animations that accompany the FS1 command briefings.<br><br> | These connections are shown in the animations that accompany the FS1 command briefings.<br><br> | ||
| Line 38: | Line 32: | ||
====[[Ribos]] - [[Betelgeuse]]==== | ====[[Ribos]] - [[Betelgeuse]]==== | ||
| − | Seen in CB_starmap06, although Betelgeuse isn't labeled. However, considering that the | + | Seen in CB_starmap06, although Betelgeuse isn't labeled. However, considering that the Command Briefing cutscene locates Ikeya where Betelgeuse should be, it is possible that this cbani is meant to refer to the Ribos-Ikeya node. |
====[[Ribos]] - [[Vega]]==== | ====[[Ribos]] - [[Vega]]==== | ||
| Line 52: | Line 46: | ||
====CB_starmap04==== | ====CB_starmap04==== | ||
| − | Is seen in La | + | Is seen in [[La Ruota della Fortuna]] (SM2-03), showing ships being attacked in [[Vega]] and subsequently jumping to [[Deneb]] and [[Antares]]. Admiral Wolf says that the Vasudan fleet is retreating after having been decimated by the [[Hammer of Light]]. |
====CB_starmap06==== | ====CB_starmap06==== | ||
| − | Is seen in Tenderizer (SM2-05), showing several possible jumps from Ribos through the surrounding systems. Admiral Wolf says that although there are dozens of star systems accessible from Ribos, the GTA can't afford to give up one more inch to the Shivans. | + | Is seen in [[Tenderizer]] (SM2-05), showing several possible jumps from [[Ribos]] through the surrounding systems. Admiral Wolf says that although there are dozens of star systems accessible from [[Ribos]], the [[GTA]] can't afford to give up one more inch to the [[Shivans]]. |
====CB_starmap08==== | ====CB_starmap08==== | ||
| − | Is seen in Enter the Dragon (SM2-07) and in Playing Judas (SM2-08), showing the Lucifer jumping from Ribos to Vega and the Galatea jumping from Beta Aquilae to Sol to Deneb. In Enter the Dragon, Admiral Wolf says that fighter patrols have detected advance ships from the Lucifer fleet approaching Vasuda Prime. In Playing Judas, Admiral Wolf says that the Galatea has entered Deneb to guard the system against the Deneb prong of the Shivan attack on Vasuda.<br><br> | + | Is seen in [[Enter the Dragon]] (SM2-07) and in [[Playing Judas]] (SM2-08), showing the Lucifer jumping from [[Ribos]] to [[Vega]] and the Galatea jumping from [[Beta Aquilae]] to [[Sol]] to [[Deneb]]. In [[Enter the Dragon]], Admiral Wolf says that fighter patrols have detected advance ships from the [[Lucifer]] fleet approaching [[Vasuda Prime]]. In [[Playing Judas]], Admiral Wolf says that the [[Galatea]] has entered [[Deneb]] to guard the system against the Deneb prong of the Shivan attack on Vasuda.<br><br> |
| − | ==Hearsay | + | ==Hearsay== |
| − | These connections are mentioned | + | These connections are mentioned but are not shown visually. |
===[[Betelgeuse]] - [[Antares]]=== | ===[[Betelgeuse]] - [[Antares]]=== | ||
| − | Mentioned in The Field of Battle (SM1-02). Admiral Wolf says that Vasudans have been conducting strikes on Terran convoys en route to the Betelgeuse-Antares jump point. This jump corridor may also be alluded to in Paving the Way (SM1-06) when Admiral Wolf says that standard procedure would have the Galatea circumvent the Antares-Beta Cygni jump corridor and make two jumps. Jumping from Antares to Betelgeuse to Beta Cygni would satisfy this requirement. (But so would Antares to Ribos to Beta Cygni, through the pseudocanon Ribos-Beta Cygni corridor.) | + | Mentioned in [[The Field of Battle]] (SM1-02). Admiral Wolf says that Vasudans have been conducting strikes on Terran convoys en route to the Betelgeuse-Antares jump point. This jump corridor may also be alluded to in [[Paving the Way]] (SM1-06) when Admiral Wolf says that standard procedure would have the Galatea circumvent the Antares-Beta Cygni jump corridor and make two jumps. Jumping from [[Antares]] to [[Betelgeuse]] to [[Beta Cygni]] would satisfy this requirement. (But so would Antares to [[Ribos]] to Beta Cygni, through the pseudocanon Ribos-Beta Cygni corridor.) |
| − | ==Implied | + | ===[[Deneb]] - [[Alpha Centauri]]=== |
| + | Mentioned in [[Surrender, Belisarius!]] (SM1-01). Allied Command orders the [[GVD Psamtik]] to the otherwise unreferenced [[Alpha Centauri]] jump node. | ||
| + | |||
| + | ==Implied== | ||
These connections are only implied, not described or illustrated. | These connections are only implied, not described or illustrated. | ||
===[[Beta Aquilae]] - [[Vasuda]]=== | ===[[Beta Aquilae]] - [[Vasuda]]=== | ||
| − | Implied in Tenderizer (SM2-05). Admiral Wolf says that the Galatea will be moving to Beta Aquilae in case the Shivans decide to attack Vasuda Prime through there. This implies that there is a jump corridor from Beta Aquilae to Vasuda. The shortest alternate route, starting from Beta Aquilae, involves three jumps: Vega to Deneb to Vasuda, or Sol to Deneb to Vasuda. (Of course, since they start in Antares, the Shivans could simply pulverize the Terran blockade and jump directly to Vasuda, but for whatever reason they don't decide to do that.) | + | Implied in [[Tenderizer]] (SM2-05). Admiral Wolf says that the [[Galatea]] will be moving to [[Beta Aquilae]] in case the [[Shivans]] decide to attack [[Vasuda Prime]] through there. This implies that there is a jump corridor from Beta Aquilae to Vasuda. The shortest alternate route, starting from Beta Aquilae, involves three jumps: [[Vega]] to [[Deneb]] to [[Vasuda]], or [[Sol]] to Deneb to Vasuda. (Of course, since they start in Antares, the Shivans could simply pulverize the Terran blockade and jump directly to Vasuda, but for whatever reason they don't decide to do that.) |
| + | |||
| + | |||
| + | ==Related Links== | ||
| + | |||
| + | [https://www.hard-light.net/forums/index.php?topic=99153.0 Duncan McPherson Blog | Hard-Light Productions.net] | ||
| + | [https://duncanmakesgames.wordpress.com/2017/05/24/from-the-vaults-of-game-design/ From the Vault of Game Design | Duncan Makes Games] | ||
[[Category:Stars and Planets]] | [[Category:Stars and Planets]] | ||
Latest revision as of 00:18, 18 February 2024
Those continuation flaws that occur regarding jump nodes between FreeSpace: The Great War and FreeSpace 2 are called node inconsistencies.
There are a number of jump node connections that are used in FreeSpace but are not illustrated on the Official Volition Node Map. They are listed below, along with their references and how valid you should consider them. Volition says that the node map should overrule other references.
Some of these node inconsistencies can be explained by referring to a slightly different node map drawn by Duncan MacPherson during FS1's development, as seen to the right.
Pseudocanon
These connections are used in-game and would be considered canon if it weren't for the official map.
Beta Cygni - Ikeya
Used in First Strike (SM1-10). Admiral Wolf says that the Taranis has been chased from the Beta Cygni system back to the Ikeya system, and the Taranis is fleeing to the Beta Cygni node during the mission itself. It is very likely, however, that this is a mistake. The cutscene immediately preceding this mission (not to mention the official node map itself) shows that the only subspace node out of Ikeya leads to Ribos. Additionally, during the mission, Freighter Halkins tows the cruiser to Tombaugh Installation, which is located in Ribos. It is probable that the mission designer just confused Ribos with Beta Cygni.
Beta Cygni - Ribos
Used by the shield prototype convoy in The Hammer and the Anvil (SM1-08). The shield prototypes are escorted from the Cygni Installation in Beta Cygni to the Ribos node.
Deneb - Altair
Used by the player's squadron and Omega wing. The node is seen in Reaching the Zenith (SM3-04) and used in Running the Gauntlet (SM3-05) and Black Omega (SM3-06). Xenolinguists are transported to Altair to retrieve the ancient records and back to Deneb to rejoin the Terran fleet.
Sirius - Delta Serpentis
Used by the GTD Bastion in Clash of the Titans (SM3-07). The Bastion tries to intercept the SD Lucifer before it can reach Sol. Also seen in CB_starmap13 and CB_starmap14.
Command Briefing Animation
These connections are shown in the animations that accompany the FS1 command briefings.
Jump Nodes
Beta Aquilae - Sol
Seen in CB_starmap06 and in CB_starmap08
Ribos - Betelgeuse
Seen in CB_starmap06, although Betelgeuse isn't labeled. However, considering that the Command Briefing cutscene locates Ikeya where Betelgeuse should be, it is possible that this cbani is meant to refer to the Ribos-Ikeya node.
Ribos - Vega
Seen in CB_starmap08, although the jump line isn't explicitly drawn
Sol - Deneb
Seen in CB_starmap08
Vega - Antares
Seen in CB_starmap04, although the jump line isn't explicitly drawn
Animation Usage
CB_starmap04
Is seen in La Ruota della Fortuna (SM2-03), showing ships being attacked in Vega and subsequently jumping to Deneb and Antares. Admiral Wolf says that the Vasudan fleet is retreating after having been decimated by the Hammer of Light.
CB_starmap06
Is seen in Tenderizer (SM2-05), showing several possible jumps from Ribos through the surrounding systems. Admiral Wolf says that although there are dozens of star systems accessible from Ribos, the GTA can't afford to give up one more inch to the Shivans.
CB_starmap08
Is seen in Enter the Dragon (SM2-07) and in Playing Judas (SM2-08), showing the Lucifer jumping from Ribos to Vega and the Galatea jumping from Beta Aquilae to Sol to Deneb. In Enter the Dragon, Admiral Wolf says that fighter patrols have detected advance ships from the Lucifer fleet approaching Vasuda Prime. In Playing Judas, Admiral Wolf says that the Galatea has entered Deneb to guard the system against the Deneb prong of the Shivan attack on Vasuda.
Hearsay
These connections are mentioned but are not shown visually.
Betelgeuse - Antares
Mentioned in The Field of Battle (SM1-02). Admiral Wolf says that Vasudans have been conducting strikes on Terran convoys en route to the Betelgeuse-Antares jump point. This jump corridor may also be alluded to in Paving the Way (SM1-06) when Admiral Wolf says that standard procedure would have the Galatea circumvent the Antares-Beta Cygni jump corridor and make two jumps. Jumping from Antares to Betelgeuse to Beta Cygni would satisfy this requirement. (But so would Antares to Ribos to Beta Cygni, through the pseudocanon Ribos-Beta Cygni corridor.)
Deneb - Alpha Centauri
Mentioned in Surrender, Belisarius! (SM1-01). Allied Command orders the GVD Psamtik to the otherwise unreferenced Alpha Centauri jump node.
Implied
These connections are only implied, not described or illustrated.
Beta Aquilae - Vasuda
Implied in Tenderizer (SM2-05). Admiral Wolf says that the Galatea will be moving to Beta Aquilae in case the Shivans decide to attack Vasuda Prime through there. This implies that there is a jump corridor from Beta Aquilae to Vasuda. The shortest alternate route, starting from Beta Aquilae, involves three jumps: Vega to Deneb to Vasuda, or Sol to Deneb to Vasuda. (Of course, since they start in Antares, the Shivans could simply pulverize the Terran blockade and jump directly to Vasuda, but for whatever reason they don't decide to do that.)
