department_orders
Vars | |
| dep_groups | which groups this computer can order from |
|---|---|
| department_delivery_areas | where this computer expects deliveries to need to go, passed onto orders. it will see if the FIRST one exists, then try a fallback. if no fallbacks it throws an error |
| department_order | reference to the order we've made UNTIL it gets sent on the supply shuttle. this is so heads can cancel it |
| override_access | access required to override an order - this should be a head of staff for the department |
| req_one_access_group | A /datum/access_group path to pull access from on init. |
Procs | |
| finalize_department_order | signal when the supply shuttle begins to spawn orders. we forget the current order preventing it from being overridden (since it's already past the point of no return on undoing the order) |
Var Details
dep_groups
which groups this computer can order from
department_delivery_areas
where this computer expects deliveries to need to go, passed onto orders. it will see if the FIRST one exists, then try a fallback. if no fallbacks it throws an error
department_order
reference to the order we've made UNTIL it gets sent on the supply shuttle. this is so heads can cancel it
override_access
access required to override an order - this should be a head of staff for the department
req_one_access_group
A /datum/access_group path to pull access from on init.
Proc Details
finalize_department_order
signal when the supply shuttle begins to spawn orders. we forget the current order preventing it from being overridden (since it's already past the point of no return on undoing the order)