This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| 4rpl:commands:createunitonterrain [2023/09/18 15:35] – Made wording more applicable + Settings are not a GUID. Vertu | 4rpl:commands:createunitonterrain [2025/02/14 14:57] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 8: | Line 8: | ||
| ===== Description ===== | ===== Description ===== | ||
| - | Creates a unit from a CMOD UID (GUID)((You can get the GUID from within the CPACK manager.\\ | + | Creates a unit from a CMOD UID (GUID)((You can get the GUID from within the CPACK manager. |
| GUIDs are unique to each custom unit and never change.)) or from an internal unit name((See [[4rpl: | GUIDs are unique to each custom unit and never change.)) or from an internal unit name((See [[4rpl: | ||
| for a list of these names.)). | for a list of these names.)). | ||
| + | |||
| + | initParams is a table that contains a set of variables that will be set on the newly created unit. See GetUnitSettings for a list of the data names that can be specified in the initData table when creating built in units. | ||
| The unit will be placed on the terrain at the supplied terrain cell coordinates. | The unit will be placed on the terrain at the supplied terrain cell coordinates. | ||