ShadowTek
New Member
- Reaction score
- 23
I have noticed that if you defeat or victory a player that has left the game, then there is sometimes a loss of unit control that results for some players immediately after the defeat/victory action for their currently selected units.
The loss of control seems to only affect any currently selected units. You can see the unit's UI, and you can click around on the screen as if you are successfully giving commands, but the unit that you have selected will not respond to any of the commands.
The only way to break out from this "stuck" condition is if you select another unit, and then reselect the previous unit. Everything behaves normally after that.
It can really suck if you end up losing units because of this, especially in a hero type game. Some players never even figure out what the problem is and just leave the game out of frustration.
I did a search a while back to see if I could find any information about this problem. I do remember finding a forum post that confirmed that this was once a problem with a previous version of WC, but the problem was claimed to have been resolved with a following patch.
So does this mean that the original problem was never completely solved, or does this particular problem have a different cause?
The loss of control seems to only affect any currently selected units. You can see the unit's UI, and you can click around on the screen as if you are successfully giving commands, but the unit that you have selected will not respond to any of the commands.
The only way to break out from this "stuck" condition is if you select another unit, and then reselect the previous unit. Everything behaves normally after that.
It can really suck if you end up losing units because of this, especially in a hero type game. Some players never even figure out what the problem is and just leave the game out of frustration.
I did a search a while back to see if I could find any information about this problem. I do remember finding a forum post that confirmed that this was once a problem with a previous version of WC, but the problem was claimed to have been resolved with a following patch.
So does this mean that the original problem was never completely solved, or does this particular problem have a different cause?