Security systems and procedures help a starship protect itself from external and internal threats. To stimulate the level of security on board Starfleet vessels, each ship has a security rating.
Security onboard Starfleet’s
vessels also vary on the type of weaponry and security personnel assigned to the
vessel. Where it be standard Starfleet security that are assigned to most
Starfleet vessels, Federated Marines, or Special Forces units such as the
‘Rogue’ Wing META units, Starfleet Rangers, 3rd Andorian Battalion,
Rigellian Roughnecks, or Rapid Response Teams, each have their own skills and
abilities that enhance a ships overall defenses. (This is not represented in the
game system. Equipment for standard and advanced security personnel are provided
in the ‘Equipment’ section of this tech brief.)
Almost all Starfleet vessels come equipped with an anti-intruder system designed to disable hostile forces, which invade the ship. This system allows the commanding officers (or other officers of appropriate rank) to order some or all parts of the ship flooded with anesthezine or neurozine gas, which renders all known humanoids unconscious in seconds.
Starfleet vessels have the ability to generate force fields, also known as containment fields or security fields, anywhere in the ship for protective or defensive purposes. For example, force fields are used to seal off Engineering in the event that the warp engine accidentally starts venting dangerous gases, to keep prisoners in the brig, to seal off sickbay to prevent a contagious disease from spreading to the rest of the crew, or to block off a corridor to prevent an invader from reaching a certain area.
A ship can generate a force field anywhere within its hull; although normally kept as small as possible to help maintain field integrity, they can be large enough to, for example, seal off the entire bridge. Many newer vessels are equipped with multi-phasic and more advanced types of internal force field grids, to increase the integrity and strength of force fields used. Multi-phasic force fields can be used to protect the warp core itself to increase the protection around the core and reinforce structural integrity of the materials used in its casing, or seal off the entire vessel bulkhead by bulkhead during crisis situations and only allow passage of Starfleet personnel through the field via their commbadge interplexing beacon outputs, that the computer registers and allows the person to pass through the ship in red alert or general quarters situations.
Working off the existing holo-emitters installed on every deck (restricted to vessels like the Prometheus, Frontier, and other newer classes of starships) to allow for holographic technology to be used as a defensive measure. They can create false corridors, to essentially confuse invading forces into thinking they’re traversing the ship when they are really walking in circles or in place, they can also create holo-‘defenders’ of any type the programmer desires; from Klingon Warriors, to Roman Legionaries, to Aldeberan Eels, to the horsemen of the apocalypse. This system acts as a potent defensive measure if hostile forces are boarding a vessel.
This device functions identically to a standard transport inhibitor (see equipment section or ‘The Price of Freedom’ pg. 108), but covers a much wider area—a sphere of up to 100 meters radius. Additionally, the military transport inhibitors emits a stronger field than a non-military model, and these are normally equipped to military units during times of crisis or war; isolinear tags, pattern enhancers, and skeletal locks with not work through it.
Aboard a starship, each military grade transport inhibitor are positioned in strategic positions in the hull of the starship with independent power supply to activate in the event of total shield and internal force field collapse. On the ground, military transport inhibitors have tripod bases with independent rotating joints and adhesive pads so that troops can place them on just about any surface (even on a vertical rock face or hanging from a ceiling). The tripod legs also fold down to form a spike that the user can thrust into the ground for better stability, or use as an impromptu weapon.
One thing that can be difficult to secure is communications. A transmission can be overhead by anyone with a receiver tuned to the proper band, making communications vulnerable. A number of technological solutions have developed to keep communications private and prevent eavesdropping, but for every technique of covert communication, there is a way around it.
The simplest means of keeping a communication secret is by using some sort of pre-agreed code essentially an artificial language that conceals the true information of the message. Starfleet encodes high-priority messages and has coded communications channels for (relatively) secure communications through subspace. Species like the Ferengi routinely encode all their communications. In the age of isolinear computer processors, codes can be very complex. Fortunately, with the help of the same computers (and universal translation software) it is still possible to break most codes, given time.
Encryption is a complex mathematical algorithm that scrambles the information content of a transmission. The receiver can reconstruct the message using a special mathematical sequence called an encryption key. Encryption is handled by computers, which are capable of performing the massive calculations required. Complex encryption sequences are very difficult to break, requiring considerable time and computing power.
A common means of covert communication is "piggybacking" a transmission within another, innocuous signal to prevent it from being noticed. This requires a carrier signal of the proper strength (like a subspace transmission) going in approximately the same direction that the message must travel, and detectable by the intended recipient.
One simple means of piggybacking a message is by sending an extremely simple signal, like Morse code or another repeating pattern. This can often be disguised as background noise or static.
With 24th century computer technology, it's a simple matter to modify the sounds and images transmitted in communications. A Shipboard Systems (Communications) Skill Test allows a character to modify a communication, altering its visual and audio components to present whatever image the character wishes. The Difficult of the test is based on the complexity of the change desired. Making the captain look like a Klingon, standing on a Klingon bridge, for example, might be Moderate, while making the captain appear as a Tholian or a Sheliak, speaking in their native language, is Challenging at least.
A communications filter changes the way the receiver sees and hears communications sent from the ship. For example, a filter might make the crew look like Cardassians, standing on the bridge of a Cardassian ship. This is a useful supplement to the other forms of deception. If a patrol ship's long range sensors tell them they are tracking a Cardassian freighter, and their communication with the ship shows a Cardassian crew on board, they're not likely to suspect that the vessel is really a Starfleet Nebula-class starship.
The center of nearly every security system in the 24th century is a computer. Control the computer, and you control the security system. The computer is the "brain" of a starship or installation, making it one of the parts most vulnerable to subversion and attack. Since the computer controls many functions automatically, completely outside the control of its crew, damage or sabotage of a ship's computer can sometimes leave it helpless.
Starship computers communicate with the outside world in a variety of different ways. They use the ship's external sensors to gather information for navigation, to avoid hazards to the ship and crew, and to provide the crew with useful information about their surroundings. They use internal sensors to monitor the locations of crewmembers, route communications, maintain environmental conditions, and dozens of other functions. Communications (both internal and external) are routed through the ship's computer, and the computer is in regular contact with outside sources of information like time-base beacons, surveillance satellites, probes, and similar objects. Computers on board stations, or planetside, function in much the same way.
Example: Ensign Roberts is trying to gain access to the computer of a Federation ship under the control of hijackers to gain his ship a tactical advantage. The Narrator sets the total Test Result required at 30 (since Ensign Roberts is quite familiar with Starfleet computer systems). Roberts makes his Computer Skill Test, scoring a Test Result of 8 on the first turn. The Narrator makes a test for the enemy. The hijacker at the bridge tactical station hasn't noticed the intrusion, so far, so good.
Roberts makes his second test, while the Captain is talking to the leader of the hijackers, stalling for time. This time he gets a Test Result of 6, he's almost halfway there, when the hijackers notice him. They break off communications and open fire. "Keep at it, Ensign!" the captain says. Roberts makes his third test. This time, the hijackers are attempting to block him. Roberts gets a Test Result of 6 again. The Narrator rolls a total for the hijackers, getting a 4. Fortunately, they're not too computer savvy. Still, Roberts has a net gain of only 2 points on his cumulative total this turn, bringing it up to 16. It's in doubt whether or not he'll be able to gain access to the other ship's computer in time to do any good.
The above rules assume the character does not have authorized access to the computer system. In some cases, however, the character may have access, in which case only a Routine Computer (Data Alteration or Programming) Skill Test is required to carry out the character's commands. This was the case in the Next Generation episode "Peak Performance," where Lt. Worf accessed the Enterprise's computer from the U.S.S. Hathaway and fed it false sensor data. When Data changed the security access codes, he blocked Worf's access.
Part of an operation to penetrate a location's security may consist of getting the proper access codes for the location's computer, circumventing its security measures. This is not as simple a matter as finding out a password or a sequence of numbers. Computers in the 24th century are quite intelligent, and generally have voice-recognition capabilities as well, so a password or code may need to be delivered by a particular voice as well. Voice synthesizers may be able to get around this problem. If the computer requires an additional verification like a DNA scan further counter-measures are required.
Starfleet gives each starship its own prefix code, providing outside access to the ship's computer to other Starfleet personnel. In the event of an emergency, or a takeover of the ship, another Starfleet vessel can use the prefix code to override the ship's computer system and take command of its key functions. In effect, a character on the other ship can operate the ship's computer as if it were an extension of his own ship's computer. Clever and knowledgeable hijackers will change a starship's prefix code as soon as possible to prevent other Starfleet vessels from simply overriding their command systems and, say, shutting down their shields or warp drive.
Codes can also be used to limit computer access to certain authorized individuals or locations. This is routinely done on board Starfleet vessels and installations; computer users must give an authorization code (by voice, so their voiceprint can also be scanned) in order to access certain restricted information and functions. For example, only the captain and the first officer of a starship can access the ship's auto-destruct system, and only in tandem. The more limited the system's access, the harder it is to overcome its security protocols.
Authorized characters can also oftentimes change the available access. For example, the captain of a Starfleet ship has the authority to localize command functions, preventing the ship's computer from accepting commands from any locations other than the one's specified. The captain can also lock out any or all of the computer's functions and place a code that unlocks them into the system. Until an authorized person inputs the code, those computer functions are no longer available.
Finally, as an emergency measure, the ranking command officer can lock out all of a starship or starbase's command functions, preventing anyone from accessing the computer until those functions are restored. This is done to prevent an enemy for seizing control of a boarded ship, allowing the crew the opportunity to take counter-measures.
Locks keep things that open closed-from doors to boxes. A lock can be a simple mechanical affair (easy to overcome with the right tools) or a more sophisticated electronic lock. Electronic locks usually have additional security features built into them, such as identifying their owner by fingerprints, retinal print, voice, DNA scan, galvanic skin response, or similar criteria.
Lock Difficulty Table
|Type of Lock||Difficulty||
Test Result Total Required
30 or more
|No proper tools||+4||
Starfleet uses a large number of security procedures and protocols to safeguard the lives of its personnel, and to prevent valuable Starfleet resources from falling into the wrong hands. Starfleet's complete security regulations take up a book many times the size of this one, covering everything from proper handling of prisoners to emergency situations.
It would be impossible to cover every aspect of security operations in complete detail. This section provides an overview of the most basic and vital security operations, allowing the Narrator and the players to extrapolate from it and information from the Star Trek shows.
One of the primary duties of the Security department on board a starship or starbase is safeguarding vital areas that may be vulnerable to theft or sabotage, or that might draw intruders. Such areas include the bridge, main engineering, the central computer core, cargo bays containing valuable goods, the shuttlebays, and the brig. When the ship or station is not on alert, guards are routinely posted at security stations on the decks located near these vital areas, able to monitor the security scanners and respond quickly if there is a need.
For a yellow alert, security personnel are placed on guard at vital points throughout the ship. They may be given special orders regarding access to those facilities (such as allowing no one but the Captain and First Officer access). The security guards allow access to authorized crewmembers unless ordered otherwise. The Captain, First Officer, or Security Chief can also give certain crewmembers access privileges, as needed.
Under red alert, security guards are posted on all decks, as well as vital areas of the ship. If an intruder alert is sounded, security personnel guard all turbolifts and airlocks, and begin sweeping the ship for signs of intruders. Information is relayed back to the main computer and the Security Chief.
Standard procedure calls for at least one security guard on duty in the transporter room when unknown or potentially dangerous individuals transport on board. The transporter chief can hold such individuals in stasis in the pattern buffer if necessary to await the arrival of security, and transporter scanners automatically detect any dangerous weapons or other devices, and can render them inoperative before the subject rematerializes, making security's job easier.
One of the prime duties of Security is safeguarding the commanding officer of a starship or station. The captain is considered a vital element of the ship, and treated accordingly. The captain should have a security escort at all times in red alert situations, and when beaming down into any situation that might become dangerous. The Security Chief and/or Operations Officer helps to safeguard the captain while on the bridge, but additional security personnel should be present if trouble is expected.
Part of safeguarding the captain involves performing security sweeps of areas before the captain enters or beams into them. Security personnel check for any potential hazards and ensure they are within reasonable limits before the captain arrives. The captain can, of course, override standard security procedures in these matters, but it is not recommended.
Security personnel form a vital part of Away Team Missions and every away team is well-advised to have at least one security officer, more if the Away Mission is expected to encounter trouble (particularly armed resistance). In some cases, away teams may be made up entirely of Security (and Command) personnel.
While on an Away Mission, the duties of the Security personnel include: 1) Remaining alert for any signs of danger to the crew or mission; 2) Safeguarding the lives of all away team members, particularly senior officers; 3) Gathering tactical and strategic information regarding any possible threats; and 4) Taking necessary action to ensure the first three priorities, including the use of force, but only as a last resort.
While all Starfleet personnel on Away Missions are expected to remain alert, it is the security officer's duty to look out for potential threats to the Away Team. This includes the use of tricorder scans for hazards (both natural and artificial) and "reading" the reactions of any life-forms the crew may encounter. The security officer should make recommendations to the commanding officer of the Away Team with regards to appropriate security precautions.
It is important to note that Starfleet security officers are expected to take a defensive posture with regard to possible threats. Stunning (much less injuring) native life-forms "simply because they might pose a threat" is against Starfleet regulations. A strategic withdrawal is normally the most prudent response in a dangerous situation, followed by neutralizing the danger as quickly as possible, if a withdrawal is not an option.
Security "extras" in the Star Trek television shows get regularly phasered, stabbed, blow up, disintegrated, frozen solid, and eaten by alien life-forms with such regularity that it's become something of a joke among Star Trek fans. Called "Red Shirt Syndrome" (for the red shirts security personnel wore on the original series), it leads players to believe that any security NPC who accompanies them is surely a dead man.
In some cases, you can use this to your advantage, killing off non-player security characters for the same reasons Star Trek writers have: mainly to show just how dangerous a particular threat is, or to show off its unique (and probably unpleasant) means of killing people. Red-shirts also make good characters to get turned into sludge-rats (or styrofoam polygons) by omnipotent alien entities.
You can also play players' red-shirt expectations against them. For example, a non-player character who's not a security officer might suffer an unfortunate fate. Science officers are a good second choice, since they're usually investigating phenomena that can turn deadly without even a moment's warning. In certain situations, you can also throw players for a loop by having the malevolent alien choose one of their characters to kill first! Things should ideally turn out to be an illusion of some sort (or something else should be able to bring the character back to life). But putting the players in the role of the "red shirts" sometimes can lend a feeling of tension and fear to the game, and make the players a bit less likely to treat NPC security officers like cannon fodder.
There are occasions when a Starfleet crew may find itself with prisoners: criminals they have apprehended, captured attackers, or even unknown aliens. In general, Starfleet crews are authorized to keep such individuals imprisoned until they can be turned over to the proper authorities, either of the planet or civilization that has jurisdiction, or to Federation authorities at a Starbase.
Each starship or station is generally equipped with a brig to hold prisoners. The brig consists of one or more cells equipped with force fields and a security station. On board larger ships and space stations brigs are capable of holding a number of prisoners. Smaller ships may only be able to hold a handful, while the smallest ships may not have a brig at all. Crews may resort to using guest- or crew-quarters as makeshift cells by locking the door and posting guards (perhaps even reinforcing the door with a force field). Most brigs use force fields to prevent any chance of the prisoner escaping via transporter.
A starship crew is expected to turn any prisoners over to the proper authorities as soon as reasonably possible. The captain, of course, is the judge of what is "reasonable" in these situations. If the ship is already engaged in a mission, the prisoners may be held until that mission is complete and the ship has an opportunity to deal with them. More delicate political and diplomatic situations may require the crew to deal with their prisoners immediately.
Starfleet regulations require that prisoners be treated well, and that all of their life-support needs be met. In the case of non-Federation citizens, the crew should make every effort to contact the proper authorities of the prisoner's home world, although prisoners accused of crimes against Federation personnel or property should be held over while Federation authorities discuss matters of extradition with the prisoner's home civilization.
One of the prime security measures is the use of sensors, devices able to pick up and monitor certain types of information, sending out an alarm or activating other security measures when they detect intruders.
Sensor technology in the 24th century is capable of picking up nearly every type of energy in the electromagnetic spectrum (and some exotic energies outside of it), along with biological matter, and even specific DNA sequences. Most sensor packages consist of multiple types of sensors, each detecting something different. For example, a sensor suite might scan for electromagnetic disturbances, ionization traces (indicative of a transporter beam), infrared signatures for body heat and working machinery, and so forth.
Visual sensors transmit a visual image of the area they are set to scan, similar to old-fashioned security cameras. They can be crudely overcome by blacking them out with some opaque material (paint, for example). A more sophisticated option is to install a device that feeds the sensor's data back into it, creating a "loop" and effectively blinding the sensor.
Motion sensors detect molecular displacement traces created by moving objects. The sensors generally have a "threshold" of movement they are designed to detect. If the threshold is set too low, the random movement of air molecules can be enough to set the sensors off. Low-grade motion sensors can be evaded by moving very slowly (a Challenging Stealth (Stealthy Movement) Skill Test). Otherwise, it easiest to defeat motion sensors by overcoming the computer that controls them (see Computer Systems).
Infrared (or IR) sensors pick up infrared radiation or heat sources, including the body heat of warm-blooded lifeforms. Characters can overcome them by wearing special anti-IR clothing to masks their heat signature, or by programming a device like a tricorder to emit an IR scattering field (a Challenging Personal Equipment (Tricorder) Skill Test).
These sensors detect electromagnetic disturbances of various kinds, including the operation of certain devices, the use of energy weapons like phasers, and so forth. They can be avoided by not using any high-energy devices, although this can make overcoming other sensors more difficult. Characters can also use technology to shield electromagnetic impulses, preventing them from being picked up by the sensors.
These sensors are fairly rare, they detect disturbances in the subspace field, such as those caused by warp nacelles or a transporter beam. They can detect anyone beaming in or out of an area, and provide information to help track the transporter beam's source. Subspace sensors are difficult to overcome, but a Difficult Shipboard Systems (Transporter) Skill Test can slip a transporter beam in "between" sensor cycles.
Starships rely heavily on the data provided by their various sensors for tactical and navigational decisions. Without its sensors, a ship is effectively blind and deaf, unable to detect anything except by having someone go to a window and look out. Therefore, many tactics in starship combat are based on fooling or shutting down an opponent's sensor systems.
There are a number of ways of evading sensor scans. The most basic is using some form of matter or energy as "cover" to interfere with the sensors' operation. Normally, the tactical officer makes a Moderate (7) Shipboard Systems (Sensors) Skill Test to obtain a sensor lock on an opposing ship. Interference increases the Difficulty of this Test, making it harder to lock on to the opposing ship.
Examples of interference include things like the following:
The Narrator should decide how much any given type of interference increase the Difficulty of Shipboard Systems (Sensor) Tests, at least by one level of Difficulty, sometimes more. In effect, the interference serves as a kind of natural "cloaking device" for the ship, with a rating determined by the Narrator.
The main drawback of most methods for interfering with an opponent's sensors is they interfere with the sensors of both ships, leaving them both stumbling around, effectively blinded. Fighting in a nebula is like two combatants fighting in a darkened room. In some cases, character with more experience dealing with sensor interference may still find it to their advantage, and it's preferable to being destroyed by a superior vessel.
In some cases it is possible to not only block an opponent's sensors but to fool them entirely, feeding them false or misleading information. Usually, this involves gaining access to the opposing ship's computer system (see Computer Systems, above) and sending false input codes to the sensors. This allows the character to make the sensors "believe" just about anything; enemy ships where there are none, system failures or problems that don't really exist, and so forth. Characters on the opposing ship realize the image is false when it doesn't live up to their expectations (the enemy ships don't open fire, the failed system continues to function, and so forth). A crewmember can also realize the computer's error with a Moderate (7) Shipboard Systems (Sensors) Test.
There are also other, somewhat cruder, means of sending false signals to an enemy ship's sensors. One is to modify the signals sent out by your own ship, giving the enemy false impressions about it. This is usually accomplished by modulating the shields, altering transponder frequencies and signals, and modifying warp field signature. A Moderate (7) Test using the appropriate Engineering skill can modify one of the ship's systems to send a simple false signal, like making the warp signature of a Federation ship appear Klingon, for example. A Challenging (10) Test can significantly alter the ship's signals, making a Federation starship appear as a Cardassian cargo-hauler to all but visual sensors. A Difficult (13) Test even provides some screening against visual sensors, but cannot fool them entirely. Still, combined with some Fast Talk and a communications filter (see Communications), this can go a long way.
One of the most difficult security and surveillance measures to avoid is the use of psionic abilities, particularly telepathic skills, in detecting criminal or subversive thoughts. Telepathy is not commonly used in espionage or security work. Federation law forbids telepathic scans of unwilling subjects, although Federation telepaths have sometimes detected criminal plots purely by chance, picking up on the surface thoughts of the criminals before they carried out their scheme. Ambassador Lwaxana Troi of Betazed once foiled a plan by the Antedeans to bomb the Pacifica diplomatic conference in this way.
Since there is no known technological means of blocking telepathy there are only two methods of evading telepathic security. The first is training in the Mind Shield skill (ST:TNG, p. 99), increasing resistance to telepathic scans and allowing the user to keep his surface thoughts well hidden. Since telepathic scans are used only rarely in security work, this usually suffices to protect the character from casual detection.
The second option is to control the amount of information known to the people involved in a criminal plot. If an underling doesn't know something, he can't reveal it, even under a deep telepathic scan like a mind meld. Espionage organizations like the Tal Shiar and the Obsidian Order have also been known to give their agents suicide devices, allowing them to kill themselves before they can be interrogated.
Finally, some species, like the Ferengi and the Breen, are naturally immune to telepathic detection. Species like the Betazoids that rely on telepathy in their dealings with other races are often uncomfortable around such lifeforms.
These game systems focus on the tactical, combat action in a Star Trek game. Although the Federation and its representatives do their best to avoid violent confrontation whenever possible, it is sometimes necessary, and Starfleet ensures its personnel have the training to come out on the winning side of such conflicts.
Ranged combat takes place using weapons that inflict damage at a distance, from muscle-powered primitive weapons like bows and spears to firearms to modern phasers. Most ranged combat in the 24th century uses energy weapons like phasers or disruptors, although there are circumstances where a Crew might be forced to use more primitive weapons, or might encounter opponents using them (particularly on less technologically-advanced worlds).
Many ranged weapons (firearms and energy weapons) can fire multiple shots with a single pull of the trigger, increasing the chance of damaging a target, or allowing the character to hit multiple targets at once. When a character firing an autofire weapon makes an Attack Test, every +1 over the required Difficulty indicates an additional shot from the weapon has hit the target, doing the weapon's normal damage. Apply Resistance (and armor) separately against each shot before determining what damage the target takes. Alternately, each +1 indicates an additional target is hit, provided they are within 2 meters of the previous target. Characters can "target" empty space if desired, in order to "walk" their autofire to another target. This wastes a shot, but otherwise incurs no penalty.
Example: Captain Picard is in the Dixon Hill program on the holodeck when a pair of Borg drones come looking for him. Grabbing a holographic Tommy gun from a nearby gangster, Picard fills the air full of lead, firing on full auto to take down the drones. The Narrator says the drones are at short range for the gun, making the Difficulty of the attack Routine (4). Picard's player makes his Projectile Weapon (Submachine Gun) Skill Test, getting a Test Result of 7, or 3 over the required Difficulty. He decides to hit each Borg with two attacks. The Borg are not prepared for the unexpected use of a projectile weapon, and they take considerable damage.
The drawback of autofire is that it penalizes the character's next attack with the same weapon. Firearms suffer from recoil when fired on automatic; the kickback from the explosion that propels the projectile pushes the gun's muzzle back and upward. Energy weapons suffer from overheating when fired on automatic, making them more difficult to handle. The Difficulty for an attack with the weapon on the following round is increased by one level. This continues until the character does not fire the weapon on automatic for at least one round.
Two or more characters can choose to "concentrate" the fire from their weapons on the same target at the same time. This increases their chances of overcoming the target's Resistance and damaging it.
Example: The Enterprise Away Team is facing off against an automated weapon in the ruins of Minos. The weapon has a deflector shield that's resisting their phaser fire, so the team concentrates their fire, hoping to overload and collapse the shield. Lt. Yar makes her Planetary Tactics (Small-Unit) Skill Test to offset the penalty for the concentrated fire attack while Cmdr. Riker and Data remain under cover. When Tasha shouts "Now!" all three Starfleet officers fire at once, focusing on the same spot. The Narrator adds the damage from all their attacks together before subtracting the Resistance of the weapon's shield. They overwhelm the shield and the weapon is destroyed.
Nearly all starships and space stations in the known galaxy have some form of artificial gravity. However, there are occasions when characters may find themselves operating under zero-gravity conditions, either on the hull of a ship, in the depths of space, or in the event of a failure of their ship's graviton generators. Security officers trained in zero-G combat operations may even deliberately sabotage the gravity fields on board a starship or station to give them a tactic advantage.
Movement in zero-G is usually limited to no more than a walk if the character is wearing magnetic boots. Characters moving freely can jump a distance equal to their Strength and continue moving at the same velocity each round until something halts their momentum.