{"data":{"id":20052,"title":"Whitley's Guide - Vulcan","rsi_url":"https:\/\/robertsspaceindustries.com\/comm-link\/spectrum-dispatch\/20052-Whitleys-Guide-Vulcan","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-links\/20052","api_public_url":"https:\/\/api.star-citizen.wiki\/comm-links\/20052","channel":"Undefined","category":"Undefined","series":"News Update","images":[{"id":26463,"name":"source.jpg","rsi_url":"https:\/\/media.robertsspaceindustries.com\/weozjmuuh3hwh\/source.jpg","alt":"","size":843046,"mime_type":"image\/jpeg","last_modified":"2019-09-19T15:49:32+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/26463","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/26463\/similar"},{"id":27892,"name":"source.jpg","rsi_url":"https:\/\/media.robertsspaceindustries.com\/w3o9r4zgppm77\/source.jpg","alt":"","size":900916,"mime_type":"image\/jpeg","last_modified":"2021-09-06T14:48:40+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/27892","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/27892\/similar"},{"id":35808,"name":"StarCitizen_DAY12_Warbond_CCU_RSI_Vulcan.png","rsi_url":"https:\/\/robertsspaceindustries.com\/media\/b16vf7m9o8fy2r\/source\/StarCitizen_DAY12_Warbond_CCU_RSI_Vulcan.png","alt":"","size":3932270,"mime_type":"image\/png","last_modified":"2024-05-11T03:20:23+00:00","api_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/35808","similar_url":"https:\/\/api.star-citizen.wiki\/api\/comm-link-images\/35808\/similar"}],"images_count":8,"translations":{"en_EN":"This article originally appeared in Jump Point 7.12.\nAegis Dynamics Vulcan\nINITIAL DEVELOPMENT\nLike many Aegis Dynamics spacecraft, the Vulcan support ship has a long and storied history that stretches back several centuries to the height of the Messer era. In 2590, innovations in fuel refinement allowed ships to spend longer on the drift, so the UEEN requested proposals for a medium-sized support spacecraft with the flexibility to conduct both refueling and rearming operations. Given the military contracting process at the time, it was a foregone conclusion that Aegis would be awarded the project. Nevertheless, the Vulcan team opted to go beyond the military specification and develop what they referred to as a true \u2018three R\u2019 spacecraft: one capable of rearming, refueling, and repairing. Aegis\u2019 designers reasoned that if they could deliver a ship capable of supporting smaller fighters and bombers (rapidly becoming a more important aspect of naval doctrine), they would have a chance at building something instrumental to the UEEN\u2019s arsenal longer term.\n\nEarly prototypes would be completely different spacecraft compared to the models released three and a half centuries later. Early Vulcans lacked the BARD drones of the modern version, meaning that each of the three main processes had to be accomplished manually in a considerably more dangerous way. After a series of early accidents destroyed several Vulcans, engineers developed a process by which munitions were kept inert and then activated by remote once loaded. Early refueling using the Vulcan platform was a more difficult proposition. Spacecraft were required to maneuver extremely close and connect via external probe for the duration of fueling. Unlike with munitions, there was no option to make quantum fuel inert; crews were keenly aware of the increased danger during refueling. In ideal situations, refueling was done at a full stop. However, this was often not possible under combat conditions, earning Vulcan crews the genuine respect of fighter and bomber squads. However, repair was a comparatively simple process, with the ship\u2019s rear compartment allowing the storage of repair tools and supplies that could be easily accessed by crewmen in external maneuvering suits.\n\nAs was common of support spacecraft at the time, the early Vulcans were completely unarmed and featured limited armor. As advances in process and military strategy improved over the decades, the Vulcan\u2019s defensive capabilities would be reworked significantly.\n\nThe resulting ship, formally launched in 2594, impressed the UEEN on its formal review, prompting them to order nearly four times the number stated in the original proposal. As the ship found its place in active service, Aegis prioritized future development to keep it from becoming obsolete. Changes to the Vulcan platform happened rapidly as the company adapted to battlefield reports and worked to integrate the latest technology. Within a decade, the simple but dangerous \u2018workshop\u2019 concept for repair operations had been replaced with a formalized process using manipulator arms, while training for in-flight refueling had improved and significantly reduced casualties. Changes to all three of the Vulcan\u2019s processes would occur regularly, supported by Aegis at every turn. The modern Vulcan took shape in 2895 with the adoption of Saga Datasystems BARD drones that standardized the ship\u2019s support functions and significantly reduced danger. By using the soon-to-be industry standard drones instead of developing their own, the overall cost-per-unit of the Vulcan was reduced and Aegis entered into a strategically important relationship with an up-and-coming technology company.\n\nTHE VULCAN AT WAR\nThe Vulcan was first bloodied in 2603 during the early battles of the Second Tevarin War. By the start of the conflict, the spacecraft had been part of the UEEN inventory for almost ten years. There it had proven its worth in peacetime, supporting and expanding the range of convoys and patrols. Its first combat missions, however, did not go well. Tevarin forces quickly realized that they could reduce UEE effectiveness by targeting the slow and under-defended support ships. For the first six months of the war, Vulcan losses were significantly heavier than anticipated and a number of strike missions failed when returning bombers were unable to refuel and were destroyed by Tevarin fighters. These problems were solved by both manufacturing and doctrinal changes. Aegis developed a battlefield upgrade for early Vulcans that improved armor and added a defensive turret; changes that would speak to the eventual rework of the ship. The military itself adapted the ship\u2019s role by operating Vulcans in groups of three: one for repair, one for rearming, and one for refueling. These trios were then assigned escort fighters, defending the ships when they came under attack and using their services in downtime.\n\nThe Vulcan saw no such problems when first pitted against the Vanduul. In early battles, the Vanduul seemed to have limited interest in targeting support ships at all, instead focusing on engaging fighters and taking others as scrap or prizes. Continued advances to the platform allowed the ships that first battled the Vanduul to be much more effective, both at their core roles and in defending themselves. With drones improving the \u2018three Rs\u2019, Vulcans were pressed into service in greater numbers than ever before, both in their traditional roles and as fleet support, with multiple Vulcans often assigned to closely follow destroyers and cruiser squadrons. In recent years, the UEEN has taken to deploying what they refer to as \u2018ranged strike groups\u2019 in an attempt to relieve pressure from the Vanduul. These strike groups consist of base-launched fighters and bombers supported by modern Vulcans to significantly extend their range and striking power, allowing them to deploy into enemy held territory to conduct raids. The strategy was developed around the idea of responding in kind to Vanduul anti-commerce raids and seems to be proving effective.\n\nTHE VULCAN AT PEACE\nThe Vulcan expanded beyond its original military role quickly due to the simplicity of the original design. Without military-grade weapons or advanced technologies like drones, the UEE saw little reason in preventing the sale of the design to corporate and private users. This gave the Vulcan its second life as a civilian support ship. Initial marketing was aimed at large corporations operating their own convoys that required support ships to operate safely. Aegis sold civilianized Vulcans in great numbers and, within five years, the design was a staple of well-trodden trade routes.\n\nWhat Aegis could not have predicted was the ship\u2019s ensuing popularity with so-called \u2018wayfarers\u2019. Initially started as an alliance between three hobbyist flying clubs in the late 29th century, wayfarer groups had become a kind of all-for-one do-gooder\u2019s organization supporting independent spacecraft owners. The Vulcan provided exactly what they had been lacking: a uniform flagship capable of providing the kind of assistance they had previously been doggedly adapting civilian spacecraft to offer. Today, you can find these versatile and durable ships in most systems, whether they\u2019re attached to companies, orgs, or as independent service providers.","de_DE":"Dieser Artikel erschien urspr\u00fcnglich in Jump Point 7.12.\nAegis Dynamics Vulcan\nURSPR\u00dcNGLICHE ENTWICKLUNG\nWie viele andere Raumschiffe von Aegis Dynamics hat auch das Unterst\u00fctzungsschiff Vulcan eine lange Geschichte, die mehrere Jahrhunderte bis zum H\u00f6hepunkt der Messer-\u00c4ra zur\u00fcckreicht. Im Jahr 2590 erm\u00f6glichten Innovationen in der Treibstoffveredelung, dass Schiffe l\u00e4nger unterwegs sein konnten. Daher forderte die UEEN Vorschl\u00e4ge f\u00fcr ein mittelgro\u00dfes Unterst\u00fctzungsraumschiff an, das sowohl Betankungs- als auch Wiederaufr\u00fcstungsoperationen durchf\u00fchren konnte. In Anbetracht des damaligen milit\u00e4rischen Vergabeverfahrens war es eine ausgemachte Sache, dass Aegis den Zuschlag f\u00fcr das Projekt erhalten w\u00fcrde. Dennoch entschied sich das Vulcan-Team, \u00fcber die milit\u00e4rische Spezifikation hinauszugehen und ein echtes \"Drei-R\"-Raumschiff zu entwickeln: ein Raumschiff, das sowohl aufr\u00fcsten als auch auftanken und reparieren kann. Die Konstrukteure von Aegis waren der Meinung, dass sie mit einem Schiff, das in der Lage ist, kleinere J\u00e4ger und Bomber zu unterst\u00fctzen (ein Aspekt, der in der Marinedoktrin immer wichtiger wird), die Chance h\u00e4tten, langfristig etwas zu bauen, das f\u00fcr das Arsenal der UEEN von Bedeutung w\u00e4re.\n\nDie fr\u00fchen Prototypen waren ganz andere Raumschiffe als die Modelle, die dreieinhalb Jahrhunderte sp\u00e4ter auf den Markt kamen. Den fr\u00fchen Vulkaniern fehlten die BARD-Drohnen der modernen Version, was bedeutete, dass jeder der drei Hauptprozesse auf eine wesentlich gef\u00e4hrlichere Weise von Hand ausgef\u00fchrt werden musste. Nachdem eine Reihe von fr\u00fchen Unf\u00e4llen mehrere Vulkanier zerst\u00f6rt hatte, entwickelten die Ingenieure ein Verfahren, mit dem die Munition inaktiv gehalten und nach dem Laden per Fernbedienung aktiviert werden konnte. Die fr\u00fche Betankung mit der Vulcan-Plattform war ein schwierigeres Unterfangen. Die Raumfahrzeuge mussten extrem nah man\u00f6vrieren und f\u00fcr die Dauer der Betankung mit einer externen Sonde verbunden werden. Anders als bei der Munition gab es keine M\u00f6glichkeit, den Quantentreibstoff zu inertisieren; die Besatzungen waren sich der erh\u00f6hten Gefahr beim Betanken sehr bewusst. Im Idealfall wurde der Treibstoff bei einer Vollbremsung getankt. Unter Kampfbedingungen war dies jedoch oft nicht m\u00f6glich, was den Vulcan-Besatzungen den Respekt der J\u00e4ger- und Bomberstaffeln einbrachte. Die Reparaturen waren jedoch vergleichsweise einfach, denn im hinteren Bereich des Schiffes konnten Reparaturwerkzeuge und Vorr\u00e4te gelagert werden, die f\u00fcr die Besatzungsmitglieder in den \u00e4u\u00dferen Man\u00f6veranz\u00fcgen leicht zug\u00e4nglich waren.\n\nWie bei Unterst\u00fctzungsraumschiffen zu dieser Zeit \u00fcblich, waren die fr\u00fchen Vulkanier v\u00f6llig unbewaffnet und hatten nur eine geringe Panzerung. Mit den Fortschritten in der Entwicklung von Verfahren und milit\u00e4rischen Strategien wurden die Verteidigungsf\u00e4higkeiten der Vulkanier im Laufe der Jahrzehnte erheblich \u00fcberarbeitet.\n\nDas daraus resultierende Schiff, das 2594 offiziell vom Stapel lief, beeindruckte die UEEN bei ihrer offiziellen \u00dcberpr\u00fcfung und veranlasste sie, fast viermal so viele Schiffe zu bestellen wie im urspr\u00fcnglichen Vorschlag vorgesehen. W\u00e4hrend das Schiff seinen Platz im aktiven Dienst fand, setzte Aegis Priorit\u00e4ten bei der zuk\u00fcnftigen Entwicklung, um zu verhindern, dass es veraltet. \u00c4nderungen an der Vulcan-Plattform erfolgten schnell, da sich das Unternehmen an die Berichte der Gefechtsfelder anpasste und daran arbeitete, die neueste Technologie zu integrieren. Innerhalb eines Jahrzehnts wurde das einfache, aber gef\u00e4hrliche \"Werkstatt\"-Konzept f\u00fcr Reparaturarbeiten durch ein formalisiertes Verfahren mit Manipulatorarmen ersetzt, w\u00e4hrend die Ausbildung f\u00fcr das Betanken w\u00e4hrend des Fluges verbessert und die Zahl der Opfer erheblich reduziert wurde. An allen drei Prozessen der Vulcan wurden regelm\u00e4\u00dfig \u00c4nderungen vorgenommen, die von Aegis auf Schritt und Tritt unterst\u00fctzt wurden. Die moderne Vulcan nahm 2895 mit der Einf\u00fchrung der BARD-Drohnen von Saga Datasystems Gestalt an, die die Unterst\u00fctzungsfunktionen des Schiffes standardisierten und die Gefahren erheblich reduzierten. Durch den Einsatz der bald zum Industriestandard werdenden Drohnen, anstatt eigene zu entwickeln, wurden die Gesamtkosten pro Einheit der Vulcan gesenkt und Aegis ging eine strategisch wichtige Beziehung mit einem aufstrebenden Technologieunternehmen ein.\n\nDIE VULCAN IM KRIEG\nDie Vulcan wurde erstmals 2603 w\u00e4hrend der ersten Schlachten des Zweiten Tevarin-Krieges eingesetzt. Zu Beginn des Konflikts geh\u00f6rte das Raumschiff bereits seit fast zehn Jahren zum Inventar der UEEN. Dort hatte es sich in Friedenszeiten bew\u00e4hrt, indem es die Reichweite von Konvois und Patrouillen unterst\u00fctzte und erweiterte. Seine ersten Kampfeins\u00e4tze verliefen jedoch nicht gut. Die tevarinischen Streitkr\u00e4fte erkannten schnell, dass sie die Effektivit\u00e4t der UEE verringern konnten, indem sie die langsamen und schlecht verteidigten Hilfsschiffe ins Visier nahmen. In den ersten sechs Monaten des Krieges waren die Verluste der Vulcan deutlich h\u00f6her als erwartet und eine Reihe von Eins\u00e4tzen scheiterte, weil die zur\u00fcckkehrenden Bomber nicht auftanken konnten und von Tevarin-J\u00e4gern zerst\u00f6rt wurden. Diese Probleme wurden sowohl durch die Herstellung als auch durch \u00c4nderungen der Doktrin gel\u00f6st. Aegis entwickelte ein Gefechtsfeld-Upgrade f\u00fcr fr\u00fche Vulkanier, das die Panzerung verbesserte und einen Verteidigungsturm hinzuf\u00fcgte; \u00c4nderungen, die f\u00fcr die sp\u00e4tere \u00dcberarbeitung des Schiffs sprechen sollten. Das Milit\u00e4r selbst passte die Rolle des Schiffes an, indem es die Vulkanier in Dreiergruppen einsetzte: eine zur Reparatur, eine zum Aufr\u00fcsten und eine zum Auftanken. Diesen Trios wurden dann Geleitj\u00e4ger zugeteilt, die die Schiffe bei Angriffen verteidigten und ihre Dienste in den Ausfallzeiten in Anspruch nahmen.\n\nDie Vulcan hatte keine solchen Probleme, als sie zum ersten Mal gegen die Vanduul antrat. In den ersten Gefechten schienen die Vanduul nur wenig Interesse daran zu haben, Unterst\u00fctzungsschiffe anzugreifen, sondern konzentrierten sich darauf, J\u00e4ger anzugreifen und andere als Schrott oder Beute zu nehmen. Die kontinuierliche Weiterentwicklung der Plattform erm\u00f6glichte es den Schiffen, die zuerst gegen die Vanduul k\u00e4mpften, viel effektiver zu sein, sowohl in ihren Kernaufgaben als auch in ihrer Verteidigung. Da Drohnen die \"drei Rs\" verbesserten, wurden Vulkanier in gr\u00f6\u00dferer Zahl als je zuvor eingesetzt, sowohl in ihrer traditionellen Rolle als auch als Flottenunterst\u00fctzung, wobei mehrere Vulkanier oft Zerst\u00f6rern und Kreuzergeschwadern dicht auf den Fersen waren. In den letzten Jahren sind die UEEN dazu \u00fcbergegangen, so genannte \"Fernkampfgruppen\" einzusetzen, um den Druck der Vanduul zu verringern. Diese Angriffsgruppen bestehen aus basisgest\u00fctzten J\u00e4gern und Bombern, die von modernen Vulkaniern unterst\u00fctzt werden, um ihre Reichweite und Schlagkraft deutlich zu erh\u00f6hen und in feindlich besetzte Gebiete vorzudringen. Die Strategie wurde mit dem Ziel entwickelt, auf die Angriffe der Vanduul gegen den Handel zu reagieren, und scheint sich zu bew\u00e4hren.\n\nDER VULKANIER IM FRIEDEN\nDie Vulkanier haben sich aufgrund ihrer einfachen Bauweise schnell \u00fcber ihre urspr\u00fcngliche milit\u00e4rische Rolle hinaus entwickelt. Ohne milit\u00e4rische Waffen oder fortschrittliche Technologien wie Drohnen sah die UEE wenig Grund, den Verkauf des Designs an Unternehmen und private Nutzer zu verhindern. So bekam die Vulcan ihr zweites Leben als ziviles Hilfsschiff. Die anf\u00e4ngliche Vermarktung richtete sich an gro\u00dfe Unternehmen, die ihre eigenen Konvois betrieben und f\u00fcr den sicheren Betrieb Unterst\u00fctzungsschiffe ben\u00f6tigten. Aegis verkaufte zivilisierte Vulkanschiffe in gro\u00dfer Zahl und innerhalb von f\u00fcnf Jahren war die Konstruktion ein fester Bestandteil ausgetretener Handelsrouten.\n\nWas Aegis nicht vorhersehen konnte, war die anschlie\u00dfende Beliebtheit des Schiffes bei den sogenannten \"Wanderern\". Urspr\u00fcnglich als Zusammenschluss dreier Hobby-Fliegerclubs im sp\u00e4ten 29. Jahrhundert gegr\u00fcndet, hatten sich die Wanderer-Gruppen zu einer Art Weltverbesserer-Organisation entwickelt, die unabh\u00e4ngige Raumschiffbesitzer unterst\u00fctzt. Die Vulcan bot genau das, was ihnen gefehlt hatte: ein einheitliches Flaggschiff, das die Art von Unterst\u00fctzung bieten konnte, f\u00fcr die sie zuvor hartn\u00e4ckig zivile Raumschiffe umgebaut hatten. Heute findest du diese vielseitigen und robusten Schiffe in den meisten Systemen, egal ob sie Unternehmen, Orgs oder unabh\u00e4ngigen Dienstleistern angeschlossen sind.","zh_CN":"This article originally appeared in Jump Point 7.12.\nAegis Dynamics Vulcan\nINITIAL DEVELOPMENT\nLike many Aegis Dynamics spacecraft, the Vulcan support ship has a long and storied history that stretches back several centuries to the height of the Messer era. In 2590, innovations in fuel refinement allowed ships to spend longer on the drift, so the UEEN requested proposals for a medium-sized support spacecraft with the flexibility to conduct both refueling and rearming operations. Given the military contracting process at the time, it was a foregone conclusion that Aegis would be awarded the project. Nevertheless, the Vulcan team opted to go beyond the military specification and develop what they referred to as a true \u2018three R\u2019 spacecraft: one capable of rearming, refueling, and repairing. Aegis\u2019 designers reasoned that if they could deliver a ship capable of supporting smaller fighters and bombers (rapidly becoming a more important aspect of naval doctrine), they would have a chance at building something instrumental to the UEEN\u2019s arsenal longer term.\n\nEarly prototypes would be completely different spacecraft compared to the models released three and a half centuries later. Early Vulcans lacked the BARD drones of the modern version, meaning that each of the three main processes had to be accomplished manually in a considerably more dangerous way. After a series of early accidents destroyed several Vulcans, engineers developed a process by which munitions were kept inert and then activated by remote once loaded. Early refueling using the Vulcan platform was a more difficult proposition. Spacecraft were required to maneuver extremely close and connect via external probe for the duration of fueling. Unlike with munitions, there was no option to make quantum fuel inert; crews were keenly aware of the increased danger during refueling. In ideal situations, refueling was done at a full stop. However, this was often not possible under combat conditions, earning Vulcan crews the genuine respect of fighter and bomber squads. However, repair was a comparatively simple process, with the ship\u2019s rear compartment allowing the storage of repair tools and supplies that could be easily accessed by crewmen in external maneuvering suits.\n\nAs was common of support spacecraft at the time, the early Vulcans were completely unarmed and featured limited armor. As advances in process and military strategy improved over the decades, the Vulcan\u2019s defensive capabilities would be reworked significantly.\n\nThe resulting ship, formally launched in 2594, impressed the UEEN on its formal review, prompting them to order nearly four times the number stated in the original proposal. As the ship found its place in active service, Aegis prioritized future development to keep it from becoming obsolete. Changes to the Vulcan platform happened rapidly as the company adapted to battlefield reports and worked to integrate the latest technology. Within a decade, the simple but dangerous \u2018workshop\u2019 concept for repair operations had been replaced with a formalized process using manipulator arms, while training for in-flight refueling had improved and significantly reduced casualties. Changes to all three of the Vulcan\u2019s processes would occur regularly, supported by Aegis at every turn. The modern Vulcan took shape in 2895 with the adoption of Saga Datasystems BARD drones that standardized the ship\u2019s support functions and significantly reduced danger. By using the soon-to-be industry standard drones instead of developing their own, the overall cost-per-unit of the Vulcan was reduced and Aegis entered into a strategically important relationship with an up-and-coming technology company.\n\nTHE VULCAN AT WAR\nThe Vulcan was first bloodied in 2603 during the early battles of the Second Tevarin War. By the start of the conflict, the spacecraft had been part of the UEEN inventory for almost ten years. There it had proven its worth in peacetime, supporting and expanding the range of convoys and patrols. Its first combat missions, however, did not go well. Tevarin forces quickly realized that they could reduce UEE effectiveness by targeting the slow and under-defended support ships. For the first six months of the war, Vulcan losses were significantly heavier than anticipated and a number of strike missions failed when returning bombers were unable to refuel and were destroyed by Tevarin fighters. These problems were solved by both manufacturing and doctrinal changes. Aegis developed a battlefield upgrade for early Vulcans that improved armor and added a defensive turret; changes that would speak to the eventual rework of the ship. The military itself adapted the ship\u2019s role by operating Vulcans in groups of three: one for repair, one for rearming, and one for refueling. These trios were then assigned escort fighters, defending the ships when they came under attack and using their services in downtime.\n\nThe Vulcan saw no such problems when first pitted against the Vanduul. In early battles, the Vanduul seemed to have limited interest in targeting support ships at all, instead focusing on engaging fighters and taking others as scrap or prizes. Continued advances to the platform allowed the ships that first battled the Vanduul to be much more effective, both at their core roles and in defending themselves. With drones improving the \u2018three Rs\u2019, Vulcans were pressed into service in greater numbers than ever before, both in their traditional roles and as fleet support, with multiple Vulcans often assigned to closely follow destroyers and cruiser squadrons. In recent years, the UEEN has taken to deploying what they refer to as \u2018ranged strike groups\u2019 in an attempt to relieve pressure from the Vanduul. These strike groups consist of base-launched fighters and bombers supported by modern Vulcans to significantly extend their range and striking power, allowing them to deploy into enemy held territory to conduct raids. The strategy was developed around the idea of responding in kind to Vanduul anti-commerce raids and seems to be proving effective.\n\nTHE VULCAN AT PEACE\nThe Vulcan expanded beyond its original military role quickly due to the simplicity of the original design. Without military-grade weapons or advanced technologies like drones, the UEE saw little reason in preventing the sale of the design to corporate and private users. This gave the Vulcan its second life as a civilian support ship. Initial marketing was aimed at large corporations operating their own convoys that required support ships to operate safely. Aegis sold civilianized Vulcans in great numbers and, within five years, the design was a staple of well-trodden trade routes.\n\nWhat Aegis could not have predicted was the ship\u2019s ensuing popularity with so-called \u2018wayfarers\u2019. Initially started as an alliance between three hobbyist flying clubs in the late 29th century, wayfarer groups had become a kind of all-for-one do-gooder\u2019s organization supporting independent spacecraft owners. The Vulcan provided exactly what they had been lacking: a uniform flagship capable of providing the kind of assistance they had previously been doggedly adapting civilian spacecraft to offer. Today, you can find these versatile and durable ships in most systems, whether they\u2019re attached to companies, orgs, or as independent service providers."},"links_count":0,"comment_count":28,"created_at":"2024-07-09T21:00:00+00:00","created_at_human":"1 year ago"},"meta":{"processed_at":"2026-05-07 23:08:29","valid_relations":["images","links"],"prev_id":20051,"next_id":20053}}