Difference between revisions of "Target location"
m (→For Maps In Production: typo fix) |
(→For Maps In Production: Mostly wording updates) |
||
| Line 1: | Line 1: | ||
== For Maps In Production == | == For Maps In Production == | ||
| − | A ''target_location'' is a non-brush entity that allows a mapper to specify | + | A ''target_location'' is a non-brush entity that allows a mapper to specify a name for a certain area of the map. Unless a player has configured their client to do otherwise, these names will be used instead of map coordinates in both the fireteam box and teammate chat messages. |
| − | + | Using these entities will cause a warning to be displayed on the server console for every entity in the map during map load on etmain, shrub, and etpub (although etpub is actively developed, and this may change in the future.) The map will still run, unaffected, though. To use them with GtkRadiant, first make a file called ''et_entities_location.def'' in the scripts directory of your mapping install. Then, open the file in notepad and paste the following in the file, and then save. | |
===Target_location entity=== | ===Target_location entity=== | ||
| Line 17: | Line 17: | ||
</pre> | </pre> | ||
| − | This will allow you to place a target_location into your map | + | This will allow you to place a ''target_location'' into your map within GtkRadiant, which will appear as a small green box. When selected, give it a key called ''message'' with a value that is the name you want at that location. You only need to place ''target_location''s so that you can always see one; placing too many may be a waste of resources. |
== For Completed Maps == | == For Completed Maps == | ||
Revision as of 15:32, 13 November 2005
Contents
For Maps In Production
A target_location is a non-brush entity that allows a mapper to specify a name for a certain area of the map. Unless a player has configured their client to do otherwise, these names will be used instead of map coordinates in both the fireteam box and teammate chat messages.
Using these entities will cause a warning to be displayed on the server console for every entity in the map during map load on etmain, shrub, and etpub (although etpub is actively developed, and this may change in the future.) The map will still run, unaffected, though. To use them with GtkRadiant, first make a file called et_entities_location.def in the scripts directory of your mapping install. Then, open the file in notepad and paste the following in the file, and then save.
Target_location entity
/*QUAKED target_location (0 0.5 0) (-8 -8 -8) (8 8 8) Set "message" to the name of this location. The message can contain colorcodes, default color is ^3(yellow) Closest target_location in sight used for the location, if none in site, closest in distance, within PVS */
This will allow you to place a target_location into your map within GtkRadiant, which will appear as a small green box. When selected, give it a key called message with a value that is the name you want at that location. You only need to place target_locations so that you can always see one; placing too many may be a waste of resources.
For Completed Maps
Note: This method is less efficient engine-wise than using actual target_locations.
target_locations on exisitng maps are saved into a file (maps/$MAPNAME_loc_override.dat). this way they are seperated from the map and its .pk3
When adding target_locations to a map you will have acces to the following commands:
Loc_commands
Loc_add <message>
- Add a new target_location at your current position whit name <message>
Loc_del
- Deletes the target_location that you are currently "in"
Loc_move
- Moves the target_location that you are currently "in" to your current position
Loc_rename <message>
- Renames the target_location that you are currently "in" to <message>
Loc_show
- Shows the target_location that you are currently "in" as text in console
Loc_save
- Saves all target_locations to a file (maps/mapname_loc_override.dat)
Loc_load
- Reloads all target_locations from a file (maps/mapname_loc_override.dat)
Viewing locations
While adding locations to your map you are able to monitor your changes. This can be enabled using a cvar.
b_debuglocations (default: 0) - Bitmask to enable debugging/design aids for location names. Works with external .dats as well as target_location ents. The following values can be added together:
- 1 - Draw a bubble sprite at each location marker.
The nearest location is drawn in green, with all the others being drawn in red. - 2 - Add a dynamic light at each location marker.
The nearest location is lit in red, with all the others being lit in green. - 4 - Draw floating text at each location marker containing the location's name.
The nearest location is colored green instead of white. - 8 - Send updates to other players when a location is added, deleted, or renamed.
This function allows multiple people to cooperatively edit locations in a level. - 16 - Accept updates to locations from other players who are using b_debuglocations 8.
