createUnit array – Talk
mNo edit summary |
mNo edit summary |
||
Line 16: | Line 16: | ||
In BIs list Returned value is stated as '''Object''' not '''Array''' | In BIs list Returned value is stated as '''Object''' not '''Array''' | ||
(Never mind about the above I fixed it, there was a missing '=' in the Parameter 4 definition.) | |||
And quite why we need to have things tagged onto the syntax example is completely beyond me: | And quite why we need to have things tagged onto the syntax example is completely beyond me: |
Revision as of 12:24, 25 August 2007
Why is the unitInfo array not explained? --T_D 00:24, 7 August 2006 (CEST)
- I have yet to go through the 'c' commands and the first list =? etc. I hope to tomorrow. If you find any commands missing the template then add {{errors}} and I will add the template. A few bugs to iron out yet. thanks for fixing any errors. ~~~~
I'm a little bit confused. what's the difference between createUnit and createUnit group? Similar problem I have with createVehicle and createVehicle array. --hoz 06:28, 28 February 2007 (CET) T_D
- Main difference between these command is that one is original OFP and the other was introduced by ArmA and has different syntax.
- Planck 13:41, 28 February 2007 (CET)
Seems that the formation does not work, strange. --T_D
What does 'Return Value: Paramater 4' mean?
If it means the listed Parameter 4 from the above list then it is wrong according to BI own comref source.
In BIs list Returned value is stated as Object not Array
(Never mind about the above I fixed it, there was a missing '=' in the Parameter 4 definition.)
And quite why we need to have things tagged onto the syntax example is completely beyond me:
Object= group createUnit ["type", position, markers, placement, "special"]
What the heck was wrong with:
group createUnit ["type", position, markers, placement, "special"]
Planck 13:18, 25 August 2007 (CEST)