[Rambetter]

After some amount of head-scratching I have come to realize that trigger_location is too buggy to be used in a production map.  Use target_location instead.

PROBLEM #1

If two people enter a trigger_location and only one of them exits, the person who exited will continue to have $location associated with that trigger_location no matter where he goes as long as the second person is still in that trigger_location.  Furthermore, if both people exit and only one of them returns, both players will have $location associated with that trigger_location.

PROBLEM #2

This is a minor issue and has to do with $crosshair.  $crosshair on a section covered by trigger_location will only work if no target_location is visible from the area pointed to by the crosshair.  target_location will take precedence over trigger_location as far as $crosshair is concerned.

[Dragonne]

Problem 2 isn't a problem, it's a caveat to using them. I pretty much stick to targets anyway.