Woah, that sounds like things going out-of-sync, which is very strange as it almost sounds like a SC2 bug.
For debugging, I would suggest to break your triggers into parts (with waits between each), and print something on the screen before any operation you are about to perform. This should allow you to figure what's the last operation before going out of-sync.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Woah, that sounds like things going out-of-sync, which is very strange as it almost sounds like a SC2 bug.
For debugging, I would suggest to break your triggers into parts (with waits between each), and print something on the screen before any operation you are about to perform. This should allow you to figure what's the last operation before going out of-sync.