This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| 4rpl:commands:getunitposition [2022/06/21 14:41] – More efficient method Karsten75 | 4rpl:commands:getunitposition [2025/02/14 14:57] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 15: | Line 15: | ||
| Note: If this call is attempted on an non-existing unit, nothing will be put on the stack. | Note: If this call is attempted on an non-existing unit, nothing will be put on the stack. | ||
| + | In V 2.4, this behavior changes and this API will now return V3(0 0 0), similar to other APIs. | ||
| ===== Examples ===== | ===== Examples ===== | ||
| <code 4rpl> | <code 4rpl> | ||
| GetUnitPosition(< | GetUnitPosition(< | ||
| + | |||
| + | # to extract the individual values from the above vector: | ||
| + | <-pos.x -> | ||
| + | <-pos.y -> | ||
| + | <-pos.z -> | ||
| + | |||
| + | # or use the .dot syntax above to directly access the values in the vector, or | ||
| + | |||
| + | EV3(< | ||
| + | |||
| </ | </ | ||
| - | A " | + | A " |
| <code 4rpl> | <code 4rpl> | ||