UnloadingClass: Difference between revisions
en>Mevitar mNo edit summary |
en>Testid123 mNo edit summary |
||
| Line 13: | Line 13: | ||
== Notes == | == Notes == | ||
Although this tag is parsed for all [[TechnoTypes]], the logic works only for [[VehicleTypes]] that make use of [[Dock]] and [[IsSimpleDeployer]]. | Although this tag is parsed for all [[TechnoTypes]], the logic works only for [[VehicleTypes]] that make use of [[Dock]] and [[IsSimpleDeployer]]. | ||
{{Bugs}} | |||
*<b><u>[[VehicleTypes]]</u></b> that is defined in the section <b><u><font style="Color:blue">UnloadingClass</font></u></b> always has <b><u>[[Turret]]</u></b> | |||
Revision as of 15:53, 15 July 2024
|
|
|
|
|
|
| Flag: | UnloadingClass |
| File(s): | rules(md).ini |
| Values: | Strings: Normal text. (Limited to: VehicleTypes) |
| Default: | none |
| Applicable to: | VehicleTypes |
Specifies the vehicle that this unit should turn into when performing a special function. The unit doesn't actually turn into another vehicle, though, and usually only the Image value is read. The default value 'none' means that the original unit's image will be used.
Notes
Although this tag is parsed for all TechnoTypes, the logic works only for VehicleTypes that make use of Dock and IsSimpleDeployer.
Bugs/Side-Effects/Unexpected Limitations
- VehicleTypes that is defined in the section UnloadingClass always has Turret