alex3337
11-27-2009, 12:38
I'm not sure if this is a suggestion, a bug, or a request ...
In the final mission of my new Aliens campaign I want to use "Ambush" blips. They way I'm doing it is having alien entry points that will be active for a single round. They show up, a blip comes through, and then it closes again. You never know where they may show up ...
The lurking rule still applies: a blip has to wait 1 turn to come out of such entry if there's a soldier less than 6 squares away from it.
Thats' where the problem appears: the new entry was announced, but you never get a warning about the lurking blip, and it does not even show on the scanner because the entry is no longer there. However, the aliens will "appear" from it just fine ...
That's nastier than what I wanted it to be. At least, you should get a warning, and a solid triangle on the scanner, so that you can move away from it, or set OW, or pray louder ...
My preferred fix would be for the lurking blip to show up on the scanner, and for the commander to issue a warning, even if the entry is no longer "officially" active.
Most likely too late for 1.02 ...
In the final mission of my new Aliens campaign I want to use "Ambush" blips. They way I'm doing it is having alien entry points that will be active for a single round. They show up, a blip comes through, and then it closes again. You never know where they may show up ...
The lurking rule still applies: a blip has to wait 1 turn to come out of such entry if there's a soldier less than 6 squares away from it.
Thats' where the problem appears: the new entry was announced, but you never get a warning about the lurking blip, and it does not even show on the scanner because the entry is no longer there. However, the aliens will "appear" from it just fine ...
That's nastier than what I wanted it to be. At least, you should get a warning, and a solid triangle on the scanner, so that you can move away from it, or set OW, or pray louder ...
My preferred fix would be for the lurking blip to show up on the scanner, and for the commander to issue a warning, even if the entry is no longer "officially" active.
Most likely too late for 1.02 ...