Area Names

[Kaleo]

You know how in Gloom2, for example, all the areas have names <pic *clicky-clicky*>. How do I do this? I have search fruitlessly...

Please help.

[TRaK]

target_location

http://www.wemakemaps.com/targetlocation.htm

[Kaleo]

Sweetz... Thaks TRaK

So biasically, If I put a target_location entity, it will name the room by a set radius (like the light entity) or will it name it by where the brushes are in the room?

[LinuxManMikeC]

Location marker used for team chats. The closest target_location in sight is used for the location. If none is in sight, the closest in distance is used.

"In sight" means there are no structural brushes between the player and the target_location.

[Survivor]

Location marker used for team chats. The closest target_location in sight is used for the location. If none is in sight, the closest in distance is used.

"In sight" means there are no structural brushes between the player and the target_location.

Am actually not so sure about that. Might also be vis area.

[Paradox]

The engine will use the nearest target_location if it cannot directly "see" one. Still a good idea to double them up in some areas, ie a room with multiple rooms, so that it doesn't get confused. The first beta maps did this, but it doesn't seem to be done anymore.  You can have multiple ents with the same text.

[player1]

Are they in all the default maps (I think they are not)? If not, could they be added to 1.2 to enable teamplay and communication? It's so much easier than typing while being shot at.

@Trak: great link!

[LinuxManMikeC]

The engine will use the nearest target_location if it cannot directly "see" one. Still a good idea to double them up in some areas, ie a room with multiple rooms, so that it doesn't get confused.

But as noted at that link posted by TRaK, it is best to try and keep it down to 1 per area.  Test your map with a singe target_location per area first.  If anything needs tweaking, try moving the entity first.  Play with distances between locations and line-of-sight.  Work with the algorithm instead of against it.  If all else fails and you really want the area labeling perfect, go ahead and add some redundant entities.  Remember though that even on todays hardware, performance could suffer.  That link also talks about increased network traffic with extra locations, so just be careful.

[Survivor]

The engine will use the nearest target_location if it cannot directly "see" one. Still a good idea to double them up in some areas, ie a room with multiple rooms, so that it doesn't get confused.

But as noted at that link posted by TRaK, it is best to try and keep it down to 1 per area.  Test your map with a singe target_location per area first.  If anything needs tweaking, try moving the entity first.  Play with distances between locations and line-of-sight.  Work with the algorithm instead of against it.  If all else fails and you really want the area labeling perfect, go ahead and add some redundant entities.  Remember though that even on todays hardware, performance could suffer.  That link also talks about increased network traffic with extra locations, so just be careful.

Tbh unless you go nuts with them it's hardly a concern. Just imagine them as a conflict area with the entity as a dot centre of an expanding circle. <40 should be easily attainable on most maps while being far sufficient for most areas.
And since most maps are fairly straightforward in shapes you should be able to apply the half rule between these points where the halfdistance between them determines the switchpoint for the locationmessage.

[Paradox]

Or lets say you have a duct moving across a hallway.  The algorithm would say that the one in the hall is closer, but you wanted to share the same one. Stick one in the duct, and your fine.

[Kaleo]

Awsome help. Thanks guys.