supportInfo – Talk

From Bohemia Interactive Community
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 1: Line 1:
==Locations==
==Locations==
Here are some interesting new commands (in 1.08 hotfix) found using this command. Locations are the markings on the game map for things like town names, peak heights of hills, forest type icons, lighthouses, etc. This info is just my findings, nothing official or thoroughly tested:
Here are some interesting new commands (in 1.08 hotfix) found using the supportInfo command. Locations are the markings on the game map for things like town names, peak heights of hills, forest type icons, rocky areas etc. This info is just my findings, nothing official or thoroughly tested:


*b:LOCATION setType STRING
*b:LOCATION setType STRING

Revision as of 12:43, 23 November 2007

Locations

Here are some interesting new commands (in 1.08 hotfix) found using the supportInfo command. Locations are the markings on the game map for things like town names, peak heights of hills, forest type icons, rocky areas etc. This info is just my findings, nothing official or thoroughly tested:

  • b:LOCATION setType STRING
Can be used to change the type of location. Types are defined in CfgLocationTypes. Eg: "RockArea","VegetationVineyard".
  • b:LOCATION setVariable ARRAY
Same as setVariable.
  • b:LOCATION attachObject OBJECT
Attach location to an object, it's location will automatically update on the map. The objects orientation doesn't affect the location's orientation. Attach to objNull to detach from an object.
  • b:LOCATION setImportance SCALAR
Importance probably controls which location shall be drawn on the map in case of overlap. Values defined in CfgLocationTypes in the config range from 1 (not-important) to 7 (important).
  • b:CONTROL drawLocation LOCATION
not tested
  • b:LOCATION setName STRING
similar to setVehicleVarName. The use of these commands is beyond me.
  • b:LOCATION getVariable STRING
same as getVariable
  • b:ARRAY in LOCATION
check if position is within location's area. Area is based on it's attached position. A non-trigger spatial test!
  • b:LOCATION setSize ARRAY
set the location's area size, [x,y]. Map visual representation of location does not change.
  • b:LOCATION setText STRING
set's the triggers text. Used for text based location types.
  • b:LOCATION setDirection SCALAR
equivalent to setMarkerDir. Rotates the location area. Map visual representation of location does not rotate.
  • b:LOCATION setPosition ARRAY
similar to setPos. Locations seem to have a 3D position.
  • b:LOCATION setRectangular BOOL
presumably locations are ellipses if they are not rectangular. No effect on map visuals.
  • b:LOCATION setSide SIDE
No idea what impact this has. MP testing required?
  • u:nearestLocations ARRAY
return nearest locations to a position array. Syntax is nearestLocations [positionArray,[locationType,locationType2,...],searchRadius]
  • u:rectangular LOCATION
return location's shape
  • u:type LOCATION
returns location's type.
  • u:locationPosition LOCATION
return location's actual location, works with attached object.
  • u:name LOCATION
return location's name.
  • u:attachedObject LOCATION
return the object a location is attached to.
  • u:size LOCATION
return location's size array [x,y]
  • u:text LOCATION
return location's text.
  • u:direction LOCATION
return location's direction. This does not change with the direction of an attached object.
  • u:createLocation ARRAY
create a new location. returns the location. syntax is _myLocation = createLocation [locationType,positionArray,sizeX,sizeY]
  • u:deleteLocation LOCATION
delete a location.
  • u:side LOCATION
return location's side
  • u:nearestLocation ARRAY
return the nearest location to a given position array of a given type. syntax = nearestLocation [positionArray,locationType]
  • u:importance LOCATION
return location's importance value.
  • u:position LOCATION
return location's position. If location is attached to an object, the returned value is the location's position if it were not attached to an object.

This info needs a proper home. --Ceeeb 11:07, 23 November 2007 (CET)