Shiptest 13 - Modules - TypesVar Details - Proc Details

mobile

Vars

assigned_transitThe transit dock assigned exclusively to this shuttle.
callTimetime spent in transit (deciseconds). Should not be lower then 10 seconds without editing the animation of the hyperspace ripples.
can_move_docking_portsif this shuttle can move docking ports other than the one it is docked at
current_shipThe linked overmap object, if there is one
docking_pointsList of all stationary docking ports that spawned on the ship roundstart, used for docking to other ships.
engine_listA list of all engines currently linked to the shuttle.
ignitionTimetime spent "starting the engines". Also rate limits how often we try to reserve transit space if its ever full of transiting shuttles.
modecurrent shuttle mode
movement_forceWhether or not you want your ship to knock people down, and also whether it will throw them several tiles upon launching.
port_directionrelative direction of the docking port from the front of the shuttle NORTH is towards front, EAST would be starboard side, WEST port, etc.
prearrivalTimetime spent after transit 'landing' before actually arriving
preferred_directionThe direction the shuttle prefers to travel in, ie what direction the animation will cause it to appear to be traveling in
rechargeTimetime spent after arrival before being able to begin ignition
ripplesList of all the ripple effects made at this shuttle's future docking location.
shuttle_areasAll currently linked areas that will be moved when the shuttle (un)docks
spawn_pointsList of spawn points on the ship
timerused as a timer (if you want time left to complete move, use timeLeft proc)

Procs

get_status_text_tguiGets shuttle location status in a form of string for tgui interfaces
initiate_dockingThis is the main proc. It instantly moves our mobile port to stationary port new_dock.
kill_atmos_infosBoth lists are associative with a turf:bitflag structure. (new_turfs bitflag space unused currently) The bitflag contains the data for what inhabitants of that coordinate should be moved to the new location The bitflags can be found in __DEFINES/shuttles.dm

Var Details

assigned_transit

The transit dock assigned exclusively to this shuttle.

callTime

time spent in transit (deciseconds). Should not be lower then 10 seconds without editing the animation of the hyperspace ripples.

can_move_docking_ports

if this shuttle can move docking ports other than the one it is docked at

current_ship

The linked overmap object, if there is one

docking_points

List of all stationary docking ports that spawned on the ship roundstart, used for docking to other ships.

engine_list

A list of all engines currently linked to the shuttle.

ignitionTime

time spent "starting the engines". Also rate limits how often we try to reserve transit space if its ever full of transiting shuttles.

mode

current shuttle mode

movement_force

Whether or not you want your ship to knock people down, and also whether it will throw them several tiles upon launching.

port_direction

relative direction of the docking port from the front of the shuttle NORTH is towards front, EAST would be starboard side, WEST port, etc.

prearrivalTime

time spent after transit 'landing' before actually arriving

preferred_direction

The direction the shuttle prefers to travel in, ie what direction the animation will cause it to appear to be traveling in

rechargeTime

time spent after arrival before being able to begin ignition

ripples

List of all the ripple effects made at this shuttle's future docking location.

shuttle_areas

All currently linked areas that will be moved when the shuttle (un)docks

spawn_points

List of spawn points on the ship

timer

used as a timer (if you want time left to complete move, use timeLeft proc)

Proc Details

get_status_text_tgui

Gets shuttle location status in a form of string for tgui interfaces

initiate_docking

This is the main proc. It instantly moves our mobile port to stationary port new_dock.

kill_atmos_infos

Both lists are associative with a turf:bitflag structure. (new_turfs bitflag space unused currently) The bitflag contains the data for what inhabitants of that coordinate should be moved to the new location The bitflags can be found in __DEFINES/shuttles.dm