You seem to be misunderstanding the schedule used in it.
it's pushing 24 commandToServer instructions to the network queue on every single frame
Torque does not flush out data this quickly, thus after a while it
will overflow
secondly, since it's a queue, you won't be able to do anything else either