Hi Justin
Each state has a state timer. The timer begins when the machine enters a state, and generates a 'Tup' event when the defined interval ends IF you are still in the same state.
In the OneState example state machine, 'Timer' refers to the state timer, and '1' refers to its duration.
In the interest of efficiency (to reduce the dead-time between trials by a few ms when state machines are large), the state machine assembler's AddState function does not use a "parse args" scheme - so all of the valid argument/value pairs ('Name', 'Timer', 'StateChangeConditions' and 'OutputActions') must be given for each state, even if they are not used.
Global timers are entirely different from the 'Timer' you see in each state definition. They are not attached to individual states, and are not required to run a state machine. This link should help clarify their use:
https://sanworks.github.io/Bpod_Wiki/function-reference/state-machine-creation/#setglobaltimer
Also, see the global timer examples in here:
https://github.com/sanworks/Bpod/tree/beta/Examples/State%20Machines
I hope this helps!