691
Gaming / Re: Pokémon Sword & Shield for Nintendo Switch revealed
« on: May 29, 2019, 09:59:55 PM »
I dont know why we're getting Pokemon Sleep when Ultra Sun and Moon already exist.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to. 691
Gaming / Re: Pokémon Sword & Shield for Nintendo Switch revealed« on: May 29, 2019, 09:59:55 PM »
I dont know why we're getting Pokemon Sleep when Ultra Sun and Moon already exist.
692
Gaming / Re: Super Smash Brothers« on: May 29, 2019, 06:19:16 PM »
The matchmaking gets better all the time
693
The Flood / Re: What the duce is going on in this chinese finger painting forum?« on: May 28, 2019, 08:04:05 PM »
Oh terrific, as if Carmen alone wasn't bad enough.
694
Gaming / Re: Super Smash Brothers« on: May 28, 2019, 02:32:41 AM »
3.1.0 patch notes
-Stage builder removed. Anyone who downloaded "Konosuba Aqua" will have a KEM strike ordered on their house. -Samus/Dark Samus automatically dies by pressing b -Input lag increased by 30 frames -All Metroid Music replaced by tracks from Other M and Federation force -Ridley's tail attack now has the same cool down as rest -All Marth alternate colors are now their own charachter slots -All Hyper Armor frames quadrupled -Selecting 3 stock Battlefield no items now garuntees you will be matched against 3 Snakes or Mii Gunners on Great Cave offensive in a timed match with all items spirits and custom ballancing enabled -Taunting, even offline will immediately notify Sakurai's who with personally come to your house to disembowel you with a rusty spork. -Shiek's hotboxes removed and replaced by hurtboxes -Network ramping and DDos tutorials added to tips 695
The Flood / Re: My discord server nearly got deleted!!!!!« on: May 27, 2019, 11:53:58 PM »
[Science-Fiction Wiki Article]
696
The Flood / Re: Prince Ali new Aladdin -- (this movie looks good and I'm excited to see it)« on: May 27, 2019, 05:49:01 PM »
That was literally the most painfully average musical number I've seen in my life
MEMORY ALPHA MEMORY ALPHA Sovereign class Sovereign class.jpg OWNER: United Federation of Planets OPERATOR: Starfleet ACTIVE: 2370s LENGTH: 685 meters DECKS: Variable (see "Physical arrangement") SPEED: Warp 8 (see "Propulsion systems") ARMAMENT: Before refit: 12 phaser arrays 1 forward quantum torpedo launcher 2 forward photon torpedo launcher 3 aft photon torpedo launchers After refit: 16 phaser arrays 1 forward quantum torpedo launcher 3 forward photon torpedo launchers 6 aft photon torpedo launchers DEFENSES: Deflector shields The Sovereign-class starship was introduced in the late 24th century, showcasing some of Starfleet's most recent technological advances. History USS Enterprise-E in drydock 2.jpg The USS Enterprise-E in drydock over Earth in 2379 The Sovereign-class was introduced during the early 2370s, and was, at the time, the most advanced starship design in the fleet, though not as large as the Galaxy-class starship. The Sovereign-class USS Enterprise-E was built at the San Francisco Fleet Yards and was launched from that facility on stardate 49827.5. (Star Trek: First Contact dedication plaque) USS Enterprise-E engages Borg at 001.jpg The USS Enterprise-E firing at the Borg cube at the Battle of Sector 001 The Sovereign class' first major engagements came in 2373, when the USS Enterprise saw action in the Borg incursion into Sector 001, and was instrumental in the destruction of the attacking cube. (Star Trek: First Contact) While the Sovereign-class was not a key player in the Dominion War, such vessels as the Enterprise-E spent time during the war putting out diplomatic "brush fires" and extending the occasional olive branch, as the Federation Diplomatic Corps were busy attempting to put an end to the war. (Star Trek: Insurrection) Sometime after the Enterprise's mission in the Briar Patch and before the engagement with the Reman warship Scimitar, a refitting of the Enterprise-E took place. The major changes included five additional torpedo tubes and four additional phaser arrays. A slight change in the warp nacelle pylons was also implemented. The Enterprise was able to deploy these new systems in 2379, prior to its mission to Romulus. (Star Trek Nemesis) Technical data Physical arrangement Sovereign side view.jpg Port-side overview Nearly seven hundred meters in length, the design of the Sovereign-class consisted of two hull sections: a saucer-shaped primary hull and a secondary hull which mounted two warp nacelles. (Star Trek: First Contact) Rick Sternbach unambiguously mapped 23 decks to the Enterprise exterior in his construction blueprints for the ten-foot miniature, which were reproduced in Star Trek: The Next Generation Sketchbook: The Movies. The ship is stated, by Captain Jean-Luc Picard in Star Trek: First Contact, as having 24 decks. In the same film, however, Lieutenant Daniels refers to a deck 26. Likewise, Lieutenant Commanders Data and Worf both refer to deck 29 in Star Trek Nemesis. The Sovereign-class MSD, seen in both films, shows 23 or 24 decks (depending on the interpretation of the lowest deck space). Tactical systems Deflector status display, Sovereign class.jpg Deflector shields on display The Sovereign-class starship had several weaponry enhancements over previous starship classes, including quantum torpedoes as well as photon torpedoes, and numerous phaser banks and arrays. USS Enterprise-E attacks the Scimitar.png The USS Enterprise-E attacks the Scimitar The Sovereign-class originally employed twelve phaser arrays at key locations throughout the ship's hull. Seven dorsal phaser arrays were located on the primary hull, one extending around the saucer section, giving it an oval appearance. Six smaller arrays covered the aft dorsal firing arcs and were located along the aft portion of the saucer section, above the main shuttlebay. Four ventral phaser arrays were located on the primary hull, extending around in nearly a half circle on both the starboard and port ventral sides of the saucer section. A single phaser array was located along the ventral section of the engineering hull, running perpendicular to the hull. (Star Trek: First Contact; Star Trek: Insurrection) During the refit, four were added to the trailing edges of the warp nacelle pylons (one dorsal and one ventral for each pylon) bringing the phaser array count to sixteen. (Star Trek Nemesis) File:USS Enterprise-E fires full phaser spread.jpg File:Sovereign class engineering hull torpedo launcher.jpg File:USS Enterprise-E firing quantum torpedoes.jpg In her original configuration, the Sovereign-class mounted five torpedo launchers. The "main" launcher was located on the ventral portion of the saucer on a turret and was supplemented by one twin-tube launcher, forward and aft at the bottom of the secondary hull. The refit saw the addition of five more tubes: three on the dorsal saucer section (a single tube facing forward on deck 3 and a twin-tube launcher facing aft [located above the aft saucer airlock]) as well as two on the secondary hull, both facing aft – one above and one below the secondary hull shuttlebay. (Star Trek: First Contact; Star Trek Nemesis) Interior design Layout Enterprise-E MSD.jpg The USS Enterprise-E's Master Systems Display on the bridge In terms of deck layout, the upper sections of the Sovereign-class starship formed the command section and living areas, while the lower decks housed main engineering and fuel supplies. As is traditional, deck numbering ascended from top to bottom. At the top of the saucer section was Deck 1, which housed the main bridge. This deck also held the more recent modifications of an observation lounge, a ready room for the ship's captain, and an airlock with attached cabin. EnterpriseECorridor3.jpg A typical Sovereign-class corridor Deck 2 encompassed the first of the many levels of crew quarters, with rooms for the highest-ranking command staff and an officer's mess hall. Decks 3 through 9 featured more officers' quarters, the forward and aft viewing lounges, science labs, the main shuttlebay, conduits for the optical data network, and the vessel's main computer core. Decks 10 through 14 completed the primary hull of the Sovereign-class starship, and also encompassed forward and aft cargo bays on decks 10 and 11, and phaser systems on deck 11. The stellar cartography department aboard the Sovereign-class was located on deck 11. Sensors and the secondary navigational deflector were found on deck 12. EnterpriseE corridor.jpg A Sovereign-class corridor at red alert Deck 13, which was taken up almost entirely by deuterium fuel tanks, marked the real split between the habitable areas and the engineering and ship's storage sections. Main engineering and its related systems – such as the EPS power taps, the central matter/antimatter reaction chamber, support labs, and the engineering computer core – were spread over decks 14 through 18. Deck 14 was largely dedicated to engineering systems, and also featured the lower sensor platform. Decks 15 through 18 comprised the main navigational deflector array and an auxiliary bridge, which was also known as the battle bridge. Deck 16 also featured the launch and retrieval mechanism for the captain's yacht. The yacht was lowered by a set of gantries until its engines extended to operational position and then it would be free to maneuver. Starfleet Cartography.jpg A Sovereign-class astrometrics lab The Sovereign-class was also equipped with an astrometrics lab where a direct uplink with Starfleet Cartography could be established. Interference from nearby astronomical phenomena could interfere with the lab's link with Starfleet Cartography. (Star Trek: First Contact; Star Trek: Insurrection; Star Trek Nemesis; MSD okudagram) Command and control systems The computer system on board the Sovereign-class were bio-neural gel pack-based. Computer systems were concentrated in two computer cores. The primary core was located directly below the main bridge on decks 6 through 8. The secondary core was located in the engineering section, adjacent to environmental control, on decks 15 through 17. Sovereign Bridge2.jpg Main bridge of a Sovereign-class starship Primary operational control of the ship was provided by the main bridge, located at the top of the primary hull. The bridge directly supervised all primary mission operations and coordinated all departmental activities. Sovereign class bridge.jpg Main bridge of a Sovereign-class starship in 2373 The central area of the main bridge provided seating and information displays for the captain and two other officers. The captain's chair was raised from the rest of the bridge officers to the height of the surrounding level, which included tactical and operations. The two officer seats were equipped with fully programmable consoles for a variety of uses. Directly fore of the command area was the conn officer, who faced the main viewer. To the port side of the conn officer, also facing the main viewscreen, was the operations officer's console, which was identical in size and design to the helm station. Sovereign Viewscreen.jpg The Ops and Conn stations in front of the viewscreen At the very front of the bridge chamber was a large viewscreen. When the screen was not active, a standard bulkhead was present. Aft and to the left of the command area was an elevated platform on which tactical and security consoles were located. To the captain's right, behind the tactical console, was the mission operations section of the bridge. Against the starboard side walls of the main bridge were the consoles for sciences, along with others that were programmable for a multitude of functions. Sovereign observation lounge (2379).jpg The observation lounge Located against the aft wall of the bridge was a large master systems display monitor, similar to the one in engineering. All relevant ship information (such as damage, power distribution, etc.) could be displayed on this cutaway image of the vessel. This monitor could be used to direct ship operations and could be configured for limited flight control if necessary. Also located against the aft wall of the main bridge was the large engineering console. This had a smaller cutaway diagram of the vessel, which displayed all engineering-relevant data and showed warp fields and engine output. There were two turbolifts on the bridge. There was also an emergency ladder that connected the bridge to lower decks. Additionally, the bridge provided direct access to the observation lounge, which was located directly aft of the bridge, and the captain's ready room. (Star Trek: First Contact) Ready room Sovereign Ready Room.jpg The ready room The captain's ready room doubled as an office and a second private cabin in addition to the commanding officer's private quarters. It was located off the starboard side of the main bridge on deck 1, and provided a place where the captain could work or rest while remaining next to the bridge in case of an emergency. Meetings between the captain and one or two people would also take place here. In one corner there was a simple, narrow bed with a small bookcase over it. Toward the rear of the room was a desk with a computer console. In a corner behind the desk was a doorway which led into a bathroom containing a sonic shower. Below a mirror was a sink that had no visible controls; the water came on automatically when hands were placed beneath the faucet, and went off when they were withdrawn. Usually, the ready room would be decorated by its occupant by adding a number of personal ornaments. Propulsion systems USS Enterprise-E at impulse.jpg Sovereign Coils.jpg Sovereign-class starships achieved warp flight through two warp nacelles, which housed multiple pairs of warp coils. It could achieve warp factor 8. (Star Trek Nemesis) Warp 8 is the highest speed a Sovereign-class ship was known to have traveled on-screen. According to Star Trek: Starship Spotter, the maximum warp of the Sovereign-class ship was warp factor 9.7. However, Star Trek Evolutions gives the Sovereign a maximum warp of 9.985. The latest edition of "Star Trek: Ships of the Line" gives the Sovereign class a maximum warp speed of 9.995. There were two impulse engines, both located at the aft of the saucer section. (Star Trek: First Contact) Main engineering contained the controls for the warp and impulse drive systems. Entrance to the primary engineering spaces was provided by two large blast doors, a pair each deck on decks 15 and 16, that could be closed for internal or external security reasons, as well as in case of emergencies. It was much larger than on previous starship classes and was split into three levels to accommodate the warp core, which spanned several decks. The majority of controls were situated on the main deck (deck 16) and an upper level gantry. Arranged around the warp core stack were a number of control consoles that could be reconfigured to emulate all the command controls on the bridge. The largest work station was the master systems display, which was used to monitor the status of all key systems and could comfortably accommodate four personnel. There were also various wall displays, including a schematic that showed the 'health' of the warp propulsion system. The deuterium tanks were above the core, while antimatter storage pods surrounded the base of the core. Two large cylindrical tanks were positioned next to the warp core and contained highly dangerous plasma coolant. Two rectangular power transfer conduits fed off from the warp reaction chamber and angle out of main engineering to the port and starboard warp nacelles. (Star Trek: Insurrection) Sovereign Warp Core.jpg Sovereign Engineering.jpg Additionally, there were numerous ladders and access panels to Jefferies tubes, leading throughout the starship. A second tier ringed the second level of main engineering on deck 15. Two ladders on the opposite ends of the catwalk provided access. (Star Trek: First Contact) By 2379, Starfleet began implementing a force field system around the warp reactor. (Star Trek Nemesis) It is unknown at this time exactly what role the reactor core force field played in protecting the ship. During its only shown use, the force field was disabled in battle mere minutes after it was activated. How this helps the ship is a mystery due to the lack of a force field around the reaction chamber. However, this could possibly be to protect it when the engineering crew fights intruders. A similar tactic was employed in "Day of Honor" by B'Elanna Torres when she had a level 10 force field surround USS Voyager's main engineering right before she ejected the warp core. It may also help contain a warp core breach and stop, or slow it, from spreading. USS Enterprise-E warp core ejection.jpg USS Enterprise-E's ejected warpcore The Sovereign-class was equipped with a warp core ejection system. Normally used as a last resort measure when a warp core breach was in progress, in 2375 the Enterprise-E used the capability in order to seal a subspace rift, caused by the Son'a, by remote detonating the ejected core. (Star Trek: Insurrection) A detailed exterior ejection sequence was designed by John Eaves for the scene. But to his disappointment only a very short shot was actually seen on screen. [1] Transporter systems Enterprise-E transporter.jpg The back wall of a Sovereign-class transporter The Sovereign-class starship included at least four separate transporter rooms, capable of site-to-site transport. (Star Trek Nemesis) Unusually, the transporter console in a Sovereign-class transporter room was built into a wall opposite the transporter platform, from where the controls on the console could be seen. (Star Trek: Insurrection) The transporters could be operated from both the tactical and engineering stations on the ship's bridge. A Sovereign-class starship was capable of beaming a single small vessel – such as a Scorpion-class attack fighter – aboard, even if the smaller craft was mobile. (Star Trek Nemesis) A Sovereign-class transporter room made only a brief appearance in Star Trek: Insurrection. Its omission from Star Trek: First Contact was the first time in the Star Trek film series that the transporter room did not appear. Crew support systems The Sovereign-class starship had the usual array of amenities available to the crew, including holodecks, gymnasiums, a ship's library, etc. It seems that Sovereign-class starships did not have the extensive provisions for civilian personnel that her Galaxy-class predecessors were designed with, as no civilians were seen on board. Married personnel, however, were permitted to share quarters. (Star Trek Nemesis) Medical facilities Sovereign Sickbay.jpg EMH in Enterprise-E sickbay.jpg One large sickbay facility, located on deck 7, served as the primary care facility on Sovereign-class starships. Equipped with six standard and one advanced biobed, sickbay was also home to the chief medical officer's office and a small lab used for routine analysis of patients. (Star Trek Nemesis) A second, smaller facility identical to an Intrepid-class sickbay was also present on deck 16. (Star Trek: First Contact) This was a reuse of the standing set used on Star Trek: Voyager. Since only a single short scene was to take place here, the set was relit and used with minimal alterations to save budget. The room itself was considered to be general purpose, and was often the location of regular crew physicals, appointments, and various medical emergencies – it could effectively handle the majority of situations that a starship crew would face. (Star Trek: First Contact) Sovereign-class starships were equipped with an Emergency Medical Hologram. (Star Trek: First Contact) Located near sickbay was the counselor's office, a modest room approximately the size of a standard living room compartment. (Star Trek: Insurrection) Crew quarters Sovereign Crew Quarters.jpg Sovereign Crew Quarters bedroom.jpg The arrangement of living quarters was designed to be modular, so that at any time a particular area could be reconfigured to create larger or smaller residential areas. Most living areas were located on the upper and lower surfaces of the saucer section, offering residents a remarkable view of the starscape outside their windows. As was common on Starfleet vessels, the living accommodations for senior officers and VIPs were larger than standard crew quarters. Officers' quarters usually included a living area in the center of the dwelling, which held a personal workstation, couch, replicator, and a small dining area. Connected to this was a bedroom that featured a double-sized bed and room for personal belongings. Normally, the bedroom would be connected by a half-bathroom with wash basin, mirror, toilet, several drawers, and a sonic shower. For senior staff, this bathroom was usually upgraded to a full-sized bathroom with bathtub. (Star Trek: Insurrection) Auxiliary spacecraft systems Located at the dorsal stern of the primary hull, the main shuttlebay took up a significant portion of the aft section of decks 6 through 9 on the Sovereign-class. Due to the mission profile of the Sovereign, the shuttlebay extended further than normal for a vessel its size to accommodate runabouts and several shuttlecraft. The secondary shuttlebay was located at the very aft portion of the engineering hull. This bay, while smaller than the main facility, was just as capable of handling flight operations as the main shuttlebay. (Star Trek: First Contact) In addition to shuttlecraft, the Sovereign class also featured a captain's yacht, designed for special diplomatic missions. The yacht on board the Enterprise-E was named the Cousteau. (Star Trek: Insurrection) Escape pods The Sovereign-class starship carried a number of escape pods. In the event of a catastrophic emergency, these pods served the same purpose as the lifeboats of a water-based vessel and ensured the continued survival of passengers and crew after the primary vessel had to be abandoned. The escape pods were located throughout the Sovereign-class starship's primary and secondary hulls: there were two rows of pods on the dorsal side of the command saucer, and two on the ventral side. Further rows of pods lined each side of the engineering hull. Unlike the escape pods utilized on the Galaxy- and Intrepid-class, there was no outer hatch that opened for launch. (VOY: "Year of Hell") Instead, the heat shield of the escape pod lay flush with the Sovereign-class ship's outer hull. Personnel entered the pods through hatches that lined sections of the ship's corridors, and a situation display monitor was located between the pods. Each hatch swung open on a hinge at the bottom, creating a short ramp from the floor of the corridor into the interior of the capsule. The pods were equipped with heat shields for atmospheric entry and landing if a suitable planet could be found to set down on. (Star Trek: First Contact) Ships commissioned USS Enterprise (NCC-1701-E) Appendices Appearances Star Trek films: Star Trek: First Contact Star Trek: Insurrection Star Trek Nemesis DS9: "Sacrifice of Angels" (LCARS graphic) "Tears of the Prophets" (LCARS graphic) "What You Leave Behind" (LCARS graphic) VOY: "Drone" (LCARS graphic) Background information Enterprise-E bridge.jpg The bridge of the Enterprise-E In production notes for Star Trek: First Contact, Michael Okuda suggested that the prototype for the Sovereign-class was the USS Sovereign and would have had a registry in a range around NX/NCC-75000. The Sovereign was also mentioned briefly in the Star Trek Encyclopedia, but the vessel itself has not been seen on screen to date. The official cutaway poster of the vessel that was released for First Contact designates the ship as an "Explorer Type 2". It appears that the Sovereign-class had at least two sickbay facilities, given sources in Star Trek: First Contact and Star Trek Nemesis that indicate sickbays on decks 8 and 16. The Sovereign-class was not the first class of vessel to have several sickbays; for example, Beverly Crusher was seen evacuating a sickbay in the engineering hull of the USS Enterprise-D in Star Trek Generations, as well as being treated in the engineering hull sickbay herself in "The Arsenal of Freedom". The saucer separation capability of the Sovereign-class was something that was neither seen nor mentioned on screen or in the scripts, but John Eaves went ahead and designed a detailed separation anyway. Design sketches were published in Star Trek: The Magazine Volume 3, Issue 11, page 49. The Sovereign class' name is never directly referred to in dialogue, but can be read on a Master systems display on the USS Enterprise-E bridge. Studio model See Sovereign-class model. Size Most sources agree that the Enterprise-E was 2,248 feet (685.2 meters) long. John Eaves described the rationale as follows: "When the "E" had a final approved design, we drew up a chart of all the Enterprises in profile. Herman [Zimmerman] and I set down a whole bunch of cutouts of the "E" in various sizes to see where this new ship should scale with the others. We found one size that looked appropriate and we put a scale to its length and that would be 2,248 feet. Rick [Sternbach] was waiting to do the blueprints and add his creativity to the design, so we gave him a drawing with this one measurement. From there he sized the whole ship ..." [2] The length of 2,248 feet can also be seen in John Eaves' size charts for Star Trek: Insurrection. [3] The Star Trek Nemesis size chart puts it at 2,250 feet, but since all the other figures in the chart are expressed to the nearest ten feet, we don't know whether this was a size revision or mere rounding for the purposes of this chart. [4] Refit According to John Eaves, the Enterprise-E was to have been retrofit at the end of Star Trek Nemesis but due to budgetary reasons and script changes the Enterprise was only seen being repaired in dry dock. "For the end of the film the badly destroyed and damaged E is being rebuilt in space-dock. This is where the opportunity was given to really fix all the lines and flow to match the roots of where the original drawing had left off. Not too often does one gets the chance to rework a beloved piece of art, and I was so happy to get the chance regardless of how minor the changes were." "The drawings were done and to be seen as the E leaves the space-dock at the end of Nemesis, with what we were hoping to get approval on being the new Aztec patterned paint job, that was so prominent with all the preceding variations of the Enterprise. As production went on, it was becoming clear that Nemesis was going to be the last of the TNG movies and thus, the E would fly no more. Very sad thoughts, and I was so hoping to at least to get to see that final version fly off into space... Budget and script changes kept the E in the bay under repair so all that exists of the big finish only exists on paper as a bunch of plans." [5] Apocrypha Sovereign-class starships have been mentioned often in novels and games. A role playing game supplement from Decipher mentions the Sovereign, Yorktown, and Independence. The class's prototype, the USS Sovereign (β), has appeared or been mentioned in several non-canon sources, such as the novels Spectre, Dark Victory, and The Genesis Wave, Book One, as well as the Pocket Books' reference works release Starship Spotter. The Sovereign was also the ship the player commanded in the later portions of the game Star Trek: Bridge Commander. USS Zhukov alongside USS Sovereign in Bridge Commander.jpg The USS Zhukov (foreground) alongside the USS Sovereign (background) in Star Trek: Bridge Commander Star Trek: Bridge Commander and Star Trek: Legacy list a likely and widely-accepted registry number for the Sovereign as NX-73811 (later NCC-73811). Other games mentioning the Sovereign are the role-playing game supplements The Price of Freedom from Last Unicorn Games and Starships from Decipher. In Star Trek: Legacy there were several Sovereign-class starships seen in the campaign, including the Enterprise, Sovereign, Davis, and Legacy. In the video game Star Trek: Invasion, two Sovereign-class vessels appeared: the USS Enterprise-E, and the USS Sentinel-B. The Enterprise-E is also the main base of operations in the game Star Trek: Elite Force II. The Sovereign-class is also the most powerful class available to the player in the game Star Trek: Armada, with the variant timeship USS Premonition also including a temporal weapon which allowed the player to pause time in local areas. This ship has never been mentioned anywhere else and due to the events of the game may never have existed (due to changes in the timeline by the player's actions.) In Star Trek: Armada II, one Sovereign-class starship is the Saratoga. In both games, the Sovereign-class has a special weapon called the "Corbomite Reflector" which deflects enemy torpedoes, sometimes right back at the ship that fired them. In Star Trek Online, the Sovereign-class starship is an "Assault Cruiser", available to those with the rank of Rear Admiral. The Vice Admiral variant comes with metreon gas canisters and a special quantum torpedo launcher. Between the free-to-obtain version, the Rear Admiral variant, the Vice Admiral variant, and the Fleet variant, there are six classes: Sovereign, Regent, Majestic, Noble, Archon, and Imperial. The mirror universe version of these classes are referred to as "Star Cruiser". External links Sovereign class at Memory Beta, the wiki for licensed Star Trek works Sovereign Changes at the Daystrom Institute Technical Library Sovereign-class variations at Ex Astris Scientia Designing a Sovereign Enterprise at Forgotten Trek Designing the Enterprise-E at the Federation Starship Datalink ARTICLE INFORMATION Top Contributors Archduk3 Sulfur Gvsualan Categories Other Languages EXPLORE GAMES MOVIES TV WIKIS FOLLOW US OVERVIEW About Careers Press Contact Terms of Use Privacy Policy Global Sitemap Local Sitemap COMMUNITY Community Central Support Fan Contributor Program WAM Score Help THE FANDOM APP Take your favorite fandoms with you and never miss a beat ADVERTISE Media Kit Contact Memory Alpha is a FANDOM TV Community. VIEW FULL SITE 697
Gaming / Re: Pokémon Sword & Shield for Nintendo Switch revealed« on: May 27, 2019, 09:05:51 AM »dude i need more info on gen 8, like fucking NOW Nintendo direct on June 5th 9 A.M E.T. 698
The Flood / Re: Hi there guys! Just want to share X thing I found cool, and here's why!« on: May 26, 2019, 08:36:15 PM »
The USS Enterprise (NCC-1701) was a 23rd century Federation Constitution-class starship operated by Starfleet. In the course of her career, the Enterprise became the most celebrated starship of her time.
In her forty years of service and discovery, through upgrades and at least two refits, she took part in numerous first contacts, military engagements, and time-travels. She achieved her most lasting fame from a five-year mission (2265-2270) under the command of Captain James T. Kirk. (Star Trek: The Original Series; Star Trek: The Motion Picture; VOY: "Q2") The Enterprise was destroyed over the Genesis Planet in 2285, when Kirk activated the ship's auto-destruct sequence to prevent the Enterprise from falling into the hands of the Klingons. (Star Trek III: The Search for Spock) Contents[show] LineageEdit See Enterprise history Service historyEdit Construction Edit In the early to mid-23rd century, at least twelve heavy cruiser-type starships, the Constitution-class, were commissioned by the Federation Starfleet. (TOS: "Tomorrow is Yesterday") Constructed at the San Francisco Fleet Yards in San Francisco, California, the Federation vessel registered NCC-1701 was christened the Enterprise in a long line of ships of the same name. (DIS: "Brother"; TAS: "The Counter-Clock Incident") Captain Robert April oversaw construction of the ship's components as well as its initial trial runs. His wife, Sarah April, designed several tools for the ship's sickbay. (TAS: "The Counter-Clock Incident") Larry Marvick was stated to be one of the designers of the Enterprise itself (TOS: "Is There in Truth No Beauty?"), while Doctor Richard Daystrom designed its computer systems. (TOS: "The Ultimate Computer") According to The Making of Star Trek, the Enterprise was built on Earth but assembled in space. Robert April's command Edit Enterprise's file Early specifications, including launch date, and duration of April's command The Enterprise was launched in 2245, under the command of Captain Robert April. (DIS: "Brother") Sarah April served as the ship's first chief medical officer, with Christopher Pike serving as Captain April's first officer. (TAS: "The Counter-Clock Incident"; DIS: "Brother") Prior to the Enterprise's launch date of 2245 eventually being made canon in the DIS episode "Brother", multiple production sources, including an unseen display screen intended for use in "In a Mirror, Darkly, Part II", the Star Trek Encyclopedia, and The Making of Star Trek, gave the same launch date. According to a computer display that was created by production staff of Star Trek: Enterprise but never used on screen, Jonathan Archer was present at the Enterprise's launch and died the next day. This information remains non-canon, because it was never photographed on film. In TAS: "The Counter-Clock Incident", it is stated that Sarah April's service on the Enterprise was the first time a medical officer served on a starship equipped with warp drive. However, it is established in Star Trek: Enterprise that warp-capable starships had medical personnel prior to the time of her service. According to the Star Trek: Federation - The First 150 Years, The Enterprise was launched on April 11, 2245. In the Star Trek: Discovery novel Drastic Measures, The Enterprise aided the Tarsus IV colony in the aftermath of Kodos the Executioner's infamous massacre in 2246. Christopher Pike's command Edit USS Enterprise, The Cage (remastered) The Enterprise in 2254 As captain, Christopher Pike commanded the Enterprise from 2250 to 2265. (DIS: "Brother"; TOS: "The Menagerie, Part I") His missions included voyages to the Rigel, Vega, and Talos systems. (TOS: "The Cage"; TOS: "The Menagerie, Part I") Pike's half-Vulcan science officer, Spock, who served under him for over eleven years, ultimately became the starship's longest-serving officer. (TOS: "The Menagerie, Part I") According to the novel Desperate Hours, the Enterprise fell under Admiral Brett Anderson's jurisdiction, along with the USS Shenzhou. In late 2256, Michael Burnham encouraged Cadet Sylvia Tilly to improve her physical conditioning so that she would stand out amongst her peers, and be assigned to the Enterprise or one of its sister ships. (DIS: "Lethe") At that time, the Enterprise was on a five-year mission under Pike. With the Federation-Klingon War underway, Starfleet elected not to recall the starship and leave her as an instrument of last resort, so ordered Pike and his crew to remain out of the fighting. (DIS: "Brother") USS Discovery rendezvousing with USS Enterprise The Enterprise rendezvouses with the Discovery, 2257. The Red Bursts Edit Following the conclusion of the war in 2257, the Enterprise was dispatched by Starfleet to investigate one of a series of unidentified signals detected throughout the galaxy. (DIS: "Brother") En route, the ship suffered multiple catastrophic systems failures, leading Pike to issue a priority 1 distress call. The call was received by the USS Discovery, en route to Vulcan. (DIS: "Will You Take My Hand?", "Brother") Pike and two senior officers transferred to Discovery to continue their mission, while a team was dispatched to tow the Enterprise back to Spacedock for a diagnostic, where the damage was assessed as severe, with no estimate for repair. (DIS: "Brother") Federation tug 23rd century The Enterprise being towed to Spacedock A week later, Pike's first officer, "Number One" had reported to Pike that the holographic comm system was the source of the failures, which had compromised primary systems. Pike ordered Number One to tell Chief Engineer Louvier to strip the system from the ship in favor of viewscreen communication. (DIS: "An Obol for Charon") Battling control Edit Discovery deploys evacuation corridors Enterprise taking on Discovery's crew Following the Discovery's acquisition of data from the Sphere that would ultimately lead to the evolution of the Section 31 artificial intelligence Control which would threaten all sentient life in the Milky Way Galaxy, Pike was left with no other option but to set the Discovery's auto-destruct system and call the Enterprise for immediate evacuation of the ship's crew. (DIS: "Through the Valley of Shadows") On Stardate 1051.8, the Enterprise finally rendezvoused with the Discovery and began taking on the ship's crew. When all personnel were fully evacuated, Captain Pike ordered Discovery's destruction. However the Sphere intelligence utilized Discovery's defensive systems to block the Enterprise's torpedo volley. Unable to eliminate Discovery, the crew determined that sending the Discovery into the future was the only method to secure the Sphere data from Control. Enterprise and Discovery Battle Section 31 The Enterprise and Discovery engage Section 31 vessels. With the appearance of a fifth red burst, both ships traveled to the planet Xahea, which was ultimately the position Cornwell and Pike decided to fight Leland/Control's armada. (DIS: "Such Sweet Sorrow") After the decision was made to destroy Discovery to prevent its capture by Control, the ship deployed evacuation corridors to transfer its crew to Enterprise. (DIS: "Such Sweet Sorrow") USS Enterprise in Spacedock The Enterprise undergoes repairs in 2258. Following the decisive battle with Control, and the loss of a significant portion of the saucer section, the Enterprise under went extensive repairs in orbit of Earth. (DIS: "Such Sweet Sorrow, Part 2") New Voyages Edit Following the repairs to the Enterprise, The Enterprise resumed her mission of exploration once again under the command of Christopher Pike. Their first stop was to a new moon that was discovered at Edrin II. (DIS: "Such Sweet Sorrow, Part 2") James T. Kirk's command Edit USS Enterprise orbiting Omicron Ceti III, remastered The Enterprise in orbit, 2267 In 2265, the Enterprise was assigned to another five-year mission of deep-space exploration, and command passed to James T. Kirk. The ship's primary goal during this mission was to seek out and contact alien life. Captain Kirk's standing orders also included the investigation of all quasars and quasar-like phenomena. Beyond its primary mission, the Enterprise defended Federation territories from aggression, aided member worlds in crisis, and provided scientific expeditions and colonies in her patrol area with annual examinations and support. (TOS: "Balance of Terror", "The Man Trap", "The Cloud Minders", "Journey to Babel", "The Galileo Seven", "The Deadly Years") Despite 2270 being given as the year Kirk's first five-year mission in command of the Enterprise came to an end (in the Star Trek: Voyager episode "Q2"), many production resources – including the booklet for the TOS Season 1 DVD set – continue to use the Star Trek Chronology's date of 2264 as the starting point of the mission. It is possible, however, that the mission ran from 2264 through 2269 and that the Enterprise did not return to Earth until 2270. According to a line from the script of Star Trek but removed from the final draft, the crew of the Enterprise came together in a time of "ultimate crisis", much like their alternate reality counterparts did. [1] According to a line of dialogue from the final draft script of "Mudd's Women", the Enterprise was located two years, five months, twenty-two days, and seven hours from a starbase at impulse speed in that episode. Discoveries Edit From 2265 to 2270, the Enterprise visited over seventy different worlds and encountered representatives of over sixty different species. More than twenty of those were first contacts with beings previously unknown to the Federation, including stellar neighbors like the First Federation and Gorn, voyagers from the Kelvan Empire in distant Andromeda, and powerful non-corporeal entities like the Thasians, Trelane, and the Organians. Two discovered species were the first known examples of silicon-based lifeforms: the Horta and the Excalbians. (TOS: "The Corbomite Maneuver", "Arena", "By Any Other Name", "The Devil in the Dark", "The Savage Curtain") USS Enterprise leaving galactic barrier, remastered In the barrier void in 2265 The Enterprise was the first Federation vessel to survive an encounter with the galactic barrier. The ship's warp drive and other systems, however, were critically damaged and casualties totaled twelve crewmembers and officers. By stardate 4657.5, the Enterprise was traveling through space in a region hundreds of light years further than any Earth starship had explored. (TOS: "Where No Man Has Gone Before", "Return to Tomorrow") The reality of time travel, externally influenced, had been known for over a century, but following two accidental temporal displacements, the Enterprise became the Federation's first deliberately-controlled timeship. Observing the death-throes of Psi 2000, the crew suffered from polywater intoxication and the Enterprise nearly lost orbit after an engine shutdown. A previously untested "cold start", via controlled matter-antimatter implosion, saved the ship, but the high-speed escape from the planet's gravity well caused the ship to travel three days into the past. (TOS: "The Naked Time") USS Enterprise in orbit of Earth Orbiting 1960s Earth In 2267, while escaping the gravitational pull of a black star, the Enterprise was hurled through space and time to Earth of 1969. The crew developed and executed a method to return to their own time, by warping around the sun's gravity well in a slingshot maneuver. A year later, the Enterprise was ordered to repeat the recently proven slingshot effect, and returned to Earth's past on a mission of historical observation. (TOS: "Tomorrow is Yesterday", "Assignment: Earth") Originally, "The Naked Time" and "Tomorrow is Yesterday" were planned to be back-to-back stories, with the events in "Tomorrow is Yesterday" happening as a result of the "cold start" of the warp drive in "The Naked Time". A change in production plans resulted in the two stories being de-linked and slightly reworked to stand alone. USS Enterprise approaches space amoeba, remastered The space amoeba in 2268 Some missions of discovery confronted Enterprise with entities and mechanisms that threatened great swaths of Federation and neighboring space. An ancient "planet killer", fueled by the consumption of planets it destroyed with its antiproton weapon, approached Federation population centers in 2267. It required the combined efforts of the Enterprise and her sister ship, USS Constellation, to destroy it. (TOS: "The Doomsday Machine") One year later, in 2268, a single-cell organism of colossal scale emitted negative energy, toxic to humanoid life, killing the entire Vulcan crew of the USS Intrepid. The Enterprise penetrated the cell interior and destroyed the organism before its imminent cell division threatened to overwhelm the rest of the galaxy. (TOS: "The Immunity Syndrome") Battles Edit USS Enterprise firing phaser proximity blast The Enterprise fires a proximity blast The nature of its mission of exploration meant the Enterprise was frequently the only Federation military asset in a little-known, otherwise undefended frontier. When called into harm's way, the ship regularly did so with little chance of immediate support against previously unknown enemies and threats. Happily, the Enterprise's earliest engagement of its five-year mission, against a deceptively powerful starship called the Fesarius, ended with an amicable first contact with the First Federation in 2266. Following the destruction of a colony on Cestus III, a surprise attack – from a previously unknown species – led the Enterprise to battle and pursue an evenly matched Gorn starship in 2267. (TOS: "The Corbomite Maneuver", "Arena") The Enterprise played the fox for four of her sister ships in a war games problem on stardate 4729.4, as part of the M-5 drills. Equipped with the new M-5 multitronic unit computer and stripped of most of its crew, the Enterprise became a killing machine – crippling the USS Excalibur and killing its entire crew – before Kirk could re-assert control. (TOS: "The Ultimate Computer") Klingon engagements USS Enterprise-D7 face off The Battle of Organia in 2267 Warships of the Imperial Klingon Fleet were frequent opponents of the Enterprise. Commander Kor held the Enterprise and Kirk in high professional regard, and relished the prospect of battle. Lower ranks chose to mock the starship; on one such occasion, Korax compared the vessel to a "garbage scow" before he corrected himself, adding, "It should be hauled away as garbage." (TOS: "Errand of Mercy", "The Trouble with Tribbles") While Starfleet rallied its forces at the outbreak of a Federation-Klingon War in 2267, the Enterprise was sent forward to secure a border region anchored by the planet Organia. The vessel destroyed a Klingon attack ship and prepared to engage an approaching Klingon fleet, before the Organian Peace Treaty precluded a full-scale war. (TOS: "Errand of Mercy") The Enterprise sporadically engaged Klingons throughout its voyage. A warship failed in an attempt to blockade the Enterprise from Capella IV in 2267. Sabotaged during a diplomatic mission to the Tellun system in 2268, the ship successfully fought off the assault of a harassing D7. The same year, the Enterprise was forced to destroy a battle cruiser that Kang had commanded but had recently abandoned, and the rescued Klingons (influenced by the Beta XII-A entity) subsequently made an unsuccessful attempt to wrest control of the Enterprise from Kirk. (TOS: "Friday's Child", "Elaan of Troyius", "Day of the Dove") Romulan engagements Romulan bird-of-prey, CG TOS-aft Ventral view of a Romulan Bird-of-Prey during the Neutral Zone Incursion of 2266 The Romulan Star Empire reemerged from a century of isolation to antagonize the Federation with the Neutral Zone Incursion of 2266. The Enterprise responded and was victorious against a new Romulan Bird-of-Prey equipped with a cloaking device and plasma torpedo system. (TOS: "Balance of Terror") In later encounters, the Romulan fleet used strength of numbers in their efforts to overwhelm the Enterprise. When Commodore Stocker took temporary command and violated the Neutral Zone in 2267, up to ten Bird-of-Prey swarmed and pummeled the starship until Kirk's "corbomite" bluff inspired their withdrawal. (TOS: "The Deadly Years") In 2268, the Enterprise again violated the Neutral Zone – for the purpose of espionage – and was quickly surrounded by three Romulan D7 class battle cruisers. She escaped by becoming the first Federation vessel to install and successfully utilize a (stolen) Romulan cloaking device. (TOS: "The Enterprise Incident") Near Tau Ceti in the following year, Kirk employed the Cochrane deceleration maneuver, allowing the Enterprise to defeat a Romulan vessel. (TOS: "Whom Gods Destroy") In the final year of Kirk's original mission, the ship was ambushed by a trio of Romulan battle cruisers while on a routine survey. The Enterprise managed to escape through an energy field that adversely affected the ship's main computer. The malfunctioning systems were corrected by another pass through the field, this time with the Romulan ships in pursuit. The attackers then became incapacitated by the same computer malfunctions, and the Enterprise was able to escape. (TAS: "The Practical Joker") Casualties Edit Service aboard the Enterprise proved to be hazardous duty. Between 2265 and 2269, individuals who were killed while assigned to the ship included at least fifty-eight officers and crew – thirteen-point-five percent of the standard complement of 430. Nine crew members were killed when the Enterprise encountered the galactic barrier in 2265. Gary Mitchell, Lee Kelso, and Elizabeth Dehner later died on Delta Vega. (TOS: "Where No Man Has Gone Before") Two of the seven crewmembers assigned to study Murasaki 312 on the shuttlecraft Galileo – Latimer and Gaetano – both met an unfortunate end by the hand of a large creature on the planet Taurus II. (TOS: "The Galileo Seven") In 2267, Enterprise security officers Hendorff, Kaplan, Mallory, and Marple were killed on the planet Gamma Trianguli VI. (TOS: "The Apple") Further incidents with multiple fatalities included four security guards killed by Nomad in 2267 as well as five security guards killed by the dikironium cloud creature on Argus X in 2268. An outbreak of Rigelian fever, in 2269, killed three crewmen and imperiled the rest until a source of ryetalyn could be obtained. (TOS: "The Changeling", "Obsession", "Requiem for Methuselah") As well, two Enterprise security officers were beamed out into open space while the ship was under the control of Gorgan. (TOS: "And the Children Shall Lead") Lieutenant Galloway was vaporized by Captain Tracey on Omega IV, (TOS: "The Omega Glory") but later was somehow resurrected. (TOS: "Turnabout Intruder") Yeoman Thompson was reduced to a dry cuboctahedron solid. She was killed when the Kelvan Rojan crushed the object in his hand. (TOS: "By Any Other Name") In the mid-2270s, Commander Sonak and an Enterprise officer were killed in a transporter accident while beaming to the ship. (Star Trek: The Motion Picture) See also: Redshirt Later Years Edit RefitsEdit In the late 2260s to early 2270s, the Constitution-class starships underwent a major refit program. The actual refitting took eighteen months of work and essentially a new vessel was built onto the bones of the old, replacing virtually every major system, ensuring their continued service for the next several years, with the USS Enterprise continuing to serve in its prominent role. In the early 2270's, the Enterprise was critical in defending the Federation from several external threats, including the V'Ger probe, and Khan Noonien Singh. (Star Trek: The Motion Picture, Star Trek II: The Wrath of Khan) USS Enterprise (NCC-1701) in spacedock The refitted Enterprise in spacedock, 2270s System upgrades with new technologies after long deployments were far from unusual in the ship's history. However, the Enterprise's overhaul of the early 2270s became a nearly keel-up redesign and reconstruction project. The very heart of the ship was replaced with a radically different vertical warp core assembly, linked to new, and heavier, warp engine nacelles atop swept-back pylons and integrated with the impulse engines. The new drive system allowed for an expanded cargo hold in the secondary hull, linked to the shuttlebay. Weapons system upgrades included nine dual-phaser banks with power channeled directly from the warp engines. A double photon torpedo/probe launcher was installed atop the secondary hull. Multiple egress points now included a port-side spacedock hatch, dual ventral space walk bays, four dorsal service hatches, and a standardized docking ring port aft of the bridge on the primary hull, four more docking ring ports, paired on the port and starboard sides of the launcher and secondary hulls respectively, and service hatch airlocks on the port and starboard sides of the hangar bay's main clam-shell doors. A new bridge module reflected the modern computer systems, operating interfaces, and ergonomics that ran throughout the ship. Following Kirk's promotion to rear admiral and posting as Chief of Starfleet Operations, his successor, Captain Will Decker (whom Kirk himself picked to succeed him), oversaw the refit, assisted by chief engineer Commander Montgomery Scott. V'gerEdit After 18 months in spacedock for refit, the Enterprise was pressed into service, weeks ahead of schedule, in response to the V'ger crisis, once again under Kirk's command. USS Enterprise approaches V'ger's cloud Making contact with V'ger Decker was temporarily demoted to commander and posted as an executive officer because of his familiarity with the new design. Incomplete systems had to be serviced during the vessel's shakedown cruise en route to V'ger, including the first test of the new warp engines. Shortly after launch, a matter/antimatter intermix malfunction ruptured the warp field and led to the Enterprise entering into an unstable wormhole. Commander Decker belayed an order from Admiral Kirk to destroy an asteroid in their path, which had been dragged into the ruptured warp field along with them, with phasers. The refitted phasers now channeled power directly from the main engines at a point beyond the dilithium/magnatomic-initiator stage. Because of this refitted function, the intermix malfunction, and the antimatter imbalance within the warp nacelles that had resulted caused automatic cutoff of the phasers, a design change of which Kirk had not been aware. Decker ordered the use of photon torpedoes instead; as a backup, they had been designed to draw power from a separate system in case of a major phaser loss. The timely arrival of Commander Spock brought correction to the intermix problem. (Star Trek: The Motion Picture) Once the V'ger threat was averted, Captain Decker was listed as "missing in action" and the Enterprise remained under Admiral Kirk's command for an interim period. At some point, Kirk passed command on to the newly-promoted Captain Spock. The new designs and components tested and proven aboard the Enterprise influenced a generation of starship design, from the Miranda-class to the Constellation-class, as well as other retro-fitted Constitutions. (Star Trek II: The Wrath of Khan) Khan's ReturnEdit In 2285, the Enterprise was in a low-tempo training cycle, based in the Sol system. Admiral Kirk boarded his old command to observe a cadet training cruise. Meanwhile, Khan Noonien Singh had escaped from his exile on Ceti Alpha V and hijacked the USS Reliant, leading to his theft of the Genesis Device from the Regula I space station. USS Enterprise exiting the Earth Spacedock The Enterprise, heavily damaged The Enterprise was tasked to investigate, and Spock deferred his command to Admiral Kirk. Subsequent engagements with Reliant left the ship badly damaged with cadet and crew deaths, including Captain Spock. (Star Trek II: The Wrath of Khan) Return to Genesis & DestructionEdit USS Enterprise self destructs "My God, Bones... what have I done?" - Admiral James T. Kirk Upon the Enterprise returning to Earth, Starfleet Commander, Starfleet Fleet Admiral Morrow announced that the starship, at that point forty years old, would be decommissioned. When Morrow denied Kirk requesting permission to return to the Mutara sector, Kirk conspired with his senior officers and stole the Enterprise from Earth Spacedock, in order to recover Spock's body from the Genesis Planet – to bring it and Spock's katra, the latter possessed by Leonard McCoy, to Vulcan. As part of the plan, Kirk had Scott rig up an automation system to run the Enterprise so easily that "a chimpanzee and two trainees" could have handled the craft. Enterprise streaking in Genesis sky The Enterprise burning in Genesis' atmosphere At the Enterprise's destination, the ship was attacked by a Klingon Bird-of-Prey operated by Klingon Commander Kruge, an assault that left the Enterprise disabled; Scotty's automation system was not designed for combat and overloaded when the ship was attacked. After setting the auto-destruct sequence, Kirk and his crew abandoned the ship for the surface of the Genesis Planet. Demolition charges in place in the bridge and elsewhere throughout the ship's saucer section exploded, killing a Klingon boarding party. The secondary hull (with what was left of the saucer) fell from orbit and blazingly streaked across the planet's atmosphere. (Star Trek III: The Search for Spock) Film writer Harve Bennett justified the destruction of the Enterprise via an analogy to the USS Niagara. According to Bennett, "Oliver Hazard Perry of the U.S. Navy scuttled the Niagra [sic] at the battle of Lake Erie and won the battle as a result and took command." He added, "Perry happens to be one of James T. Kirk's great heroes. So, the scuttling of the ship to achieve the greater good is a tactic." (Great Birds of the Galaxy: Gene Roddenberry and the Creators of Trek) A supporter of the decision to blow up the Enterprise was Nicholas Meyer, who commended Bennett for the idea in a letter between them (dated 24 September 1982). There is a difference in the appearance of the Enterprise between Star Trek II: The Wrath of Khan and Star Trek III: The Search for Spock; in Star Trek III, the ship's external appearance appeared to have deteriorated around some areas damaged by Khan's attacks (and repaired in others), while other areas of the ship that had not been damaged by Khan's attack had battle damage, including the starboard secondary hull, both nacelles, and the top of the saucer. This extra damage was explained in non-canon Star Trek literature as having occurred in spars with Klingon warships between the second and third movies. The aggressive move to attack the Enterprise was explained by the secrecy of the Genesis Planet and the overall uneasiness it created. This could also explain the Klingon aggressiveness displayed throughout the third movie. [2] Command crew Edit USS Enterprise bridge, 2258 The crew of the Enterprise under the command of Christopher Pike in 2258. There will be no tribble at all The crew of the USS Enterprise enjoy a jovial moment with Captain Kirk Commanding officer Robert April (2245–2250; briefly in 2270) Christopher Pike (2250–early 2260s) Katrina Cornwell (briefly in 2257) James T. Kirk (2265–2270; early 2270s, 2285) Stocker (2267) Matt Decker (2267) Will Decker (2270s) Spock (2285) First officer Christopher Pike (2245–2250) "Number One" (2250s) Spock (2260s–2270; 2285) Will Decker (2270s) Saavik (as a trainee) (2285) Second officer Spock (2270s) Montgomery Scott (2266–2270s) Chief engineer Louvier (2257) Montgomery Scott (2265–2270s, 2285) Chief medical officer Sarah April (2245–2250) Phil Boyce (2254) Mark Piper (2265) Leonard McCoy (2266–2270, 2270s, 2285) Christine Chapel (2270s) Helmsman "Number One" (2250s) Mann (2257) (acting) Gary Mitchell (2265) Hikaru Sulu (2266–2270s, 2285) Leslie (2266-2267) Hansen (2267) Hadley (2267–2268) DePaul (2267) Spinelli (2267) Kyle (2268) Rahda (2268) Walking Bear (2270) Communications officer/Operations officer Garison (2254) Nicola (2257–) Alden (2265) Uhura (2266–2270s, 2285) John Farrell (2266) Palmer (2267–2269) Angela Martine (2267) M'Ress (2269–2270) Navigator José Tyler (2254) Amin (2257–) Lee Kelso (2265) Dave Bailey (2266) John Farrell (2266) Kevin Riley (2266) Stiles (2266) Hadley (2267–2269) DeSalle (2267) DePaul (2267) Osborne (2267) Leslie (2267) Painter (2267) Pavel Chekov (2267–2269) Jana Haines (2268) Arex (2269–2270) Ilia (2270s) DiFalco (2270s) Saavik (2285) Security chief Giotto (2267) Pavel Chekov (2270s, 2285) Tactical officer Mann (2257–) Hikaru Sulu (2266–2270) Pavel Chekov (2267–2270) Science officer Evan Connolly (2250s–2257) Kroad (2257) Hikaru Sulu (2265) Spock (2254–2257; 2258–2270, 2270s–2280s) Will Decker (2270s) Pavel Chekov (2285) Records officer Benjamin Finney (2267) A&A officer Carolyn Palamas (2267) See also: List of USS Enterprise (NCC-1701) personnel The Starships Enterprise United Earth: XCV 330 • NX-01 Federation: NCC-1701 • NCC-1701-A • NCC-1701-B • NCC-1701-C • NCC-1701-D • NCC-1701-E • NCC-1701-J Terran Empire (mirror universe): NX-01 • NCC-1701 Federation (alternate reality): NCC-1701 • NCC-1701-A Constitution-class starships USS Ahwahnee • USS Constellation • USS Defiant • USS Eagle • USS Emden • USS Endeavour • USS Enterprise • USS Enterprise-A • USS Excalibur • USS Exeter • USS Hood • USS Intrepid • USS Korolev • USS Lexington • USS Potemkin • NCC-1700 • NCC-1707 • Unnamed Mirror universe: USS Defiant • ISS Enterprise Alternate reality: USS Enterprise • USS Enterprise-A • Unnamed Appendices Edit Appearances Edit This list contains 15 items (show all • hide all) Star Trek: The Original Series (every episode) Star Trek: The Animated Series (every episode, except "The Slaver Weapon") Star Trek films: (4) TNG: "Relics" (bridge shown on holodeck) DS9: (2) ENT: "These Are the Voyages..." (closing montage) DIS: (5) References Edit This list contains 10 items (show all • hide all) TAS: "The Slaver Weapon" TNG: "The Naked Now" VOY: "Q2" DIS: (7) Background information Edit MarsTOSremastered-Intro The CG Enterprise from the "remastered" opening credits Sickbay painting The Enterprise on a painting aboard the Enterprise-D The Enterprise and its interiors were designed primarily by Matt Jefferies. A three-foot demonstration model was completed in November 1964 by the Howard Anderson Company to show to Gene Roddenberry. After getting his approval, an eleven-foot model was then constructed by Richard C. Datin, Jr., Mel Keys, and Vern Sion at Volmer Jensen's model shop, and was finished in December 1964. The eleven-foot model was modified for TOS: "Where No Man Has Gone Before" and again for the regular series effect shots. Re-used footage of all three stages of the eleven-foot model's appearance are seen mixed together in TOS. In the final draft script of TOS: "The Naked Time", the Enterprise was somewhat poetically described thus; "Sleek... efficient... the look of man in space... tooled... equipped...." For Star Trek: The Animated Series, the color of the Enterprise was limited. D.C. Fontana commented, "For the purposes of animation you can't do the light white, silver kinds of colors. So they made the Enterprise gray and it came off all right." (Star Trek: The Magazine Volume 1, Issue 16, p. 68) Some distinctive effects shots of the Enterprise from TOS were recreated in animation for Star Trek: The Animated Series. Depicting the ship performing any new, impressive maneuvers would have been too costly for TAS and would have taken the animators too long to show, despite frequent TAS Director Hal Sutherland later implying that a desire to portray the ship doing "barrel rolls and that kind of thing" was quite common. (Star Trek: The Magazine Volume 1, Issue 16, pp. 63 & 64) The refit of the Enterprise depicted in the films Star Trek: The Motion Picture, Star Trek II: The Wrath of Khan, and Star Trek III: The Search for Spock was designed by Andrew Probert, based on designs for the vessel made by Matt Jefferies for undeveloped television series Star Trek: Phase II. The design for the movie refit was the basis of a design patent issued by the US Patent and Trademark Office. The Enterprise was to have appeared in Star Trek: The First Adventure that revealed the design of the ship in TOS was actually a refit; the original design resembled Enterprise NX-01, though that vessel was created years later. The Enterprise was recreated as a new physical model for the DS9 Season 5 episode "Trials and Tribble-ations". The ship's interior was represented with sets built on Paramount Stage 11. (Information from Larry Nemecek) The CG model of Constitution-class USS Defiant, created for "In a Mirror, Darkly", was relabeled as the Enterprise for the final scene of "These Are the Voyages...", the last episode of Star Trek: Enterprise. A new CG model, built from caliper measurements of the original eleven-foot physical model, was created for use in the remastered and recreated version of Star Trek: The Original Series (for more detailed treatises on the studio models used, see the appropriate articles: Constitution-class model (original) and Constitution-class model (refit)). Visual effects artist Gabriel Koerner created a re-imagined version of the pre-refit Enterprise. The design is more contemporary, while keeping the design of the original ship. A video showing the ship from various angles can be seen on YouTube. The model was also featured as the August image for the 2007 Ships of the Line calendar, as well as in the Ships of the Line coffee-table book, placed between TOS and TMP images, which included text from Michael Okuda suggesting it as one of the ideas on how to refit the ship. The Enterprise was pictured on three paintings during the Star Trek franchise: on a painting in the recreation deck of the refitted vessel in Star Trek: The Motion Picture, on a painting in the waiting area of the sickbay aboard the USS Enterprise-D in the Star Trek: The Next Generation fifth season episode "Ethics", and on a painting on the wall of Kirk's kitchen in the Nexus in Star Trek Generations. Upon preparing to view the bridge of the Enterprise in the first draft script of TNG: "Relics", Montgomery Scott specified, "Show her the way she was before Stardate 5928," referencing the stardate on which TOS series finale "Turnabout Intruder" takes place. Consequently, this line of dialogue would have established that the holographic simulation of the Enterprise's bridge in "Relics" was definitely contemporaneous with the exact setting of TOS. Scott did not specify that in the final draft of the script, however. [3] The line is also not spoken on screen. The Enterprise was to have been referenced in the first draft script of VOY: "Flashback", in connection with its near-destruction at Eminiar VII. However, all mention of the vessel was eliminated from the episode by the time the final draft of the script was written. A new CGI model was created for the appearance of the USS Enterprise in the Season 1 finale of Star Trek: Discovery, "Will You Take My Hand?". This model updates the appearance of the USS Enterprise to better match the style of Starfleet ships seen in the show, most noticeably changing the warp nacelles to have visible, glowing blue cutouts on the inner surface. The impulse engine is also different and the nacelle pylons are swept back with openings in their centers similar to the refit configuration. The new model also has a longer "runway" before the shuttlebay doors. 699
The Flood / Re: This is the only Carmen that matters« on: May 26, 2019, 08:13:49 PM »spy kids is one of those things i'm very embarrassed to have enjoyed as a kid, like anti-nostalgia This only sane response brought to you by the same dude who thinks Attack of the Clones was good. What is the world coming to? YouTube I'll say though that the first one was pretty alright, or at least the sought of it does not trigger brief desires to commit suicide for liking it. 700
The Flood / Re: This is the only Carmen that matters« on: May 26, 2019, 01:07:13 AM »Speaking of Halo, when the hell are you gonna play with us againThat F-Zero X inspired race in Spy Kids 3 >>> Halo 4Inferior childhood confirmed Ill probably play as soon as tomorrow. I was tied up grinding other games and binging Mobile Suit Gundam. 701
The Flood / Re: This is the only Carmen that matters« on: May 26, 2019, 12:24:24 AM »That F-Zero X inspired race in Spy Kids 3 >>> Halo 4Inferior childhood confirmed That race made the Boltshot and DMR look like the absolute of apex of game ballance in comparison. 702
The Flood / Re: This is the only Carmen that matters« on: May 26, 2019, 12:10:15 AM »Inferior childhood confirmed Arte we now actually acting like Spykids 3D was good (asside from putting Khan and Scarface in the same movie)? No wonder you hate Halo 4 703
The Flood / Re: This is the only Carmen that matters« on: May 26, 2019, 12:06:35 AM »Hold it right there you sick fuck lolicon 704
The Flood / Re: oh damn« on: May 25, 2019, 11:49:25 PM »
USS Enterprise (NCC-1701-E)
English Edit Share USS Enterprise Class: Sovereign-class Registry: NCC-1701-E Owner: United Federation of Planets Operator: Starfleet Status: Active (2379) "...I tend to think of this ship as home." – Jean-Luc Picard, 2063 (Star Trek: First Contact) The USS Enterprise (NCC-1701-E) was a 24th century Federation Sovereign-class starship operated by Starfleet. This ship was the sixth Federation starship to bear the name Enterprise. Contents[show] History Edit Construction and launch Edit On stardate 49827.5, the Sovereign-class Enterprise-E, seen as the pinnacle of Starfleet ship design, was launched from San Francisco Fleet Yards, with Captain Jean-Luc Picard in command once more. Much of the crew of the Enterprise-D had been reassigned there, including almost the entire senior staff. The sole exception was Lieutenant Commander Worf, who had already transferred to the space station Deep Space 9. (Star Trek: First Contact; DS9: "The Way of the Warrior", "Trials and Tribble-ations") Asked about its construction, Ronald D. Moore replied that his "working assumption was that the E-E had her keel laid sometime during TNG's last season and was probably going to be given another name. When the E-D was destroyed, that Sovereign-class ship was nearing completion and was then christened Enterprise. This same sort of thing happened during WWII. After the carrier Yorktown was sunk at Midway, the US Navy decided to rename a carrier then under construction in honor of the fallen ship." (AOL chat, 1998) In the novel Headlong Flight, it is stated that the Enterprise-E was originally going to be named the USS Honorius before the Battle of Veridian III. The novel The Autobiography of Jean-Luc Picard stated that the vessel was originally going to be named the USS Sentinel. Service history Edit The Borg ThreatEdit After almost a year in space, the Enterprise was ordered to patrol the Romulan Neutral Zone during the second Borg incursion. Starfleet was officially concerned about possible Romulan military action since many of the available ships had been diverted to fight the Borg, but in reality, Starfleet was concerned about Picard's presence at the battle. USS Enterprise-E engages Borg at 001 The Enterprise at the Battle of Sector 001 Return to EarthEdit However, shortly after the Federation fleet engaged the Borg cube, Picard disobeyed orders and returned to Earth to assist the fleet. Once there, Picard became aware of a battle-induced weakness in the Borg ship due to his residual link to the Collective and ordered all the ships in the fleet to concentrate their fire on that section of the ship. As a result, the Borg vessel was destroyed and the Battle of Sector 001 was a victory for Starfleet. Defiant and Enterprise-E The Enterprise passing the USS Defiant Journey to 2063Edit Before the Borg cube was destroyed, it launched a second vessel towards Earth. This ship created a temporal vortex and traveled back to the year 2063 in order to stop Zefram Cochrane from launching his historic warp ship, the Phoenix. Their hope was to prevent first contact with the Vulcans and assimilate Earth before the Federation could be formed to resist them. The Enterprise, protected from the alterations in the timeline by a temporal wake within the vortex, chased the Borg into the past and destroyed their ship and sent an away team to help Cochrane repair the Phoenix. Borg assimilating Enterprise-E corridor Borg assimilating the decks of the Enterprise However, the ship's sensors and shields were damaged during the trip through the vortex and, unbeknownst to the crew, several Borg drones transported aboard the Enterprise before their ship exploded. They began to assimilate the ship, beginning with main engineering and sickbay on deck 16 and converting the corridors into a Borg configuration, complete with regeneration alcoves and assimilation chambers. On Picard's order, Lieutenant Commander Data locked out the main computer with a fractal encryption code to prevent the Borg from fully seizing control of the Enterprise. The Borg established their collective in engineering and cut primary power to all other decks, cutting the Enterprise off from the away team still down on the surface. The Borg were able to swiftly overrun the defense checkpoints set up by the Starfleet crew on decks 26 through 11, assimilating the crew as they progressed and seizing control of such sections as hydroponics, stellar cartography, deflector control and the shuttlebays. They also attempted to build an interplexing beacon on the particle emitter of the deflector dish to contact the Borg Collective of that time period. Sovereign class deflector dish, damaged The main deflector dish, with particle emitter disconnected A three-man team led by Captain Picard stopped the beacon from being completed by separating the dish from the ship by disengaging the magnetic locks and destroying it. The Borg changed tactics and continued to overrun the defense checkpoints, assimilating the ship up to deck 5 with the intent to fully assimilate the vessel. The Borg's ability to adapt to the handheld weapons of the Enterprise crew made stopping them impossible and Picard realized that the fight was a lost cause. After great consideration, he reluctantly ordered the evacuation of the ship via the escape pods and activated the ship's auto-destruct sequence to prevent the Borg from interfering with the Phoenix flight. Picard eventually confronted the Borg Queen in main engineering, only to find, to his horror, that the Borg had apparently coerced Data into collaborating with them. He aborted the auto-destruct sequence and entered the encryption codes into the main computer, effectively giving the Borg Queen command of the Enterprise. On the Queen's instructions, Data fired three quantum torpedoes at the Phoenix, ostensibly intending to destroy it. However, the torpedoes narrowly missed their target and Data revealed that he had in fact simply been deceiving the Borg. He ruptured one of the plasma coolant tanks, flooding engineering with plasma coolant and liquefying the Borg Queen and all the drones in engineering. With the death of the Borg Queen, the remaining Borg onboard were disabled, which allowed Data and Picard to recapture the vessel. The Enterprise crew was successful in helping Cochrane make his flight and instigate First Contact with Vulcans. Using the gravitational field of Luna allowed the Enterprise to remain undetected by the Vulcan ship and the Enterprise was able to recreate the vortex used by the Borg to return to 2373 where the Borg components were removed, the ship repaired and subsequently returned to service. (Star Trek: First Contact) The Briar Patch Edit Enterprise-E in Briar Patch The Enterprise in the Briar Patch With the Federation Diplomatic Corps attempting to negotiate an end to the Dominion War, the Enterprise was relegated to a diplomatic role, much to the dissatisfaction of Captain Picard. In 2375, the Enterprise was conducting a diplomatic mission with the Evora, a new Federation protectorate species and was scheduled to resolve a dispute in the Goren system when her crew became embroiled in a plot by the Son'a, assisted by Starfleet Admiral Matthew Dougherty, to forcibly remove the Ba'ku from their isolated homeworld in the Briar Patch. The Son'a PlotEdit The Son'a turned out to be vengeful former Ba'ku who had been exiled from the planet after a failed coup a century prior. They planned to harvest metaphasic radiation from the planet's ring system and needed Starfleet's cooperation to carry out the plan. Captain Picard felt the relocation of the Ba'ku was a severe violation of the Prime Directive and resigned his commission, leading a team of Enterprise crewmembers to the Ba'ku planet to prevent their capture and removal. Isolytic-burst The Enterprise being pursued by a subspace tear in the Briar Patch Commander William T. Riker was instructed to take the Enterprise and contact the Federation Council to alert them of Admiral Dougherty's treachery. However, the Enterprise was required to navigate an area of space known as the Briar Patch in order to contact Starfleet Command. This area disrupted communications as well as the ship's warp drive. The Battle of the Briar PatchEdit Main Article: Battle of the Briar Patch Two Son'a battle cruisers were sent by Ahdar Ru'afo to intercept the Enterprise before she left the Briar Patch and severely damaged the ship in the process. The warp core was ejected in order to seal a dangerous tear in subspace created by the isolytic weaponry of the Son'a. Riker was able to outwit the Son'a by collecting metreon gas native to the Briar Patch then venting it behind the ship. When the Son'a used their weapons, the gas exploded, destroying one ship and severely damaging the other. Geordi La Forge half-jokingly commented that the tactic could become known as the Riker Maneuver. The Enterprise later returned to the Ba'ku planet to aid Captain Picard disarming the Son'a collector. They ran into Ru'afo's flagship on their way there and Commander Riker pretended to ram into the flagship but instead flew over it and used its phaser banks to fire at it. When the collector started to blow up, the Enterprise beamed up Picard and left Ru'afo to destroyed in the collector while it blew up. The Enterprise later left Briar Patch to leave for Earth.(Star Trek: Insurrection) 2375-2379Edit The Enterprise visited Earth for several days in 2376, around the time the Pathfinder Project made contact with the USS Voyager and conducted a mission about seven light years from Earth the following year. According to Deanna Troi, it was an important mission, but the objective was never discussed. (VOY: "Pathfinder", "Life Line") Sometime between 2375 and 2379 the Enterprise underwent a major refit. Four additional aft-facing photon torpedo tubes were added, along with one more forward-facing tube: a twin launcher aft of the bridge, a single launcher above the aft hangar deck and a single launcher at the forward base of the bridge terracing. The bridge was refitted with handrails and the consoles were improved across the port and starboard walls with more detailed displays. Additionally, new nacelle pylons were fitted at that time, slightly longer, broader and more sharply swept than the originals and fitted with four additional phaser arrays. (Star Trek Nemesis) Stopping Shinzon Edit USS Enterprise-E, aft The Enterprise in 2379 In 2379, the Enterprise returned to Earth for the wedding of William T. Riker and Deanna Troi. She departed for Betazed, where another ceremony, a traditional Betazoid wedding, was scheduled. Discovery of B-4Edit While en route, the ship detected unusual positronic signals from the Kolarin system, discovering another Soong-type android, the prototype B-4. Shortly following, the Enterprise was ordered to Romulus for a meeting with the new Praetor, Shinzon, who apparently wanted to initiate peace talks. Both the discovery of B-4 and the peace overtures turned out to be a ruse to capture Captain Picard and discover tactical positions of Starfleet vessels. USS Enterprise-E and Scimitar following collision extraction Enterprise faces and collides with the Scimitar Shinzon's True GoalsEdit Once it became clear Shinzon was going to use his starship, the Scimitar, to destroy all life on Earth and wage war on the Federation, the Enterprise was to join Star Fleet Battle Group Omega and make a stand against Shinzon. Battle of the Bassen RiftEdit Shinzon caught up to the Enterprise in the Bassen Rift and, in the ensuing confrontation, the vessel was severely damaged, including a major hull breach on the bridge, destroying the viewscreen and controls and disabling the warp core. As a last resort, Picard ordered Counselor Deanna Troi to take control of the Enterprise and have it ram the Scimitar, resulting in the loss of much of the saucer section's forward area. The collision disabled the Scimitar, but Shinzon, driven by vengeance, activated his deadly thalaron weapon and trained it on the Enterprise. The weapon was overloaded and the Scimitar was destroyed due to interference from Commander Data, who sacrificed himself to save the Enterprise, Picard and, indirectly, Earth. USS Enterprise-E in drydock 2 Enterprise in drydock over Earth Following the Scimitar incident, the Enterprise returned to Earth where it underwent an extensive repair in one of the orbiting spacedocks. (Star Trek Nemesis) A cut scene from the script for Star Trek Nemesis revealed that it was the starship USS Hemingway that towed the critically damaged Enterprise to Earth. According to the Star Trek Nemesis script and a deleted scene, the Enterprise was to explore the Denab system following her refit. In this scene you can also see Commander Martin Madden, the new executive officer, his awkward first encounter with Picard (having, as a joke, been given laughably inaccurate advice by Riker) and a new captain's chair with something most Star Trek bridges have lacked: a seatbelt. Technical information Edit USS Enterprise E at warp, 2375 The Enterprise-E at warp In her original configuration, the Enterprise-E was under 700 meters long and had 24 decks according to Jean-Luc Picard, although Deck 26 was reported as being controlled by the Borg. She was equipped with twelve phaser arrays and five torpedo tubes. Picard and crew depart The main bridge of the Enterprise By 2379, the Enterprise-E had undergone at least one refit, including four additional phaser arrays and five additional torpedo tubes. The number of decks was also increased by five to a minimum of 29. (Star Trek Nemesis) However, if the ship did have a Deck 26 during the Borg attack, despite the number mentioned by Picard, then it could have also had a Deck 29, without any change in the interim. Sections included deflector control, stellar cartography, hydroponics (on deck 11) and one sickbay ward. Main engineering and sickbay were on Deck 16. (Star Trek: First Contact) In the script of Star Trek Nemesis, Picard mentions the main Dorsal output of the ventral type XII phasers on average was 125,000 TeraJoules but was not stated by Picard due to confusion of audiences. John Eaves stated this to be true when asked about the script. (John Eaves official website PM) " The total output of phasers was indeed added to the script at one point but was removed due to it being unneeded, (125,000 TeraJoules)"(citation needed • edit) The ship could be controlled by a manual steering column located on the bridge. (Star Trek: Insurrection) She was also the first Enterprise to be equipped with an Emergency Medical Hologram. (Star Trek: First Contact) Ronald D. Moore commented that, as of First Contact, the Enterprise-E "definitely" had no children aboard. (AOL chat, 1998) USS Enterprise-E shuttlebay The Enterprise's forward shuttlebay The Enterprise carried a newer design of shuttlecraft as well as numerous other forms of transportation including a warp-capable captain's yacht, the Cousteau, (Star Trek: Insurrection) and a special multipurpose shuttlecraft, the Argo. (Star Trek Nemesis) The yacht was installed as a part of the saucer section and detached upon deployment. Other auxiliary craft were launched from two shuttlebays; one at the aft end of the secondary hull and another near the aft end of the primary hull. Crewmembers included those of the Human, Vulcan, Bajoran, Betazoid, Bolian and Trill species, as well as a Klingon and an android. (Star Trek: Insurrection) In The Q Continuum trilogy by Greg Cox, it is stated that the Enterprise uses the bio-neural gel packs used by USS Voyager. Command crew Edit Commanding Officer Jean-Luc Picard (2372–) William T. Riker (2375) (acting) First Officer/Executive Officer William T. Riker (2372–2379) Second Officer/Operations Officer/Science Officer Data (2372–2379) Chief Engineer Geordi La Forge (2372–) Tactical Officer/Security chief Daniels (2372–2375) Worf (Acting 2373, 2375, 2379) Chief Medical Officer Beverly Crusher (2372–) Counselor Deanna Troi (2372–2379) Conn Hawk (2373) Kell Perim (2375) Branson (2379) See also: USS Enterprise personnel Scenes cut from the theatrical release of Star Trek Nemesis (but included in the 2003 and 2005 DVD releases) state that Commander Martin Madden took over for Riker as first officer and that Beverly Crusher left the ship to head up Starfleet Medical. Early versions of the script made reference to an Andorian ops officer. The new counselor was female, according to dialogue. Novels set after Nemesis have ignored these deleted scenes and several new characters were created by the authors. Beverly Crusher returned to the Enterprise, beginning a romantic relationship with Captain Picard, eventually marrying him and as of the third book of the Star Trek: Destiny trilogy Lost Souls, she was pregnant with their first child. Worf was also promoted to commander and became the Enterprise's new first officer. In the Countdown comic mini-series leading up to Star Trek, which was set in 2387, Picard had left the Enterprise and Starfleet, becoming Federation ambassador to Vulcan. Worf had again left Starfleet and become a general in the Klingon Defense Force and a restored Data (in the body of B-4) was now captain of the Enterprise. Geordi La Forge had also retired from Starfleet to design ships, including the Jellyfish, although it is listed as having been commissioned by the Vulcan Science Academy. Also, the storyline for Star Trek Online has Data as being brought back by the Soong Foundation (with assistance from Geordi La Forge) and being given command of the Enterprise after Picard retired. The Starships Enterprise United Earth: XCV 330 • NX-01 Federation: NCC-1701 • NCC-1701-A • NCC-1701-B • NCC-1701-C • NCC-1701-D • NCC-1701-E • NCC-1701-J Terran Empire (mirror universe): NX-01 • NCC-1701 Federation (alternate reality): NCC-1701 • NCC-1701-A Battle Group Omega starships USS Archer • USS Aries • USS Enterprise-E • USS Galaxy • USS Hood • USS Intrepid • USS Nova • USS Valiant Appendices Edit Appearances Edit This list contains 4 items (show all • hide all) Star Trek films: (3) VOY: (1) References Edit This list contains 4 items (show all • hide all) DS9: (1) VOY: (3) Background information Edit Enterprise-E, galaxy class A Galaxy-class Enterprise-E Following Star Trek Generations, the six-foot filming model for the Galaxy-class USS Enterprise-D had been modified to have the registry number read "NCC-1701-E". Penny Juday, the archivist at Paramount Pictures, had no explanation for this change as of 19 October 2001. (TNG Season 2, Disc 6: "Inside Starfleet Archives"). It turned out that the change was done at ILM by John Goodson prior to crating up the model after completion of Generations, presumably on the assumption that the new Enterprise might be a Galaxy-class ship as well and having the number changed over already would save whoever did the special effects the trouble of having to change it over themselves. (Industrial Light & Magic: Into the Digital Realm, p. 60) The Enterprise-E was, in fact, the only replacement for a previously-destroyed "hero" ship that was not of the same class as its predecessor, as opposed to USS Enterprise-A (and its alternate reality counterpart) , the USS Defiant (NCC-75633) and the Delta Flyer II. It was principally designed by John Eaves under the supervision of Herman Zimmerman. Using Eaves's sketches, Rick Sternbach drafted the blueprints for a ten-foot physical model. Eaves and Zimmerman also supervised the interior design of the bridge, engineering and corridors, although many sets from Star Trek: Voyager were also reused during Star Trek: First Contact and Star Trek: Insurrection. Though the Enterprise-E was mentioned in several episodes of Voyager, the ship was never seen outside of the films. However, the interior of the ship is visible in a communication with Deanna Troi in VOY: "Life Line" as well as a turbolift interior built for the films which was re-purposed for the Enterprise-D in ENT: "These Are the Voyages...". The ten-foot physical model, constructed under the supervision of John Goodson at Industrial Light & Magic (ILM), was used for visual effects shots during Star Trek: First Contact, alongside a CGI version. In Star Trek: Insurrection and Star Trek Nemesis, CGI versions of the ship completely replaced the physical model. The Nemesis CGI model included several modifications designed by John Eaves. In addition to the new weapons mentioned above, the warp pylons were slightly modified and the connection between the primary and secondary hulls near the main shuttlebay was made more sleek. The model of the Enterprise-E from Star Trek: First Contact (Lot #107) was sold at the 40 Years of Star Trek: The Collection auction on October 5, 2006 for US$132,000 including the buyer's premium (the winning bid was US$110,000). [1] There has been some confusion about the number of decks on the Enterprise-E. The construction blueprints of the filming miniature created for Star Trek: First Contact explicitly label 23 decks. In the film, Picard told Lily Sloane that the ship had 24 decks, while the master systems display on the bridge allows either interpretation. Earlier on, however, Daniels had reported that the Borg are in control of Decks 26 through 11. Michael and Denise Okuda say in their text commentary on the film, during the scene in which Picard tells Lilly about the 24 decks: "Unfortunately, earlier in this film, we are told that the ship has at least 26 decks. We can't imagine that Picard doesn't know his own ship, so we theorize that the other two decks are top secret for some reason. Either that, or his memory was affected by his earlier Borg assimilation. It certainly couldn't be a goof, because the design of the ship changed slightly during filming." In Star Trek Nemesis, the Remans beam onto Deck 29. This could mean that Picard did not tell Lily the truth and there are actually more than 24 decks, or that more decks were added to the ship prior to Star Trek Nemesis. It may also be the case that Picard was counting only finished decks, as there could have been decks left unfinished for future expansion. Also, there was the possibility that Picard may have intentionally withheld or lied about certain aspects of the Enterprise-E design in the event that Lily was assimilated by the Borg. Also in Nemesis, the Reman Viceroy fell several decks down a maintenance shaft. Because the Viceroy and the other Remans boarded the ship on Deck 29, it had been assumed that the ensuing battle took place on Deck 29 and that the Viceroy fell from that deck, implying that there could be 35 or more decks, or that the normal deck scheme was altered in some way that the ship could have more named decks than it measured in height. This was not the case as signage on the corridors where the phaser fight between the Remans and the Enterprise officers took place indicate they were actually on Deck 9. This suggested that the two parties encountered each other about halfway to their destinations (Enterprise officers to Deck 29, the Remans to the bridge on Deck 1). Size Edit It is apparent from lineup charts that every new starship Enterprise is slightly longer than the previous one. In Star Trek: First Contact, Picard informs Lily Sloane that the Enterprise-E is "almost seven hundred meters long", in accordance with its intended size of 2,248 feet (685 meters). John Eaves describes the rationale as follows: When the "E" had a final approved design, we drew up a chart of all the Enterprises in profile. Herman [Zimmerman] and I set down a whole bunch of cutouts of the "E" in various sizes to see where this new ship should scale with the others. We found one size that looked appropriate and we put a scale to its length and that would be 2,248 feet. Rick [Sternbach] was waiting to do the blueprints and add his creativity to the design, so we gave him a drawing with this one measurement. From there he sized the whole ship ... [2] By January 7, 1997, the following dimensions from Rick Sternbach had been added to FAQ: A History of Ships Named Enterprise: [3] Length: 2,248' Beam: 820' Height: 290' L of saucer: 1,150' Nacelle span: 700' L of nacelles: 1,056' The same length, beam and height (in meters) appear on the SciPubTech poster from around the same time. In addition, the length of 2,248 feet is listed in at least three comparison charts prepared for Star Trek: First Contact. [4] It can also be seen in the charts prepared for Star Trek: Insurrection. [5] The Star Trek Nemesis size chart puts it at 2,250 feet, consistent with a size revision during either the filmed or the unfilmed stage of redesign. [6] [7] Apocrypha Edit In the novel Ship of the Line, the Enterprise was given to Captain Morgan Bateson for its shakedown cruise, which included war games near the Klingon border. Along for the ride, as temporary chief engineer, was Montgomery Scott. Some missions of the Enterprise during the Dominion War are featured in Behind Enemy Lines, Tunnel Through the Stars and Tales of the Dominion War. In the DS9 Millennium book series, the Enterprise was destroyed at the Battle of Rigel VII in an alternate future that the intrepid heroes of Deep Space 9 later prevented. Star Trek: A Time to..., set during the year leading up to Star Trek Nemesis, featured the Enterprise being involved in a major political scandal that disgraces the ship and her crew for much of the coming year; the final duology in that series features the Enterprise being ordered to lead an invasion and occupation of a sovereign planet, with resemblance to the current real life world political situation at the time the novels were written. A "TNG relaunch" of sorts followed the Enterprise's activities after Nemesis; the first book in the series, Death in Winter, was released in September 2005. The novel Resistance established that before he left the Enterprise for the Titan, Commander Riker christened this Enterprise's version of the crew lounge, or Ten Forward, as the "Happy Bottom Riding Club," a name Worf absolutely hated and refused to use under any circumstances. The name for the lounge was derived from a similar watering hole that old Earth astronauts used to frequent. It also establishes that every ship's computer that was built during the last decade has encrypted information about Romulan cloaking technology, which can be decrypted in case of emergency using an admiral's code and thus enable the crew to build a cloaking device. In Resistance the crew separated the saucer section from the engine section (a feat this Enterprise had previously not done) and then cloaked the engine section to engage a Borg cube. During Resistance, Worf is promoted to the official first officer after acting in the position in an unofficial capacity during the ship's reconstruction after its confrontation with the Scimitar. In Q&A, an encounter with Q reveals that his past contact with the crew has been to prepare them for an encounter with "Them", a race far above even the Q, with Picard's response convincing Them that the universe deserves to exist. The novel Before Dishonor allies the crew of the Enterprise with Spock and Seven of Nine as they are forced to reactivate the original planet killer after Admiral Janeway is assimilated and becomes the new Queen of a Borg super-cube, the confrontation ending with the loss of Pluto, the destruction of the cube and Janeway's apparent death. The Destiny miniseries culminates in the final destruction of the Borg after the Titan learns their true origin, but the Federation is left devastated by the subsequent invasion, with much of the later novels focusing on the role the Enterprise will play in the reconstruction amid the creation of the Typhon Pact, an "anti-Federation" consisting of some of the Federation's most notorious adversaries, including the Romulans, the Tholians and the Breen. After the events of The Fall miniseries, the Enterprise is sent on a new mission of exploration. In the Star Trek: The Next Generation Technical Manual (which was printed before Star Trek: First Contact), it was speculated that the Enterprise-E might be a Nova-class ship. USS Enterprise-E, Countdown The Enterprise-E in Countdown, Issue 2 In Star Trek: Countdown, the Enterprise was still active as of 2387 with Data as captain, having been revived after successfully imprinting his neural network into B-4's existing CPU. The timeline for Star Trek Online follows the storyline in the Countdown comic series, with Data as captain into the 25th century. The timeline only mentions that the Enterprise-E left service around 2408, but its ultimate fate was unclear; however, by 2409, a new Odyssey-class vessel is christened Enterprise (NCC-1701-F), implying that her predecessor was decommissioned or destroyed. The short story "Unexpected Honor", written for issue 40 of Star Trek Magazine in May 2012, revealed that the Enterprise-E was destroyed in an ambush by the Undine at Starbase 236 in 2408; among the survivors was Captain Data, who retired from Starfleet to take up teaching on Earth. The Enterprise has also featured in many apocryphal productions, including the strategy games Star Trek: Armada, Star Trek: Armada II, Star Trek: Bridge Commander, Star Trek: Starfleet Command III and Star Trek: Elite Force II, Star Trek: Legacy and most recently Star Trek Online. 705
The Flood / Re: Hilda is probably the best show ever« on: May 25, 2019, 09:27:49 PM »
Imperial II-class Star Destroyer
Production information Manufacturer Kuat Drive Yards[1] Line Imperial-class Star Destroyer[1] Model Imperial II-class Star Destroyer[1] Class Star Destroyer[1] Technical specifications Length 1,600 meters[2] MGLT 60 MGLT[3] Maximum atmospheric speed 975 kilometers per hour[4] Engine unit(s) KDY destroyer-I ion engines (3)[5] Cygnus Spaceworks gemon-4 ion engines (4) (Emergency use)[5] Hyperdrive system Equipped[6] Power plant Solar ionization reactor[5] Shielding Deflector shield generator domes (2)[5] Armament Turbolaser batteries (60)[4] Heavy ion cannon emplacements (60)[4] Tractor beam projectors (10)[4] Complement 20 All Terrain Armored Transports[7] 30 All Terrain Scout Transports[7] At least 2 Gozanti-class cruisers[8] 8 Lambda-class T-4a shuttles[7] TIE/ln space superiority starfighters (72)[9] Docking bays At least 2[8] Crew Officers (9,200)[7] Enlisted crew (27,850)[7] Stormtroopers (9,700)[10] Consumables 2 years[10] Communication systems Communications tower[11] Usage Role(s) Carrier[9] Command ship[9] Affiliation Galactic Empire[9] Imperial Navy[9] Ubrik Adelhard's Imperial remnant[12] Jakku Imperial remnant[6] [Source] "Imperial Two-class. They're trying to hail us now." ―Carklin Ryoon, upon seeing three Imperial II-class Star Destroyers emerge from hyperspace — Gnome-speakernotesListen (file info)[src] The Imperial II-class Star Destroyer, also known as an Impstar-Deuce, was a Star Destroyer model manufactured by Kuat Drive Yards for use by the Imperial Navy. Part of the Imperial-class line, the class served as successor to the Imperial I-class Star Destroyer. Armed with a plethora of weapons, including turbolasers and ion cannons, the 1,600-meter-long capital ship could be used to subjugate a planet or serve as a command ship for other vessels. Following the death of Emperor Palpatine in 4 ABY, the Imperial II-class Star Destroyer Torment was dispatched to Naboo as part of Operation: Cinder, an order from the late Emperor to destroy Imperial planets with satellites. However, the attack was thwarted by the Rebel Alliance and the Torment was destroyed before it could withdraw. Later in the Contingency, in 5 ABY, three Imperial IIs from an Imperial remnant took part in the Battle of Jakku against the New Republic, although the Star Destroyers fled from the battle. They were later destroyed by the Sovereign Latitudes of Maracavanya's Executor-class Star Dreadnought Liberty's Misrule. Contents[show] CharacteristicsEdit General characteristicsEdit Torment The Torment was an Imperial II-class Star Destroyer. Part of the Imperial-class Star Destroyer line, the Imperial II-class Star Destroyer was a capital ship model built by Kuat Drive Yards for the Imperial Navy to replace the Imperial I-class Star Destroyer. Like its predecessor,[1] the Imperial II-class measured 1,600 meters in length,[2] was painted a light shade of gray, was wedge-shaped and had a raised bridge tower. However, it featured[13] a communications tower[11] between its two deflector shield generator domes,[5][13] whereas standard[14] ships of the Imperial I-class had a tractor beam targeting array in the same location.[15] Imperial II-class Star Destroyers were powered by a solar ionization reactor[5] located on the ventral hull.[13] PropulsionEdit Ships of the class were propelled by three[9] KDY destroyer-I ion engines,[5] and they also had four[9] backup Cygnus Spaceworks gemon-4 ion engines.[5] This allowed for speeds of sixty MGLT in realspace[3] and nine-hundred and seventy-five kilometers per hour in an atmosphere.[4] A hyperdrive was also equipped, allowing the ships to travel in hyperspace.[6] Weapons systems and complementEdit "The Impstar-Deuce has a complement of seventy-two TIE fighters, princess." ―Shara Bey, to Leia Organa, upon their approach to the Torment[src] Like all Imperial-class vessels, Imperial II-class Star Destroyers were armed with sixty turbolaser batteries, sixty heavy ion cannon emplacements, and ten tractor beam projectors.[4] The ships carried with them seventy-two TIE/ln space superiority starfighters,[9] at least eight Lambda-class T-4a shuttles, at least twenty All Terrain Armored Transports and thirty All Terrain Scout Transports, the latter two of which were transported to planetary surfaces by at least two Gozanti-class cruisers. All these vessels were stored in the ships' two large hangar bays, which were located side by side in the anterior wall of an indentation in the ventral hull.[8] 9,700 stormtroopers crewed the Star Destroyer,[10] along with various other Imperial Military personnel such as TIE fighter pilots[9] and Imperial officers. MSE-6 series repair droids were also present in the ship's corridors.[13] Two years worth of consumables were kept on the vessels to maintain the crew.[10] BridgeEdit Torment bridge The Torment's bridge "Clear the bridge." ―Captain Lerr Duvat, upon the arrival of the messenger[src] Organized almost identically to that of the Imperial I-class,[16] the Imperial II-class had a command bridge with a central command walkway and two pits where Imperial officers operated their console stations, which were arranged perpendicular to the central walkway.[13] RoleEdit An Imperial II-class Star Destroyer was capable of commanding an assault on an entire planet, which could include controlling smaller siege vessels[9] or using its large carrying capacity to deliver a surface assault force.[8] The ship could also form part of a fleet.[17] HistoryEdit It is requested that this article section be expanded. Please improve it in any way that you see fit, and remove this notice once the article section is more complete. Early historyEdit By 5 BBY,[18] Kuat Drive Yards had started manufacturing the Imperial II-class Star Destroyer after the run of the Imperial I class ended with the Devastator, a ship which would go on to become the flagship of Darth Vader, Imperial enforcer and Sith apprentice to Emperor Palpatine.[1] Some Imperial Is, including the Devastator, were upgraded to feature bridges with communication towers,[14] like Imperial IIs.[9][11] In or before 0 BBY,[19] at least four Imperial II-class Star Destroyers were amongst roughly twenty ships in an Imperial Navy fleet above the planet Scarif, home of the Death Star battle station.[17] The Torment's attackEdit "I've got an Imperial-class Star Destroyer at two-two mark six…" "…Looks like a Deuce." "Well, we knew this wouldn't be easy…" ―Shara Bey, Leia Organa and Sosha Soruna discuss the Torment[src] Seventeen days after the Battle of Endor[13] in 4 ABY,[20] which had seen the Rebel Alliance defeat the Galactic Empire with the death of Emperor Palpatine,[21] and subsequent retreat of remaining Imperial forces,[8] the Imperial Imperial II-class Star Destroyer[9] Torment was visited by a messenger droid. The droid delivered a posthumous message from the Emperor, ordering the ship's captain, Lerr Duvat, to scour the planet Naboo using weather-altering satellites,[13] as part of the Contingency's[6] Operation: Cinder, an Imperial plan to ensure both the Empire and its enemies would fall following the Emperor's death.[13] Restoration vs Torment The Torment was destroyed by the Restoration. Assisted by Lieutenant Gulin, Duvat immediately set course for Naboo. Upon the Torment's arrival at the planet, he deployed the satellites in order to create massive storms across Naboo.[13] However, a group of N-1 starfighters from Naboo, piloted by the rebels Shara Bey, Leia Organa and Sosha Soruna, attacked the satellites. In retaliation, the Star Destroyer's complement of TIE fighters was deployed to engage the attackers.[9] Just as the three starfighters were about to be destroyed by the TIEs, the Rebel Alliance arrived with the MC80 Star Cruiser Restoration[9] and Danger Squadron, a squadron of X-wing starfighters.[8] Together with the Naboo starfighters, they destroyed the remainder of the satellites and the Torment, despite an attempt by the Star Destroyer to withdraw.[9] Before its destruction, however, the Torment managed to deploy part of its planetary assault force, which briefly attacked Naboo's capital of Theed before being neutralized by an ion pulse from the Theed Royal Palace, and then captured.[8] Eleodie Maracavanya's findEdit "These ships are running. Look at the battle damage—they've taken fire, and recently. And behold those hyperspeed vectors—they're coming from near to the Unknown. They're coming from Jakku. We do a little cleanup here for the New Republic, then we send them the bill." ―Eleodie Maracavanya explains the plan to destroy the three Imperial II-class Star Destroyers to the Liberty's Misrule's crew — Gnome-speakernotesListen (file info)[src] In 5 ABY,[22] three Imperial II-class Star Destroyers were part of the last major Imperial remnant, which fought in the Battle of Jakku against the New Republic, the Rebel Alliance's successor state. However, the Star Destroyers fled from Jakku, and after jumping out of hyperspeed in Wild Space, their captains attempted to seek solace with a small fleet of ships led by the[6] Executor-class Star Dreadnought[23] Liberty's Misrule, which they thought was another Imperial remnant.[6] However, the fleet was actually under the command of pirate Eleodie Maracavanya of the Sovereign Latitudes of Maracavanya. Maracavanya deduced that the ships had come from Jakku, and ordered the destruction of the vessels, much to the surprise of crew member Carklin Ryoon. Maracavanya then elaborated on the decision to the Liberty's Misrule's crew, citing that the New Republic could grant the group some legitimacy if they destroyed the vessels, as it was likely they would appreciate the cleanup following their battle. All vessels then opened fire on the three Star Destroyers, with Maracavanya believing they stood no chance of survival.[6] Behind the scenesEdit Notable appearancesEdit The Imperial II-class Star Destroyer debuted in the Star Wars canon in Shattered Empire, Part II, a 2015 comic written by Greg Rucka and illustrated by Marco Checchetto, Emilio Laiso and Angel Unzueta. Although the Torment's class was not mentioned in the issue,[13] it would later be identified as an Impstar-Deuce in the next issue of the series, Shattered Empire, Part III, which was also written by Rucka.[9] The class' full name was revealed in the 2016 reference book Star Wars: Rogue One: The Ultimate Visual Guide, written by Pablo Hidalgo.[1] Avenger-ESBHD The Avenger, an Imperial II-class Star Destroyer in the Legends continuity The Imperial II-class Star Destroyer was originally created for[24] the 1980 film Star Wars: Episode V The Empire Strikes Back,[25] although it is only confirmed to have appeared in that film in the Star Wars Legends continuity.[24] This is because, in the new canon, it is not known if the class appears in content that features Imperial-class Star Destroyers with communications towers, such as The Empire Strikes Back. The reason for this is that some Imperial I-class Star Destroyers, which normally featured a tractor beam targeting array,[15] were upgraded to have a communications tower.[14] As Imperial II-class Star Destroyers also had communications towers, the two classes could have been indistinguishable.[11] In Legends, the Imperial II-class Star Destroyer first appeared[24] in the The Empire Strikes Back's novelization, written by Donald F. Glut, which was released in the same year as the film itself.[26] However, the ship's class was not revealed until the term ISD II was used by the 1989 supplement The Star Wars Rules Companion,[27] and the term Imperial II Star Destroyer was used by the Imperial Sourcebook, also released in 1989.[28] InconsistenciesEdit Torment The incorrect depiction of the Torment On the first page of Shattered Empire, Part II, illustrated by Emilio Laiso, the Torment was mistakenly depicted[13] with the targeting array of an Imperial I-class Star Destroyer.[15] This was rectified in the last page of the same issue, this time drawn by Marco Checchetto,[13] as well as in its later appearances in Shattered Empire, Part III[9] and Star Wars Battlefront II.[8] AppearancesEdit Star Wars Battlefront II A New Dawn Lost Stars Lost Stars webcomic Battlefront: Twilight Company Galaxy of Adventures logo Star Wars Galaxy of Adventures – "Chewbacca - The Trusty Co-Pilot" Galaxy of Adventures logo Star Wars Galaxy of Adventures – "Stormtroopers vs. Rebels – Soldiers of the Galactic Empire" Galaxy of Adventures logo Star Wars Galaxy of Adventures – "Han Solo - Galaxy's Best Smuggler" Smuggler's Run: A Han Solo & Chewbacca Adventure Han and the Rebel Rescue Smuggler's Run animated comic Smuggler's Run, Part 1 Princess Leia, Part II Princess Leia, Part III Princess Leia, Part IV Princess Leia, Part V 706
The Flood / Re: is this not a good topic??« on: May 25, 2019, 10:46:03 AM »
Bright Noa (ブライト・ノア Buraito Noa?) is a character from the Universal Century timeline. At the beginning of in Mobile Suit Gundam, Bright is an officer candidate without a commission from the Earth Federation Space Forces, but takes command as the highest-ranking surviving military personnel. Bright's commands include the White Base, the shuttle Temptation, Anti Earth Union Group's Argama, the entire AEUG fleet, and Londo Bell's Ra Cailum.
Contents[show] Character Bright Noa is a loyal and dedicated soldier both in war and peace. He is known for his competence, strong leadership and ability to quickly adjust to complex situations. Thrust into leadership at a young age and by chance, and with a crew comprised largely of civilians and minors, he nevertheless demonstrated an affinity for command, and has been a key member of the Earth Federation Forces ever since. He has regularly proven himself in unfavourable situations, such as the early parts of Mobile Suit Gundam and Mobile Suit Gundam ZZ. As captain, he enforces strict military discipline and regulations, and does not hesitate to punish his crew when they step out of line. A prime example of ability to maintain discipline and make tough decisions for one's own good is throwing the protagonist Amuro Ray into the brig for insubordination and for going AWOL. Additionally, Bright is not above using physical force to discipline crew members who are being insubordinate or otherwise disruptive. He once slapped Amuro after he refused to pilot the Gundam, despite Amuro knowing full well that his duties ensured the safety of the White Base and its crew; he punched Kai Shiden for being loud and obnoxious; and after Emma Sheen launched without permission, he ordered her to return to the bridge later for "correction".[1] He is considered to be the most experienced field commander in mobile suit warfare, and is often granted top-notch military equipment and has ace pilots under his command, such as Amuro Ray, Char Aznable, and Kamille Bidan. Yet Bright is known for relying on standard and reliably proven tactics rather than acts of bravado. Many would consider Bright to be one of the most successful field commanders in the Universal Century, as he has led his ships and fleets victorious in the One Year War, the Gryps Conflict, the First Neo Zeon War, and the Second Neo Zeon War. Bright has a strong moral compass and never hesitates to make the morally right decision for the better of all, even if he has to disobey orders from his superiors. For instance, he decided to act pre-emptively during the Londo Bell-Neo Zeon encounter in Char's Counterattack. A more prominent example is in Zeta Gundam, where he defected to Anti Earth Union Group rather than continue to serve the corrupt and oppressive Earth Federation. Although Bright is not a Newtype, he has nevertheless has some traits and experiences associated with them. He has received several telepathic messages over the series, and can sense when someone in his proximity is "like Amuro" (including Kamile Bidan, Judau Ashta and Banagher Links). History One Year War Bright Noa is a 19-year-old Earth Federation Forces Ensign who is stationed on the SCV-70 White Base as a junior line officer. As he arrives to his assignment, he runs into chief engineer Lieutenant Tem Ray, who shows Bright a picture of his son, Amuro. When Zeon pilot Char Aznable attacks Side 7 after discovering the secret Project V, Bright scrambles to get the evacuees onto the White Base while a pilot in the RX-78-2 Gundam fights off the MS-06 Zaku II. He eventually realizes that Amuro, whom he hasn't met yet, is the only living candidate to pilot the Gundam. Due to the surprise attack, all the original staff officers on the White Base are either killed or incapacitated. Captain Paolo Cassius, though alive, is badly wounded and not fit for command; therefore, responsibility for the ship falls upon the young Bright, who immediately takes action in putting together a suitable crew from the surviving civilian refugees to crew the ship. Among them is a woman named Mirai Yashima, who has piloting experience; Bright selects her to be the helmsman. When Bright and the Captain Paolo finally contact Amuro, Bright is upset that the pilot is just a kid and is ready to remove him, when Captain Paolo points out that they have no one else to replace him. Therefore, Bright reluctantly allows Amuro to pilot the Gundam for the time being. Under pursuit by Zeon forces, the White Base flees to the Federation base Luna II. Upon arrival, the White Base is refused entry, and Admiral Wakkein orders Bright and the rest of the crew detained over their use of top-secret military hardware. Bright attempts to warn the officers of an impending Zeon attack, but is ignored. As predicted, the Zeon attack, but Wakkein refuses to let Bright and the others use the White Base and Gundam to fight it off; Captain Paolo intervenes, telling Wakkein that they are the only ones equipped to handle it and that he will take full responsibility. The crew fight off the Zeon attack and prepares for atmospheric re-entry to Earth. During the battle, Paolo dies from his wounds; with his death, Bright becomes the official commander of the White Base. Landing deep in Zeon-controlled territory, the White Base is forced to fight its way to Federation space. Each battle tests them, bringing them closer together and honing their skills. In the beginning, it is thanks to the cutting-edge technology of the White Base and the Gundam, along with some timely luck, that allow the crew to survive; but as the war progresses, the White Base develops into a formidable unit. Nicknamed "The Trojan Horse" by Zeon forces, Bright and the White Base develop a mighty reputation. By the time they rendezvous with the main Federation fleet, their reputation precedes them, and the Federation leadership decides to use the ship as a major element in Federation operations. Likewise, the crew becomes so skillful in such a short amount of time that the Federation brass decides to keep them together rather than to assign a veteran military crew to take over. Bright is promoted to lieutenant junior grade for his proven effective leadership, and Mirai is accepted into the Federation Forces military and given an automatic officer's commission as an ensign, making her the ship's First Officer and second-in-command. Bright leans heavily on Mirai for counsel during difficult decisions, and together they form a strong core military leadership for the ship. Bright remains captain of the White Base throughout the One Year War, participating in the major operations, including Operation Odessa, the defence of Jaburo, and the last stand of Zeon at asteroid fortress A Baoa Qu. After the war, Bright and Mirai get married, and they have two children together, Cheimin and Hathaway. Gryps Conflict BrightZNT Bright (27) in Mobile Suit Zeta Gundam: A New Translation After the One Year War, Bright, like most of his comrades aboard White Base, was alienated by the High Command of the Earth Federation Space Forces. He was promoted to commander and assigned to captain the shuttle spacecraft Temptation, whose primary missions were to escort high-ranking Earth Federation officials. Bright defected to the AEUG to aid their struggle against the Titans after being beaten up by Titans officers, including Bask Om himself, when he objected to a set of unethical orders. Considering his veteran experience in mobile suit warfare as the captain of White Base during the One Year War, AEUG commissioned Bright with the rank of captain and gave him command of the assault space carrier Argama, which was the flagship and crown jewel of the AEUG fleet.[1] Bright Noa worked together with his former adversary, Char Aznable, and together they formed the core leadership of the Argama. With their combined battle experience and expertise of mobile suits, they truly became a force to be reckoned with and not taken lightly. After Commodore Blex's assassination, Char became the face and idealistic leader of AEUG, but it was Bright who took over command of the military forces. As captain of the AEUG flagship, Bright assumes command of the entire AEUG fleet and effectively leads them in all major battles. Several highlights of Bright's tour of duty as captain of the Argama include the attack on Federation Headquarters at Jaburo and Kilimanjaro, Operation Maelstrom, and the final three-way battle between the fleets of the AEUG, Titans, and Axis Zeon near the Gryps Two space colony. After the climatic battle at Gryps Two, the AEUG fleet was left crippled and Bright was the sole experienced military commander within the ranks of AEUG leaders. First Neo Zeon War Bright zz 46 Bright (28) in Mobile Suit Gundam ZZ He continued to command the Argama during ZZ Gundam. After taking the Argama to the colony Shangri-La to repair the Argama and take Kamille to the hospital, he and the crew of Argama was attacked by an old foe Yazan who was helped by Judau Ashta and his friends. While Judau attempted to steal the Zeta Gundam, as he was able to make it move, Bright compared him to Kamille and Amuro. Eventually when Yazan revealed his true colors, Judau in the Zeta Gundam defeated him and left before Bright could ask his name. While in Shangri-La, Bright had to deal with multiple attacks by Mashymre Cello's troops and Judau's attempts to steal the Zeta Gundam, but all the encounters ended with Judau defeating the Neo Zeon forces and then returning the Zeta Gundam. Due Judau's abilities, Bright believed he could be a major help to the AEUG, and would send him the Zeta Gundam to train him and force him to join the Argama. Eventually he was successful, and all of Judau's friends and Judau himself joined the Argama. Soon afterwords Roux Louka would join the Argama, as a liaison to La Vie en Rose, for supplies. After a struggle with Mashymre's forces, the Argama successfully leaves Shangri-La. After docking with La Vie en Rose, he meets old friend Emary Ounce who gives Judau the ZZ Gundam and upgrades the Argama to have the Hyper Mega Particle Cannon. After Fa leaves the AEUG, he creates the Gundam team which made of Judau and his friends whom uses the ZZ Gundam, Zeta Gundam, Gundam Mk-II, the rebuilt Hyaku Shiki and Mega Rider. Throughout the show he attempts to train the Gundam team to be real soldiers. While his friend Emary housed romantic feelings for him and was very attractive, Bright remained loyal to his family. On a mission in Dublin, he met Fa and Kamille once more. When he learned Haman planned to drop another colony, the Argama and Karaba, were able to rescue a portion of the population of Dublin at the price of destroying most of Karaba's force and highly damaging the Argama. He and the Gundam team went back to La Vie en Rose, to get the new Nahel Argama. Bright despite being assigned as the ship's captain, was separated from it in combat and he with Shita and Qum returned to La Vie en Rose. He later met with Sayla Mass and Leina Ashta, who discussed of Char's whereabouts and possible plans. He and the rest of the AEUG forces would later arrive at Core 3 to back up the Nahel Argama's crew in battle only to find the battle over. He later confronted an emotional Judau and allowed Judau to punch him. He later saw off Judau and Roux to the Jupiter Fleet. After the Axis Zeon was defeated, AEUG forces were integrated back with the Earth Federation, and Bright was re-instated as an officer of the Earth Federation with the rank of Captain. Second Neo Zeon War BrightCCA Bright (33) in Mobile Suit Gundam: Char's Counterattack He was later made the commanding officer of Londo Bell Task Force, as seen in the movie Char's Counterattack. He was rejoined by his former subordinate Amuro Ray. They played critical roles during the events in Char's Counterattack when they encountered and fought Char Aznable's Neo Zeon rising faction for the last time. Third Neo Zeon War Gundam uc bright Bright (36) in Mobile Suit Gundam Unicorn In UC 0096, Bright Noa would later appear in Mobile Suit Gundam Unicorn and he is still the commanding officer of the Londo Bell corps. His ship, the Ra Cailum, has been equipped with a Minovsky Craft System, enabling it to operate on Earth and in space. Bright is present at the Battle of Dakar where a Zeon mobile armor lays waste to the city. He is ordered by Ronan Marcenas to either secure or destroy the Garencieres, which housed the key to Laplace's Box. Bright sees the job as a personal request, however. Ronan also asks Bright to take his son, Riddhe, on board the ship with his Delta Plus. Upon meeting, Riddhe requested that he not be given special treatment, to which Bright states he'll receive none. As Riddhe turned away to look at a picture of Amuro, Bright received a call that the Garencieres had moved. The Ra Calium moved to Torrington to repel a Zeon remnant assault on the city and military base. They are later witnessed to the Unicorn Gundam transforming into Destroy Mode and battling the Shamblo. Once the battle is over, Bright orders Riddhe to take the Gundam into custody. However, the Vist Foundation launches its own RX-0 Unicorn Gundam 02 Banshee, which swiftly captures the Unicorn. All three suits are then brought aboard the Ra Calium, while at the same time the ship became occupied by Vist Foundation member, agitating the crew. Bright calmed his crew, reminding that they still serve General Staff HQ and they should consider the Foundation people to be part of them. Although their operating circumstances changed, Bright states that their mission was to hunt down the Garencieres. As he exited the briefing room, Meran informed him that the supplies delivered to the Garuda are fit for royalty. He then visits Banagher Links, the Unicorn's pilot, in his cell and kindly questioned him. Banagher laments that if anyone finds the coordinates to Laplace's Box, "that place" would become a battlefield and that more people like Loni would die. Bright asks if Banagher escaped the Garencieres, but he says that the group simply let him go, and that Zinnerman was unhappy with the operation. Bright agrees based on the movements of the ship, and asks if he was given free will despite being a technical prisoner. Banagher says that he never felt as though Zeon was an enemy, since was a civilian and not a soldier taught to discern friend from foe. As Bright leaves, he tells Banagher not to give up because he has strength, though he says it was dumb luck that he found the Unicorn. Bright says that it may have been pure luck, but those were the circumstances of all the Gundam pilots before him, and that he chose to pilot the Gundam on his own. He asks what gave Banagher the resolve to pilot the suit, and he says there's someone he wanted to help: Mineva Lao Zabi. Bright and Meran then go to a private terminal and get in contact with Beltorchika Irma, who confirmed that the General Revil had been deployed on a covert mission for General Staff HQ. Bright suspected they are targeting the Nahel Argama, as its crew know of Laplace's Box. Beltorchika asks if they should warn the Nahel Argama, because it would not stand a chance against the General Revil. Bright then stated that they need to get contact with the Garencieres and had Kai Shiden negotiate a plan to save Mineva from the Garuda and get the Unicorn away from the Foundation. As the crew prepared to transfer the Unicorn to the Garuda, Banagher broke away from his Vist bodyguards to try and talk to Riddhe. Bright catches him and while the Tri-Stars occupy the bodyguards, he inform Banagher of the plan. As the Tri-Stars, the Banshee and Riddhe/Delta Plus make their way to the Garuda, the carrier is assaulted by the Garencieres. The Ra Calium attempted to go on alert, but Meran stopped them, reminding everyone to remain focused on the mission. Bright and everyone else were later witness to the psychofield generated by the Unicorn enabling the Garencieres to make orbit with the Nahel Argama. As the Ra Calium sets out for space to rendezvous with the Nahel Argama, Bright received a reprimand from Martha Vist Carbine for allowing the Unicorn to fall into the Sleeves' hands. Bright admits that his plan backfired, with Frontal capturing the Nahel Argama due to his quick response. Martha asks how he could lose track of the group, and Bright explains that the standard patrol fleets were removed from the area due to the nature of the General Revil's mission, and subtly implies the Vist Foundation's hand in the conflict. He confronts Martha on what Laplace's Box actually is, and she tells him about The Lady and the Unicorn tapestry that has been a Vist keepsake. The "box" is guarded by a white unicorn and a black lion, and Martha tells Bright that if they can't protect the box, then they'll destroy it as she dismisses the services of Londo Bell. Bright is later informed by Kai that the Federation had rebuilt the Gryps Laser as Gryps II with the intention of destroying the Magallanica where the Box is located before it falls into anyone else's hands. With the Nahel Argama engaged in battle and no means of warning them nor being able to evacuate the colony, Bright orders the Ra Calium to descend to Earth. Upon arriving at Cheyenne Mountain, where Gryps II's control centre is based, Bright declared his authority as Londo Bell commander to inspect the place. When he enters the command center, he finds Chairman Ronan in the process of inserting the activation keys for the superweapon. He attempts to protest the decision, vowing to turn against the Federation if Ronan goes through with the plan, to which his superior calls his bluff. After he inserts the final activation key and starts charging Gryps II, Bright turns to leave, but then Alberto Vist revealed that Riddhe was piloting the Banshee and was in the line of fire. Bright turned to the base commander and insisted they shut off Gryps II, to which he was refused, as the laser was approaching critical mass and any accident would endanger the thousand people aboard the superweapon. Ultimately, the Magallanica is saved as the Unicorn and Banshee create a three-layered psychofield to deflect the laser. Soon after, Princess Mineva begins broadcasting to all of Earth and space, revealing the Box's secret, that it was the original Universal Century charter, which stated that Newtypes were meant to take part in government. Martha ordered that the General Revil intercept the Magallanica and stop the transmission, Alberto declares that the conspiracy is over with the Box's opening. Bright then tells Martha that the military will be taking over and that she as a civilian had no say. He then takes her in to questioning. U.C. 105 HASAULE-2-10 Bright Noa (45), U.C. 105 20 years after the events of the Second Neo Zeon War, Bright ends up in a position that no father should ever be forced into: As an officer of the Earth Federation military, he condemns Hathaway to death after Hathaway's capture as leader of the anti-Federation terrorist group Mufti. Apparently, Bright didn't know who the Mufti leader really was until the time of his execution, when he was completely unable to do anything to stop it; whether this was an unfortunate coincidence or the doing of his fellow commanders is unknown. This incident triggers Bright's definitive retirement from the military. After witnessing the execution and spending a long time in a heavy depression, Bright finally regains his spirits enough to open a small restaurant with his remaining relatives, Mirai and Cheimin. Notes & Trivia Bright was the captain of Gundam series' main mothership in Super Robot Wars series for a long time before his role was taken by Murrue Ramius in Super Robot Wars Alpha 3. In plot mainly as she still defers to his authority due to his experience not only with the One Year War but the events of the previous games in the series. In later games, mainly ones without UC Gundam, she does take the lead role, more so in games with Gundam SEED Destiny as she would be the experienced captain. In the first Super Robot Wars Z game, she was the lead captain of a part of the ZEUTH group while Bright was the other. In Super Robot Wars V, he defers to Captain Okita from Space Battleship Yamato 2199 due to the latter's age and experience, though Okita asks Bright to take over for him should he become unable to continue serving as the overall commander of that game's multiversal heroic fleet, known as the Earth Fleet Tenkuu. In the ending, Bright does fulfill Okita's wishes when Okita canonically dies like he did in his own series, even overseeing Okita's funeral and the decommissioning of the Tenkuu forces in the 'true' ending of the game. Not counting spin-offs, Bright is the most recurrent characters in the franchise. He made his debut in Mobile Suit Gundam, and continued in Zeta Gundam, Gundam ZZ, Char's Counterattack and finally Gundam Unicorn. Bright's only known pupil is Beecha Oleg, whom he trusted to take command of Nahel Argama. This makes Beecha as de facto Captain for Nahel Argama until Bright make his return. Bright is quite famous (or infamous) for slapping his crew members, usually to teach them some discipline. In one episode of Zeta Gundam, he even tells Lieutenant Emma to "get up on the bridge for some disciplinary action" while slapping the air. Fans consider his slaps "therapy" for young angsty pilots, turning them into "Men of Destiny" and argue he should have applied it to Kira in Super Robot Wars Alpha 3. However, this overlooks that it's often not Bright alone who convinces the pilots to pull themselves together; for instance, it was also Fraw's words to Amuro that got him piloting again. In Mobile Suit Gundam, Bright is mentioned to be from the city of Hong Kong and is sometimes listed as being British in official material. However, as the anime was produced before the deal in 1984 to return the city to China, it is unclear whether Bright Noa is meant to be British or Hong Kongese. 707
The Flood / Re: Aunt Josephine's fear had made her a bad guardian.« on: May 24, 2019, 10:42:06 PM »
The Ra Cailum was a battleship and the lead ship of the namesake of its class.
Contents[show] Technology & Combat Characteristics The class was constructed to make use of mobile suits, so it incorporates a hanger that can hold ten machines and two launch catapults into its design. The class has four two-barrel main beam turrets, twenty-two secondary anti-aircraft guns, and six missile tubes. The class also has eight engines and a pair of cooling fins to help improve fuel consumption and increase speed. Finally one new feature the Ra Cailum class possesses is the ability to deploy multiple decoy ships, balloon like objects that expand to the same size and shape as the ship with a similar color scheme. A close visual inspection would reveal which is real and which are fakes, however they were useful for fooling long-range inspection and sensors thanks to Minovsky particle interference. Armament 2-barrel Main Beam Gun The main weapons of the Ra Cailum-class are four 2-barrel mega-particle cannons situated on the dorsal and ventral hulls with three situated forward of the bridge and one to the bridge's aft. These guns provide full covering fire from all directions, ensuring the ship remains protected from threats on all approaches. 2-barrel Defensive Gun For anti-air/anti-mobile suit defense the Ra Cailum-class is equipped with twenty two two-barrel defensive guns. The guns are placed on hardpoints in various locations on the hull to ensure the ship is defended from mobile suits and aircraft no matter which direction attacks may come from. Missile Launcher The Ra Cailum-class is equipped with six missile launchers which, depending on the ordnance loaded, can be used for anti-ship or anti-mobile suit combat. Special Equipment & Features Minovsky Craft Emitters When scattered in open space or in the air, the repulsive forces between charged Minovsky particles cause them to spontaneously align into a regular cubic lattice structure called an I-field. An I-field lattice will slowly expand and scatter into space; however, if used correctly, the Ra Cailum can obtain low altitude flight under gravity without refueling. History Mobile Suit Gundam: Char's Counterattack The conclusion of the Federation's civil war and the defeat of the Titans had brought the colonial space separatist movement to a virtual fever pitch, and when the First Neo Zeon War ended, it was decided that a new organization should be created to inspect the colonies for left-over dissents and revolutionaries. The force created for this job was called Londo Bell, and they did inspect the colonies, but unlike the Titans, they were much more humane in their inspections. This task force was first to receive the new Clop-class cruisers and they also received the first battleship of the Ra Cailum-class, the Ra Cailum. The Ra Cailum was the largest battleship built to date, and it was adopted for use as a flagship by Captain Bright Noa, Londo Bell's commanding officer. The Ra Cailum also served as Amuro Ray's base of operation when he became a part of Londo Bell, which brought the MS contingent aboard the Ra Cailum to seven Mobile Suits and one Gundam. The Ra Cailum was also the first Federation ship to make use of the Base Jabber, a mobile suit sled that increased the operational range of Mobile Suits by providing them with an external fuel source to travel from one point to another. The Base Jabbers on the Ra Cailum were used to move Mobile Suits into battle so they would not use up their internal fuel on the flight to engage enemy forces. The Ra Cailum saw its first action on 3 March U.C. 0093, when the ship responded to a new Neo Zeon movement under the command of Char Aznable. In company with three of the Federation's Clop-class cruisers, the Ra Cailum raced to the scene and the Second Neo Zeon War began in earnest with the battle for Fifth Luna. Although the ship and its Mobile Suits fought valiantly, they failed in stopping the drop of Fifth Luna, which made land-fall on Lhasa, Tibet, then-location of Federation headquarters. Although damaged by the battle, Bright Noa ordered Ra Cailum to super-impose herself between the Neo Zeon forces and a disabled passenger shuttle that had wandered into the combat zone. When the battle died down, the shuttle captain and his passengers abandoned the disabled shuttle and were taken aboard the Ra Cailum as refugees; among those on the shuttle were Bright Noa's son Hathaway, Vice-Foreign Minister of the Earth Federation Adenaur Paraya, and his daughter Quess. Once aboard, Adenauer Paraya ordered Captain Noa to take the Ra Cailum to the space colony Londenion, located at Side 1, for the purpose of seeking contact with Neo Zeon leadership with the eventual intention of seeking a settlement to the war. The Ra Cailum arrived at Side 1 shortly thereafter and docked at the colony's spaceport. Here the civilians from the shuttle disembarked, and the ship's officers and crew enjoyed a brief shore leave while dockworkers hustled to get the battleship repaired, refueled, and restocked with supplies for its next operation. In particular, Ra Cailum 's bow had been blown off during the battle and had to be reconstructed from scratch. Meanwhile, the negotiations between the Federation and the Neo Zeon reach a conclusion: The Neo Zeon would surrender all of their warships in exchange for the asteroid Axis, which they purchased from the Federation with gold bullion. This seemed suspicious to one of the Federation's accountants, and he informed Bright Noa of Char's purchase and—fearing the worst—arranged for the Ra Cailum to receive 15 nuclear warheads. Armed with the warheads and the information of the purchase Ra Cailum and her task force set sail from Londonion on 12 March U.C. 0093 to pursue the Neo Zeon forces and ensure that they disarmed. Unfortunately, Londo Bell mistook ship-like balloons for the Neo Zeon fleet, which enabled the Neo Zeon fleet to capture Luna II and Axis with relative ease. Amuro Ray eventually saw through the balloon deception, and explained to the officers aboard the battleship that they had been tricked, and that the Neo Zeon already had control of Axis. Bright Noa ordered Ra Cailum to speed for Axis, but the Londo Bell forces arrived to late to stop the reactivation of the engines. As soon as Londo Bell was within range of Axis, the task force opened fire on the asteroid, and a massive battle for control of Axis erupted between the Londo Bell fleet and the Neo Zeon fleet, leading to the loss of several mobile suits. Bright Noa opted for the use of the nuclear missiles, but Ra Cailum's attempt to destroy the asteroid with the nuclear weapons failed. With time running out the battle subsided as Londo Bell's senior officers and Mobile Suit pilots reconvened aboard Ra Caium to prepare for one last ditch effort. Their plan called for the destruction of Axis' tail thrusters, which would cause the asteroid to miss earth entirely, but if that failed then Ra Cailum would have to close in and launch Mini-Mobile Suits (MMS) to infiltrate Axis and plant powerful explosives. The resulting explosion would split the Asteroid in two, causing it to miss earth entirely. Wasting no time Ra Cailum's Mobile Suit squad re-launched. The attempt to destroy the tail thrusters on Axis ended up failing, so Ra Cailum closed in on the Asteroid to allow a number of MMS to land on the Axis and plant high nuclear explosives, as per the plan. Despite murderous losses incurred by the Londo Bell forces the MMS unit succeeded in placing the explosives, and the resulting blast split Axis into two pieces, the latter of which was still headed for earth. Amuro Ray, through the use of his Nu Gundam, prevented the last piece from colliding with earth, thus bringing the battle for Axis to a close. Mobile Suit Gundam Unicorn Despite being damaged heavily(half the hull is gone) during the Second Neo Zeon War, Federation spent a huge amount of money repairing and refitting the ship, claiming it as a symbol of victory (even though it was strategic draw, with both sides losing equal amount) along with the extremely famous captain Bright Noa. By the time of the outset of the Third Neo Zeon War in U.C. 0096, the Ra Cailum had been transferred to Earth for testing of a newly installed Minovsky Craft System. During the time of the refit, the ship was equipped with a new team of mobile suits which included three RGM-96X Jestas and a new RGZ-91 Re-GZ (probably serving as a reminiscence of the legendary pilot Amuro Ray rather than actually for battle, since Re-GZ is considered as a failed prototype by both Londo Bell and AE). The Ra Cailum's Jesta team would be involved in the defense of the Earth Federation at Dakar while the ship was undergoing trials off the coast. After the attack on Dakar, the Ra Cailum was reassigned to the South Pacific area at the request of Federation Council member Ronan Marcenas. During this transfer, Ensign Riddhe Marcenas, along with his assigned MSN-001A1 Delta Plus, was transferred aboard the Ra Cailum to support the ship's mobile suit complement. Shortly after departing the Marcenas Manor, Captain Bright was notified of the attack on the Torrington Base in Australia. Heading there to observe and assist, Captain Bright orders the Ra Cailum into the area and launches the Jesta team and Delta Plus in support of the Federation Forces stationed in the area, which are all badly outmatched. All of the crew later bear witness to the RX-0 Unicorn Gundam transform into Destroy Mode. As soon as the AMA-X7 Shamblo is destroyed, Bright ordered Riddhe to secure the Unicorn. But before he could take action, the Vist Foundation deployed the RX-0 Unicorn Gundam 02 Banshee, which captured the Unicorn and all three suits were brought to the Ra Cailum. The crew became antsy with the Foundation occupying their ship. Soon, the Foundation arranged for the Unicorn to be brought to the Garuda, with the Banshee, Tri-Stars and Riddhe/Delta Plus to escort it. In transit, the Garencieres appeared and launched a sneak attack against the Garuda. The Ra Cailum attempted to go on alert but second-in command Meran stopped them, reminding that their mission is to escort the Unicorn to the Garuda. The Ra Cailum later went into space in pursuit of the Neo Zeons. Mobile Suit Gundam: Hathaway's Flash The Ra Cailum is seen again in U.C. 0105 as part of the 13th Independent Fleet. 708
Gaming / Re: Halo Mega Thread« on: May 24, 2019, 08:30:55 AM »I rewatched the Halo Wars 1 cinematics last night and they’re better than I remembered.Doesn't look power ranger enough for 343. This helmet design brought to you by: 709
The Flood / Re: Had any strange dreams lately?« on: May 23, 2019, 06:12:19 PM »
I had another one like the one I described this morning. I'd moved back into my old home but my mother and sister were there trying to control things. Dad and I were scared for our lives and called the cops, but my mom had already contacted them with some fake story. Dad and iade a run for it and got trapped in the roof.
I don't know what it is making me have these kinds of dreams but it's honestly kind of disturbing. 710
Gaming / Re: Sherlock Holmes 2: Magic Compton Boogaloo (Fate/Thread)« on: May 23, 2019, 06:03:40 PM »
Barbatos died in vein then
[ 711
Gaming / Re: Sherlock Holmes 2: Magic Compton Boogaloo (Fate/Thread)« on: May 23, 2019, 02:37:58 PM »Yo, man I love Illya as much as you do but FFS put MERLIN out with the MLB Golden Carp CE. My whole friend list is being to fucking retarded right now. 714
Gaming / Re: Pokémon Sword & Shield for Nintendo Switch revealed« on: May 22, 2019, 02:32:43 PM »my pikachu (who i named pancake) Cheat please make Alphy a mod. 715
The Flood / Re: Star Wars: Episode IX« on: May 22, 2019, 02:30:34 PM »A bunch of new images released for the film: These are sick but why does the first one look like a Borderlands screenshot? 716
Gaming / Re: WoW Classic "bugs" and Blizz response« on: May 19, 2019, 09:04:03 PM »
Wernt the community running their own WOW Classic at some point? whatever happened to that?
717
The Flood / Re: The Video Club is hosting a DOUBLE FEATURE tonight — Kill Bill, parts 1 & 2!« on: May 19, 2019, 09:00:34 PM »
Die of an overdose already
718
The Flood / Re: Solonoid is a fucking unstable person« on: May 19, 2019, 08:53:59 PM »
stop breathing
719
The Flood / Re: Tonight, the Video Club is hosting Fear and Loathing in Las Vegas!« on: May 19, 2019, 09:02:37 AM »
stop breathing
720
The Flood / Re: In case you missed it - I nearly lost my entire server yesterday« on: May 19, 2019, 01:16:26 AM »Who did you make this thread for? Are people from your server on sep7agon? 'cause I don't think any of the users from sep7agon are into your server and what's going on, but I could be wrong. Can you enlighten me? Making this thread just doesn't make sense for meHe's a deluded narcissist with some kind of chromosomal disorder and he's on god knows how many mind and hormone altering drugs. You expect anything he does to make sense? |