Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LWS Comments with no code attached: determine action #154

Open
MalucoMarinero opened this issue Mar 5, 2017 · 0 comments
Open

LWS Comments with no code attached: determine action #154

MalucoMarinero opened this issue Mar 5, 2017 · 0 comments

Comments

@MalucoMarinero
Copy link
Contributor

		// LWS: Units can (rarely) spawn on top of fires in certain maps. This causes them to
		// start burning on their first turn, and take damage on the next turn after that. Taking damage
		// causes them to activate, which begins the scamper. If we defer it here until the squad leaves
		// concealment it shuts down the entire AI patrol system because nobody will move while there is 
		// a pending scamper.
		//
		// If we don't wait for concealment to break, though, then the scampering units can't see XCOM,
		// and may flank themselves when deciding where to scamper. This occurs far more often than the
		// rare unit-spawns-on-fire case. We could attempt to mitigate both by only deferring the scamper
		// if someone on XCOM can *see* the unit that's scampering, but in the case of asymmetric LoS things
		// might still be screwy and the leader may flank itself. Probably better to try to fix this problem 
		// from the "nobody is allowed to move while there is a pending scamper" side, or try to come up with
		// some better conditions governing when to wait on concealment.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant