- There's an extra signal sent on wrapping around in initiative that
  breaks the logic for when to tick because both new and old initiative
  numbers are 0
- The logic is still faulty if there are duplicate initiative numbers,
  but this at least replicates what seems to be the intended original
  behavior.

- There seems to have been a mistake translating it from the original,
  which always caused a 0->0 update message, rather than an N->0 update
  message on wrapping around (and thus no N->0 message was sent before
  the 0->MAX message, causing some intervals to be skipped).
- There probably shouldn't be an N->0 message when N is already <=0 due
  to actual rolled initiatives being that low.

- Clarify relation to initiative signals, and generalize the avoidance
  of 'degenerate' messages, although they shouldn't occur anymore.
- Made the intervals mentioned in the comments no longer backwards.