Starships and planetary vehicles carry people, supplies, and equipment through the Old Republic. From passenger shuttles and independent freighters to combat vessels, speeders, and industrial machines, their capabilities shape where people can go and what they can accomplish. Their crews, service histories, and supporting infrastructure also make them lasting parts of everyday life.
This part of the Technology archive covers transportation, vessel systems, operating arrangements, and the support that keeps machines in service. It includes craft used for travel, combat, freight, exploration, and specialist work.
A vehicle’s role describes its intended work, but does not provide a complete specification. Two transports may differ substantially in passenger accommodation, cargo access, endurance, protection, or maintenance requirements. The individual machine’s configuration and history explain what its users can reasonably expect.
Transportation also creates relationships. A regular passenger service connects communities; an assigned craft connects a pilot to an organization; a privately operated ship connects its crew to customers, technicians, and familiar ports. These connections can matter without making every journey dangerous or every repair difficult.
Passenger space, cargo capacity, and accommodation are distinct considerations when choosing a transport. A ship used for occasional deliveries may need different facilities from one that houses its crew throughout extended voyages.
The XS Freighter demonstrates how these functions can coexist. Its design includes an enlarged cargo hold, concealed compartments, additional sleeping quarters, and a lounge. Laser and torpedo batteries supplement upper and lower turrets that can be operated manually or from the cockpit.
Those features belong to the documented design. For another freighter, establish its own arrangement: how cargo enters, where passengers stay, which areas remain accessible during a loaded voyage, and what the crew uses as living space.
A character can travel through scheduled passage, charter, institutional transport, or an invitation aboard another person’s ship. Ownership is only one way to gain access to transportation.
For a recurring shuttle or passenger service, establish its operating area and the connections it provides. Surface transfers, journeys between stations, and independent interstellar travel place different demands on the craft. “Shuttle” alone does not establish a hyperdrive, long-range endurance, or overnight accommodation.
A useful journey description identifies the departure point, destination, provider, and any consequential transfer. Routine passage can remain routine; details become important when they affect the people traveling or waiting for their arrival.
SWTOR’s Galactic Starfighter presents several distinct combat roles. Scouts emphasize speed and reconnaissance; strike fighters specialize in direct engagement; gunships deliver firepower at range; and bombers deploy mines and automated drones for defensive support.
These roles help explain a craft’s intended employment. They do not make every fighter equally suitable for pursuit, escort, reconnaissance, or sustained independent operations.
For a recurring pilot, establish the supporting arrangement: a squadron, carrier, planetary installation, private hangar, or another credible base. Flight experience, maintenance expertise, access to replacement equipment, and command responsibilities can belong to different members of that organization.
SWTOR’s named vessel designs illustrate how an assignment can shape construction, equipment, and interior space.
BT-7 Thunderclap — A Republic rapid-assault ship with substantial protection and armament, command and briefing facilities, an armory, a medical bay, and accommodation supporting extended squad deployments.
Defender — Built for Jedi missions, combining diplomatic rooms and secure Council communications with medical, cargo, meditation, and defensive facilities.
Fury — Developed for priority Imperial military assignments, with subsequent designs accommodating its popularity among Sith Lords.
X-70B Phantom — An experimental Imperial Intelligence design emphasizing discreet operation and advanced systems. Its original description presents limited prototypes unsuitable for mass production.
D5-Mantis — A compact combat vessel built for independent, long-range work. Retractable weapon assemblies and careful interior design support its role, while construction expense limited production.
A design’s original customer and an individual vessel’s later circumstances are separate matters. Where a ship has changed hands, explain the relevant transfer and distinguish surviving equipment from later alterations. An unusual acquisition should fit the established history without assuming that a former owner continues to supply personnel, credentials, or technical support.
For a capital ship used in roleplay, establish the scale of the community aboard as well as its military or logistical purpose. Command, engineering, flight operations, medical work, security, and supply can provide different perspectives on the same voyage.
A mobile base can also operate at a smaller or unspecified scale. StarForgeRP’s Aureline is a Czerka Interstellar recovery vessel supporting coordination, medical stabilization, technical examination, and evidence custody. Smaller craft conduct direct deployments while the larger vessel provides a recurring working base.
Its location reference establishes the relevant spaces, responsibilities, and access arrangements. Serving as a headquarters does not, by itself, establish a vessel’s classification as a capital ship.
Planetary transportation completes journeys that interstellar travel only begins. A landing field may still be some distance from a household, workplace, settlement, or expedition site.
For a particular speeder or transport, describe the features that affect its use: seating, cargo access, environmental protection, operating terrain, and storage. An open personal vehicle and an enclosed passenger carrier offer different experiences even when both reach the same destination.
Local vehicles can also establish familiar relationships through shared commuting, deliveries, hired transport, or a regular service route.
Working vehicles move materials, position equipment, and support construction or recovery. Their usefulness depends on the task they are configured to perform and the conditions in which that work takes place.
The KDY Orbital Lifter provides a specific Old Republic example. Kuat Drive Yards developed this personal heavy-construction vehicle for orbital engineering requiring more delicate handling than automation could provide.
For a recovery or engineering assignment, establish what must be moved, how the machine reaches it, and who operates the equipment. Tools, Industry & Specialist Equipment explains the wider workshop, fabrication, and recovery context.
Walkers provide another option for specialized movement and fieldwork. SWTOR’s Alliance Combat Patrol Transport, or AC-PT, is described as gathering intelligence while traversing hostile worlds and difficult terrain.
For a particular walker or heavy vehicle, identify its assignment, fitted equipment, operator, and deployment arrangements. Storage, transportation to the work area, and servicing may matter as much as movement once it arrives.
A model’s appearance as a player mount establishes neither universal civilian availability nor a complete account of its operational capabilities.
Describe propulsion through the journeys the vessel can undertake. Establish its sublight and hyperspace capabilities separately, including whether it can travel independently or relies on another craft for part of a deployment.
Fuel is an established strategic resource in SWTOR. Corellia’s Black Hole refineries process hypermatter used in starship travel and Republic and Imperial fleet operations. Fuel supply can therefore connect an individual ship to industrial workers, transport contracts, and wider military demands.
For a particular voyage, consider fuel, provisions, navigation information, and the condition of relevant systems. The Galactic Map explains geographic connections and travel considerations; distance on a map does not supply a universal journey time.
Define shipboard instruments by the questions they can answer. Detecting a contact, identifying a vessel, examining a damaged component, and interpreting a recorded transmission are different tasks.
Communications also involve more than carrying a transmitter. The intended recipient, available connection, authentication, and access permissions can affect an exchange. A secure channel does not grant unrestricted access to the institution at its other end.
Logs and telemetry can preserve useful evidence, but their meaning depends on what was recorded and what survives. Communications, Data & Security covers transmission, protected systems, information recovery, and the assessment of records.
Document the armament and defensive systems actually installed. The Thunderclap’s armor and modular shielding, the Defender’s shields and turbolasers, and the XS Freighter’s batteries and turrets demonstrate different configurations.
Protection should have a defined function. A ship’s ability to withstand one threat does not establish immunity to every weapon, environmental hazard, or internal failure. Equally, limitations should follow established equipment and circumstances rather than appear solely to force a particular outcome.
For a modification, consider mounting, power, control, ammunition where applicable, and maintenance. Weapons & Defense provides the related context for personal and battlefield equipment.
A recurring ship benefits from an understandable interior. Establish the spaces needed for the people and work aboard: sleeping areas, sanitation, meals, cargo handling, machinery access, and any specialist rooms.
SWTOR’s designs provide useful examples of deliberate specialization. The Defender includes diplomatic and meditation spaces; the Thunderclap supports squad briefings and medical work; the XS Freighter accommodates a resident crew alongside its freight operations.
For environmental and medical systems, describe the supported conditions and available resources. A treatment area may permit assessment and stabilization without providing every form of definitive care. Cybernetics & Medical Technology explains the distinction between equipment, clinical expertise, and continuing treatment.
Establish how the characters use the machine: as owners, passengers, employees, assigned personnel, borrowers, or contracted operators. An ordinary vehicle can have an ordinary purchase or service arrangement; unusual access deserves additional context when it affects the story.
Ownership, operational command, and specialist authority need not belong to one person. A captain may direct a voyage while an employer controls assignments and a medical professional makes treatment decisions. Boarding permission may leave particular compartments or records restricted.
Define the responsibilities that matter, including supplies, servicing, cargo acceptance, and damage. Disputed ownership or uncertain authority should remain unresolved until the relevant continuity establishes an answer.
Assign duties according to the vessel’s work and configuration. Piloting, navigation, engineering, communications, cargo handling, and specialist operations may be combined on one craft and divided among several people on another.
Shipboard droids can contribute technical upkeep, piloting, service, or other defined functions. Their abilities depend on their equipment, programming, and experience. Droids & Automation provides the broader context, including the distinction between a machine’s assigned duties and its individual history.
A reliable operating arrangement leaves room for complementary expertise. Familiarity with one vessel can make a technician or droid particularly valuable without making that individual an expert on every machine encountered.
Maintenance includes inspection, diagnosis, component replacement, adjustment, and testing. A crew may handle routine work aboard while using a workshop or shipyard for tasks requiring larger equipment or specialist knowledge.
For significant alterations, distinguish the original design, the present configuration, and work still in progress. Consider compatibility with existing components, access for servicing, power requirements, and changes to usable space. A modification can be successful without improving every aspect of the vessel.
Keep the service history that affects later play: a recognizable rebuild, a supplier-dependent replacement, an unresolved fault, or work performed by a recurring technician. Routine servicing need not become a recurring crisis.
A port’s usefulness depends on the services available there. Berthing, refueling, freight handling, passenger transfers, component supply, and major repairs are different functions. Establish which ones a particular destination provides when they affect an assignment.
Kuat Drive Yards illustrates the strategic importance of shipbuilding infrastructure. Its orbital manufacturing complex became the focus of Republic–Imperial fighting in SWTOR. That historical conflict provides context without determining its circumstances in every later story.
Mek-Sha offers a different setting: an inhabited asteroid where refueling, engineering, commerce, and local interests meet. Its location reference explains the community surrounding the docks.
Browse Galaxy for the wider setting and the Location Directory for documented destinations. Consult Current Setting when contemporary conditions affect a journey; that page contains major story spoilers. Local references and established events determine the circumstances at the destination.
An original vessel needs a clear identity and a useful place in the setting. Begin with its intended work and present users, then describe the features other participants need to understand it.
Purpose and scale — What work does it perform, and how large an operation does it support?
Origin and access — Was it built, purchased, assigned, transferred, inherited, or recovered?
Layout — Which spaces are established, and how do people and cargo move through them?
Configuration — Which propulsion, protective, communication, and specialist systems are fitted?
Personnel and support — Who operates it, and where does it obtain servicing and supplies?
Operating limits — Which conditions or assignments exceed its established capabilities?
Continuing history — Which previous owners, alterations, incidents, or relationships still matter?
Exact measurements are useful when they resolve a real question, such as whether equipment fits through a loading entrance. Otherwise, a coherent description may serve better than an unsupported technical specification.
Describe a proposed capability clearly enough that other participants can understand its consequences. Stealth, exceptional endurance, advanced automation, or unusual protection should have a particular basis and defined scope.
Choose details that invite another character to contribute. A vehicle can support a brief encounter, an ongoing working relationship, or a recurring setting shared across several stories.
Purpose — What journey or assignment brings these people aboard?
Origin — Does the craft’s acquisition connect its users to an employer, seller, former owner, or benefactor?
Expertise — Whose knowledge is needed for this particular operation?
Support — Which familiar port, workshop, supplier, or service crew makes the work possible?
Limits — What established condition requires a change of plan or outside assistance?
History — Could a previous repair, voyage, delivery, or transfer matter again?
Connections — Who is waiting for the crew, depending on the cargo, or hoping to join the next departure?
These questions can lead to cooperation as readily as conflict: a successful delivery earns another commission, a technician becomes a trusted contact, or passengers return as friends. Roleplay connects developing stories with their participants and consequences. Repeated use gives an ordinary machine a history worth remembering.
SWTOR can establish that a vessel or capability exists without supplying a complete technical specification. Combat statistics, upgrade slots, mount unlocks, travel shortcuts, and gameplay restrictions do not independently establish literal performance, price, rarity, ownership rules, or journey duration.
Use narrative descriptions and relevant evidence for consequential capabilities. Describe limitations with the same care.
A design from another Star Wars period needs an appropriate basis before appearing in an Old Republic story. Similarity of purpose or appearance does not establish the presence of that particular model.
Likewise, an exceptional prototype demonstrates what that prototype can do. It does not automatically make the same capability standard on other ships. Continuity & Canon explains how SWTOR evidence, compatible Legends material, interpretation, and StarForgeRP-created history fit together.
A reader’s knowledge of a vessel does not give a character its coordinates, credentials, concealed compartments, or technical secrets. Determine what the character learned through service, observation, records, or an established discovery.
Keep testimony, suspected faults, disputed provenance, and confirmed findings distinguishable. A recovered ship can remain only partly understood without predetermining what an investigation will uncover.
Droids & Automation — Shipboard assistance, technical duties, programming, memory, and individual droid history.
Communications, Data & Security — Transmissions, telemetry, protected records, and access to computer systems.
Tools, Industry & Specialist Equipment — Diagnostics, fabrication, lifting equipment, workshops, and recovery.
Cybernetics & Medical Technology — Medical facilities, emergency treatment, specialist care, and continuing support.
Weapons & Defense — Related armament, protective equipment, and their operating requirements.
Ancient, Rare & Experimental Technology — Recovered machinery and unusual systems whose provenance or capabilities require closer examination.