mobile

Vars
callTime	time spent in transit (deciseconds). Should not be lower then 10 seconds without editing the animation of the hyperspace ripples.
control_flags	All shuttle_control computers that share at least one control flag is able to link to this 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
prearrivalTime	delay after call time finishes for sound effects, explosions, etc.
rechargeTime	time spent after arrival before being able to launch again
shuttle_computer	Reference of the shuttle docker holding the mobile docking port
timer	used as a timer (if you want time left to complete move, use timeLeft proc)
Procs
beforeShuttleMove	Misc move procs
calculate_docking_port_information	Calculated and populates the information used for docking and some internal vars. This can also be used to calculate from shuttle_areas so that you can expand/shrink shuttles!
initiate_docking	This is the main proc. It instantly moves our mobile port to stationary port `new_dock`.
linkup	Called after the shuttle is loaded from template
preflight_check	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

Var Details

var
callTime
–

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

var
control_flags
–

All shuttle_control computers that share at least one control flag is able to link to this shuttle

var
ignitionTime
–

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

var
mode
–

current shuttle mode

var
prearrivalTime
–

delay after call time finishes for sound effects, explosions, etc.

var
rechargeTime
–

time spent after arrival before being able to launch again

var
shuttle_computer
– /obj/machinery/computer/camera_advanced/shuttle_docker

Reference of the shuttle docker holding the mobile docking port

var
timer
–

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

Proc Details

beforeShuttleMove
(/turf/newT, rotation, move_mode, /obj/docking_port/mobile/moving_dock)

Misc move procs

proc
calculate_docking_port_information
(/datum/map_template/shuttle/loading_from)

Calculated and populates the information used for docking and some internal vars. This can also be used to calculate from shuttle_areas so that you can expand/shrink shuttles!

Arguments:

loading_from - The template that the shuttle was loaded from, if not given we iterate shuttle_areas to calculate information instead

proc
initiate_docking
(/obj/docking_port/stationary/new_dock, movement_direction, force)

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

proc
linkup
(/datum/map_template/shuttle/template, /obj/docking_port/stationary/dock)

Called after the shuttle is loaded from template

proc
preflight_check
(/list/old_turfs, /list/new_turfs, /list/areas_to_move, rotation)

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

Hiding turfs if necessary

Unhiding turfs if necessary

mobile /obj/docking_port/mobile

Vars

Procs

Var Details

var callTime –

var control_flags –

var ignitionTime –

var mode –

var prearrivalTime –

var rechargeTime –

var shuttle_computer – /obj/machinery/computer/camera_advanced/shuttle_docker

var timer –