Interesting Timing Error

[blindzebra]

Originally Posted by Camron Rust

In A, B, and C, some time should have passed. The clock currently says 0.0. If you don't know how much extra time elapsed, you can't put anything back. It should either be 0.0 or something between 0.0 and 1.2. It can't be 1.2.

Care to support that by a rule?

Like I said, replace the 1.2 with 5 seconds and for whatever reason, there was never a count, you going to allow a team to lose a game because of a known timing error? I doubt it.