Editing Trailblazer (Individual JumpShip)
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision
Your text
Line 1:
Line 1: − {{Otheruses|the exploration JumpShip|other uses|Trailblazer}} + {{Otheruses|the exploration [[JumpShip]]|other uses|Trailblazer (disambiguation)}} {{InfoBoxIndividualSpacecraft {{InfoBoxIndividualSpacecraft | image = | image = Line 11:
Line 11: }} }} ==Description== ==Description== − Launched in [[2655]], the '''''Trailblazer''''' was an exploration [[JumpShip]] put on an ambitious mission to map and survey unexplored star systems, under the command of Commodore [[Niamola Bendricks]]. (The mission name was given as ''Trailblazer One'', while the ship itself was consistently named the ''Trailblazer'').<ref name=SLp60>''The Star League'', p. 60: "Mysterious Disaster Ends Trailblazer Mission"</ref> + Launched in [[2655]], the '''''Trailblazer''''' was an exploration [[JumpShip]] put on an ambitious mission to map and survey unexplored star systems, under the command of Commodore [[Niamola Bendricks]]. (The mission name was given as ''Trailblazer One'', while the ship itself was consistently named the ''Trailblazer'').<ref name=SLp60>''The Star League'', p. 60</ref> The exact class of the ''Trailblazer'' was not mentioned. Its notable features (see Notes below) include reportedly featuring not one but three [[jump drive]]s, and being capable of deploying a HPG beacon which indicates it carried an [[HPG]]. The exact class of the ''Trailblazer'' was not mentioned. Its notable features (see Notes below) include reportedly featuring not one but three [[jump drive]]s, and being capable of deploying a HPG beacon which indicates it carried an [[HPG]]. Line 23:
Line 23: ==Notes== ==Notes== − * Mentioned only in a sidebar in one of the earliest [[BattleTech]] sourcebooks, the ''Trailblazer'' story is difficult to reconcile with more detailed information about jump drives and HPG technology that was published later on: + *Mentioned only in a sidebar in one of the earliest [[BattleTech]] sourcebooks, the ''Trailblazer'' story is difficult to reconcile with more detailed information about jump drives and HPG technology that was published later on: − ** Published information about the (fictional) [[jump drive|Kearny-Fuchida jump drive]] technology strongly implies that it should be impossible for a single vessel to possess more than one jump drive core. It is impossible under current (or any previous) construction rules to design such a ship. There are no obvious advantages to combining three separate jump drive cores on one ship either.<br />A possible canon-compliant explanation would be a setup by which three Kearny-Fuchida drive cores are linked for simultaneous jumps in a fashion similar to the [[Ryan Cartel]] [[IceShip]] fleets, but form a single vessel instead of separate vessels jumping in unison. For the ''Trailblazer'' to be a single ship the drive cores would have been physically linked permanently by means of the "circuit junction" that was hit by the meteorite. + **Published information about the (fictional) [[jump drive|Kearny-Fuchida jump drive]] technology strongly implies that it should be impossible for a single vessel to possess more than one jump drive core. It is impossible under current (or any previous) construction rules to design such a ship. There are no obvious advantages to combining three separate jump drive cores on one ship either.<br />A possible canon-compliant explanation would be a setup by which three Kearny-Fuchida drive cores are linked for simultaneous jumps in a fashion similar to the [[Ryan Cartel]] [[IceShip]] fleets, but form a single vessel instead of separate vessels jumping in unison. For the ''Trailblazer'' to be a single ship the drive cores would have been physically linked permanently by means of the "circuit junction" that was hit by the meteorite. − ** Similarly, the idea of an "HPG transponder signal" or that the source of an HPG signal could be traced is not easily compatible with existing theories on how HPGs work. It could be assumed that the ''Trailblazer'' used its HPG to send distress radio signals containing the ship's transponder code and data on their current position to several nearby systems, one of which was eventually picked up. Alternatively, it could be an inaccurate description of a [[Jump Pigeon]] system. + **Similarly, the idea of an "HPG transponder signal" or that the source of an HPG signal could be traced is not easily compatible with existing theories on how HPGs work. It could be assumed that the ''Trailblazer'' used its HPG to send distress radio signals containing the ship's transponder code and data on their current position to several nearby systems, one of which was eventually picked up. Alternatively, it could be an inaccurate description of a [[Jump Pigeon]] system. ==References== ==References== Line 31:
Line 31: ==Bibliography== ==Bibliography== − * ''[[The Star League]]'' + * ''[[The Star League]]'' (sourcebook) [[Category:Individual JumpShips]] [[Category:Individual JumpShips]]
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| − | {{Otheruses|the exploration JumpShip|other uses|Trailblazer}} | + | {{Otheruses|the exploration [[JumpShip]]|other uses|Trailblazer (disambiguation)}} |
{{InfoBoxIndividualSpacecraft | {{InfoBoxIndividualSpacecraft | ||
| image = | | image = | ||
| Line 11: | Line 11: | ||
}} | }} | ||
==Description== | ==Description== | ||
| − | Launched in [[2655]], the '''''Trailblazer''''' was an exploration [[JumpShip]] put on an ambitious mission to map and survey unexplored star systems, under the command of Commodore [[Niamola Bendricks]]. (The mission name was given as ''Trailblazer One'', while the ship itself was consistently named the ''Trailblazer'').<ref name=SLp60>''The Star League'', p. 60 | + | Launched in [[2655]], the '''''Trailblazer''''' was an exploration [[JumpShip]] put on an ambitious mission to map and survey unexplored star systems, under the command of Commodore [[Niamola Bendricks]]. (The mission name was given as ''Trailblazer One'', while the ship itself was consistently named the ''Trailblazer'').<ref name=SLp60>''The Star League'', p. 60</ref> |
The exact class of the ''Trailblazer'' was not mentioned. Its notable features (see Notes below) include reportedly featuring not one but three [[jump drive]]s, and being capable of deploying a HPG beacon which indicates it carried an [[HPG]]. | The exact class of the ''Trailblazer'' was not mentioned. Its notable features (see Notes below) include reportedly featuring not one but three [[jump drive]]s, and being capable of deploying a HPG beacon which indicates it carried an [[HPG]]. | ||
| Line 23: | Line 23: | ||
==Notes== | ==Notes== | ||
| − | * Mentioned only in a sidebar in one of the earliest [[BattleTech]] sourcebooks, the ''Trailblazer'' story is difficult to reconcile with more detailed information about jump drives and HPG technology that was published later on: | + | *Mentioned only in a sidebar in one of the earliest [[BattleTech]] sourcebooks, the ''Trailblazer'' story is difficult to reconcile with more detailed information about jump drives and HPG technology that was published later on: |
| − | ** Published information about the (fictional) [[jump drive|Kearny-Fuchida jump drive]] technology strongly implies that it should be impossible for a single vessel to possess more than one jump drive core. It is impossible under current (or any previous) construction rules to design such a ship. There are no obvious advantages to combining three separate jump drive cores on one ship either.<br />A possible canon-compliant explanation would be a setup by which three Kearny-Fuchida drive cores are linked for simultaneous jumps in a fashion similar to the [[Ryan Cartel]] [[IceShip]] fleets, but form a single vessel instead of separate vessels jumping in unison. For the ''Trailblazer'' to be a single ship the drive cores would have been physically linked permanently by means of the "circuit junction" that was hit by the meteorite. | + | **Published information about the (fictional) [[jump drive|Kearny-Fuchida jump drive]] technology strongly implies that it should be impossible for a single vessel to possess more than one jump drive core. It is impossible under current (or any previous) construction rules to design such a ship. There are no obvious advantages to combining three separate jump drive cores on one ship either.<br />A possible canon-compliant explanation would be a setup by which three Kearny-Fuchida drive cores are linked for simultaneous jumps in a fashion similar to the [[Ryan Cartel]] [[IceShip]] fleets, but form a single vessel instead of separate vessels jumping in unison. For the ''Trailblazer'' to be a single ship the drive cores would have been physically linked permanently by means of the "circuit junction" that was hit by the meteorite. |
| − | ** Similarly, the idea of an "HPG transponder signal" or that the source of an HPG signal could be traced is not easily compatible with existing theories on how HPGs work. It could be assumed that the ''Trailblazer'' used its HPG to send distress radio signals containing the ship's transponder code and data on their current position to several nearby systems, one of which was eventually picked up. Alternatively, it could be an inaccurate description of a [[Jump Pigeon]] system. | + | **Similarly, the idea of an "HPG transponder signal" or that the source of an HPG signal could be traced is not easily compatible with existing theories on how HPGs work. It could be assumed that the ''Trailblazer'' used its HPG to send distress radio signals containing the ship's transponder code and data on their current position to several nearby systems, one of which was eventually picked up. Alternatively, it could be an inaccurate description of a [[Jump Pigeon]] system. |
==References== | ==References== | ||
| Line 31: | Line 31: | ||
==Bibliography== | ==Bibliography== | ||
| − | * ''[[The Star League]]'' | + | * ''[[The Star League]]'' (sourcebook) |
[[Category:Individual JumpShips]] | [[Category:Individual JumpShips]] | ||