Location – Talk
No edit summary |
No edit summary |
||
Line 14: | Line 14: | ||
[[User:BarmyArmy|BarmyArmy]] | [[User:BarmyArmy|BarmyArmy]] | ||
getVariable and setVariable doesn't seem to work in ArmA II. | getVariable and setVariable doesn't seem to work in ArmA II. [[User:tsuki|tsuki]] |
Revision as of 21:32, 16 August 2009
This is a significant find. So these locations are Global in MP. Correct? But the variables are not due to the limitations of setVariable. Correct? And once a location is set can you move the location? Sounds like you cannot correct? --ViperMaul 19:58, 26 November 2007 (CET)
- Unfortunately I have no idea about MP performance (and no simple way to test). But I can tell you that mission created locations can be moved as freely as an object can be, while in my testing it seems the island's config defined locations cannot be altered. --Ceeeb 22:26, 26 November 2007 (CET)
Nice find Ceeeb! Hopefully someone will report how often these update (for a moving object) and how well they work with JIP. --Doolittle 06:56, 28 November 2007 (CET)
- Both answered.--Suma 10:50, 28 November 2007 (CET)
To quote the last bulletted point on the Location page. "A terrain's config can not be changed using the location script commands, but they can be found and read. This provides a single command method of finding nearby high points, towns, etc. " In other words you can, by script, determine the position and size of "Paraiso" as defined by the map/terrain. however if you do not like the size or shape or position you cannot by script change it, or event delete it and create a new one, the commands execute by have no effect. This restriction does NOT apply to locations created by script using createLocation BarmyArmy
getVariable and setVariable doesn't seem to work in ArmA II. tsuki