Timer Blocks retain Start commands while switched OFF

Manuel Koch shared this bug 10 hours ago
Submitted

Platform: PC/Steam

Category: Timer Blocks

Summary

Timer Blocks appear to retain incoming Start commands even while switched OFF.

When the affected Timer Block is switched ON again, it executes the previously received command, despite the original trigger having already occurred and the originating Timer Block no longer being active.

This behaviour can cause unexpected timer executions and makes it difficult to reliably coordinate multiple Timer Blocks.

Setup

Three Timer Blocks are used:

  • Timer 1: Main trigger.
  • Timer 2: Executes sequence A.
  • Timer 3: Executes sequence B.

Both Timer 2 and Timer 3 have a 2-second countdown configured.

Initially, Timer 2 is ON and Timer 3 is OFF.

Timer configurations

Timer 1:

  • Start Timer 2.
  • Start Timer 3.

Timer 2:

  • Execute its assigned actions.
  • Switch Timer 3 ON.
  • Switch Timer 2 OFF.

Timer 3:

  • Execute its assigned actions.
  • Switch Timer 2 ON.
  • Switch Timer 3 OFF.

Steps to reproduce

  1. Trigger Timer 1.
  2. Timer 1 sends a Start command to both Timer 2 and Timer 3.
  3. Timer 2 starts its 2-second countdown.
  4. Timer 3 remains switched OFF.
  5. Timer 2 finishes its sequence, switches Timer 3 ON and switches itself OFF.
  6. Timer 3 unexpectedly starts its countdown, even though it was switched OFF when Timer 1 issued the original Start command.
  7. Timer 3 executes its sequence normally.
  8. Timer 3 switches Timer 2 ON and itself OFF.
  9. Timer 2 remains idle because its original Start command has already been consumed.

Expected behaviour

A Timer Block switched OFF should ignore incoming commands or discard pending commands.

When switched ON again, it should only react to new commands received after being re-enabled.

In this example, Timer 3 should remain idle after Timer 2 switches it ON.

Actual behaviour

Timer 3 appears to retain the Start command sent by Timer 1 while switched OFF.

When Timer 2 subsequently switches Timer 3 ON, the previously received command is executed, and Timer 3 starts its countdown.

Switching Timer 1 OFF after the initial trigger does not prevent this behaviour, as the command has apparently already been sent.

Interestingly, Timer 2 does not repeat its original sequence when it is switched ON again by Timer 3. Its original Start command appears to have already been consumed.

Additional testing and confirmation

The following tests were performed:

  • All mods were removed. The behaviour persists.
  • Both Start and Trigger Now produce the same behaviour.
  • Switching Timer 1 OFF after the initial trigger does not prevent Timer 3 from executing.
  • Removing the 'Start Timer 3' action from Timer 1 completely prevents the unexpected activation. All other configurations and actions remain unchanged.

The last test confirms that the unexpected activation originates from Timer 1's original Start command.

Timer 3 therefore appears to retain and execute a command received while switched OFF, rather than ignoring or discarding it.

(!!) Workaround (!!)

Adding an explicit 'Timer 3 → Stop' action to Timer 2 before switching Timer 3 ON prevents the unexpected execution.

This suggests that the 'Stop' command also get registrated while Timer Blocks are off and clears the pending execution.

Suspected cause

Timer Blocks may retain incoming commands while switched OFF and process them when switched ON again.

Whether this is intentional behaviour or a bug in the handling of pending timer commands is unclear.

Expected fix

Switching a Timer Block OFF should prevent incoming trigger commands.

A switched-off Timer Block should only react to new commands received after it has been re-enabled.

Replies (1)

photo
1

making the start countdown reset when turning off could ruin a lot of people's builds logics so i would vote for that to not to be changed. that being said, just run an order to stop countdown when turning them off or on

Leave a Comment
 
Attach a file