[Trick] Early Game +7% Mineral Boost - Page 24

I suspect this is caused by the use of battle.net. As everyone knows, no game is now played on "LAN latency" -- all commands you issue have a delay integrated so that, should you have a brief lagspike, your computer already knows what should happen over the next chunk of time. Since this delay would be applied when a command is issued, not executed, my guess is that workers who have just harvested issue such a command (it's not previously queued). By issuing it earlier, yourself, you can eat the delay when it's irrelevant, and have instant response as the queue is executed.

If I'm right, this would apply to any automatically-provided order. The problem is knowing which orders are complex, and which orders are simple but automatically provided. The biggest example in my mind is target selection. If your roach finishes blowing up one stalker, and starts looking for the next one, is that all part of one "attack" command? Or is a new attack command enqueued when the first enemy is eliminated? If the latter, you're losing DPS, and optimal combat micro becomes absurdly intensive (not only must you manually select all targets, you must do it one step ahead -- always having the next target queued up). This should be testable -- throw a unit against a few enemies, and time the kills, then do the same with each enemy queued up.

If this is the case, I can think of two fixes:

1) "Linked" commands. When you mine something, the return is enqueued at the same time, and linked to the mining action. If the mining is canceled so is the return. This would be an easy fix for workers, but to have every combat unit always have a secondary target queued up would be a pain.

2) Complex commands. "Harvest" has to include both gather and return. "Attack" has to include target selection, etc.

Can anyone think of other (potentially) automatically issued commands?