Firstly let me applaude the introduction of loc files (I think that's what they're called) into maps--those things that tell you your location on the map. Since their introduction in 3.1 they've improved gameplay imo.

Secondly, I was curious as to why mappers choose to put so few locations into their maps. Dod_caen is the only map I've noticed that has good locations built into it (fire alley, bank, wire alley, plaza, etc). On the other hand, dod_avalanche, for example, has just one loc for each flag (5 total). In avalanche's case, wouldn't it be better to put one maybe at the church and the tall building across from it in the plaza---something like "Church basement," "Church steeple," or "Building, 2nd Floor?"

'Props for bringing this feature to DoD. I'm thankful for it but curious about why it's not used more exhaustively in maps.

I think krastkoff has a lot of them. As for use, I don't use them because I'm lazy :) but some mapper might not think there important or don't have the room (entity limit)

and maybe some mappers havent spotted tuts on how to do them yet...

HINT

HINT

entity limit, hmm. Thanks for the replies

Originally posted by Angry Beaver
and maybe some mappers havent spotted tuts on how to do them yet...

HINT

HINT

you place a dod_location entity in your map and give it a name (dod_control_points count too) if you type %l in ingame chat the %l is replaced with the name of hte closes location

best use is a bind like "say Im at %l and need backup"

right, k I'd spotted both and i knew to use %l to call to it but I'd never got the misssing gap as to how to put in my map.

whats also annoying is how some maps simply have locations lsited as something like

ALLIED_POINT_SEWER or something, i made that up but you know what i mean, at least give it an appropriate name.

I believe the purpose of this was to put the locations in titles.txt, along with all of the env_message entries, like map_allied_victory2, map_spawn_warning, etc., but for some reason the locations aren't there. The reasoning behind using this method for all of the game text is that it would make it a lot easier to translate the game to other languages.

On the other hand, dod_avalanche, for example, has just one loc for each flag (5 total)
its not that theres only 5 in avalanche, theres probably not any(dod_locations).

as rozdower said, dod_control_points also act as location points, so when your near a control point(i.e. flag/objective) and you use the %l itll use the control_point name.

i think the biggest problem with dod_locations is that the %l variable will use the nearest dod_location to where you are.
thats why sometimes you can be nowhere near the location yet it will say you are.
i wouldve thought it would be better if you could asign an area that it works in.
like tie the dod_location to an invisible brush so when someone enters the brush and hits %l it shows up

yeah when I firts read about the %l I thought it was mapped with brush based entitys.

instead of converting maybe you could just add a "range" filter to the dod_location