byond - Modules - TypesVar Details - Proc Details

stacking

Vars

consumed_on_fadeoutIf status should be removed due to being under one stack
consumed_on_thresholdIf status should be removed once threshold is crossed
delay_before_decayDeciseconds until ticks start occuring, which removes stacks (first stack will be removed at this time plus tick_interval)
max_stacksStacks cannot exceed this amount
overlay_stateStates in .dmi must be given a name followed by a number which corresponds to a number of stacks. put the state name without the number in these state vars
stack_decayHow many stacks are lost per tick (decay trigger)
stack_thresholdSpecial effects trigger when stacks reach this amount
stacksHow many stacks are accumulated, also is # of stacks that target will have when first applied
threshold_crossedSet to true once the threshold is crossed, false once it falls back below
tick_intervalDeciseconds between decays once decay starts
underlay_stateThe number is concatonated onto the string based on the number of stacks to get the correct state name

Procs

fadeout_effectRuns if status is deleted due to being under one stack
stack_decay_effectRuns every time tick() causes stacks to decay
stacks_consumed_effectRuns if status is deleted due to threshold being crossed
threshold_cross_effectWhat happens when threshold is crossed

Var Details

consumed_on_fadeout

If status should be removed due to being under one stack

consumed_on_threshold

If status should be removed once threshold is crossed

delay_before_decay

Deciseconds until ticks start occuring, which removes stacks (first stack will be removed at this time plus tick_interval)

max_stacks

Stacks cannot exceed this amount

overlay_state

States in .dmi must be given a name followed by a number which corresponds to a number of stacks. put the state name without the number in these state vars

stack_decay

How many stacks are lost per tick (decay trigger)

stack_threshold

Special effects trigger when stacks reach this amount

stacks

How many stacks are accumulated, also is # of stacks that target will have when first applied

threshold_crossed

Set to true once the threshold is crossed, false once it falls back below

tick_interval

Deciseconds between decays once decay starts

underlay_state

The number is concatonated onto the string based on the number of stacks to get the correct state name

Proc Details

fadeout_effect

Runs if status is deleted due to being under one stack

stack_decay_effect

Runs every time tick() causes stacks to decay

stacks_consumed_effect

Runs if status is deleted due to threshold being crossed

threshold_cross_effect

What happens when threshold is crossed