[SUPPORT] Advanced Turn Based Tile Toolkit

[Monokkel]

@Wisdom-;297137

Hi ,
Great ideas, as usual

Your solution is about firing an overwatch event, and that’s really great even if I will maybe reduce line trace check during tick event, creating an increasing index integer and firing the line trace only when index % 4 = 0 (or more than 4, if needed)
That’s should increase system overall performance, even if a line trace is not an expensive operation.

My actual concern, unlike XCom, is to create a mobile and rotating sight area selection when you select overwatch special ability (by displaying, for example, 2 red lines that simulate the unit view field), so that I am concerned about the altitude. That’s why I think I’ll need a cone trace, or maybe I need to create an invisible cone mesh. When I apply that view field, using your idea, I will just change the unit rotation and apply a boolean value (isInOverwatch) to true, then continue to check line trace on tick % 4 = 0.

But can line trace be useful when attacker and victim are at different altitudes?

My solution works equally well for different altitudes. Just check both pitch and yaw. If either is below a certain threshold, fire your overwatch event. Or use only yaw, since I don’t think you’d want players to specify the pitch of their units heads when putting them in overwatch. My solution does not allow you to display a visible cone, of course, even though the result will be similar to a cone. If you want to display the cone you could of course use a semi-transparent cone mesh with the same angles as you’ve set as the cutoff for checking yaw. This wouldn’t visually account for cover, though. In that case you’d probably want to shine some sort of conical light from your pawn.