UndeploysInto: Difference between revisions
m Updated template. |
mNo edit summary |
||
| (9 intermediate revisions by 4 users not shown) | |||
| Line 3: | Line 3: | ||
|files={{Categ|Rules(md).ini}} | |files={{Categ|Rules(md).ini}} | ||
|values=strings (names of [[VehicleTypes]]) | |values=strings (names of [[VehicleTypes]]) | ||
| | |special=none (needs confirmation) | ||
|types={{Categ|BuildingTypes}} | |types={{Categ|BuildingTypes}} | ||
|ts=yes | |ts=yes | ||
| Line 12: | Line 12: | ||
|rp=yes | |rp=yes | ||
}} | }} | ||
Specifies the [[VehicleType]] that this BuildingType can undeploy into (you can set which VehicleType deploys into this BuildingType by using the {{f|DeploysInto|link}} flag). This BuildingType's {{f|Buildup|link}} animation is played (in full length, unlike when you sell this building) in reverse direction. | |||
[http://forums.renegadeprojects.com/showthread.php?tid=1219&pid=13563#pid13563 It has been reported] that using <code>UndeploysInto=none</code> results in the object automatically being sold when undeployed. | |||
== Undeployed vehicle facing == | == Undeployed vehicle facing == | ||
| Line 21: | Line 22: | ||
! INI Flag || Facing | ! INI Flag || Facing | ||
|- | |- | ||
| {{ | | {{f|ConstructionYard|yes|link}} <br>[[Image:Warning small.png]] '''Warning:''' Side-effects.|| South-West | ||
|- | |- | ||
| {{ | | {{f|TickTank|yes|link}} || North-West | ||
|- | |- | ||
| {{ | | {{f|Artillary|yes|link}} || North-East | ||
|- | |- | ||
| {{ | | {{f|ICBMLauncher|yes|link}} | ||
| rowspan=2 | North-East | | rowspan=2 | North-East | ||
|- | |- | ||
| {{ | | {{f|SensorArray|yes|link}} | ||
|- | |- | ||
| {{yro}}{{ | | {{yro}}{{f|DeployFacing|link}} | ||
| rowspan=2 | As set | | rowspan=2 | As set | ||
|- | |- | ||
| {{yro}}{{ | | {{yro}}{{f|DeployDir|link}} | ||
|} | |} | ||
{{Bugs}} | |||
*If <b><u>[[BuildingTypes]]</u></b> has <b><u><font style="color:blue">UndeploysInto=</font>(name of vehicle)</u></b> but no <b><u>{{f|Buildup|(name of animation)|Link}}</u></b> <b ><u>[[BuildingTypes]]</u></b> cannot be restored to <b><u>[[VehicleTypes]]</u></b>.<br> | |||
*Even if you specify name <b>[[VehicleTypes]]</b> that do not exist, such as <b>UndeploysInto=AAA</b> | |||
tags <b>UndeploysInto</b> will work as expected, along with <b>[[VehicleTypes]]</b> that do not contain images. There is no information and <b>{{f|Locomotor|{4A582747-9839-11d1-B709-00A024DDAFD1}|Link}}.</b><br> | |||
(If you specify the name of [[AircraftTypes]] You must have complete information of specified [[AircraftTypes]] and importantly it will become [[VehicleTypes]] completely even if there is a match, e.g. ORCA)<br> | |||
*If [[BuildingTypes]] has [[DeploysInto]] and [[UndeploysInto]] [[BuildingTypes]] will not be repairable. | |||
*Using this with <b>construction yard</b>will cause an error if <b>construction yard</b> does not have {{f|UndeploysInto||link}}{{f|BaseUnit|link}}. | |||
*If you set it like this: | |||
'''[GAPILL]'''<br> | |||
'''UndeploysInto=GAPILL'''<br> | |||
And you need to have a [[Voxel]] file named '''GAPILL''' when you undeploy. | |||
You will be presented with [[VehicleTypes]] which has images with but no data whatsoever. | |||
Although '''[GAPILL]''' has information in the [[BuildingTypes]] however | |||
Latest revision as of 00:15, 3 December 2024
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Flag: | UndeploysInto |
| File(s): | Rules(md).ini |
| Values: | strings (names of VehicleTypes) |
| Special Values: | none (needs confirmation) |
| Applicable to: | BuildingTypes |
Specifies the VehicleType that this BuildingType can undeploy into (you can set which VehicleType deploys into this BuildingType by using the DeploysInto flag). This BuildingType's Buildup animation is played (in full length, unlike when you sell this building) in reverse direction.
It has been reported that using UndeploysInto=none results in the object automatically being sold when undeployed.
Undeployed vehicle facing
Mind that if the game doesn't know which direction the VehicleType should be facing when it undeploys, it will undeploy the building without spawning the vehicle. The facing can be specified in the following ways:
| INI Flag | Facing |
|---|---|
ConstructionYard=yes  Warning: Side-effects. |
South-West |
| TickTank=yes | North-West |
| Artillary=yes | North-East |
| ICBMLauncher=yes | North-East |
| SensorArray=yes | |
 DeployFacing
|
As set |
| DeployDir
|
Bugs/Side-Effects/Unexpected Limitations
- If BuildingTypes has UndeploysInto=(name of vehicle) but no Buildup=(name of animation) BuildingTypes cannot be restored to VehicleTypes.
- Even if you specify name VehicleTypes that do not exist, such as UndeploysInto=AAA
tags UndeploysInto will work as expected, along with VehicleTypes that do not contain images. There is no information and Locomotor={4A582747-9839-11d1-B709-00A024DDAFD1}.
(If you specify the name of AircraftTypes You must have complete information of specified AircraftTypes and importantly it will become VehicleTypes completely even if there is a match, e.g. ORCA)
- If BuildingTypes has DeploysInto and UndeploysInto BuildingTypes will not be repairable.
- Using this with construction yardwill cause an error if construction yard does not have UndeploysInto=BaseUnit.
- If you set it like this:
[GAPILL]
UndeploysInto=GAPILL
And you need to have a Voxel file named GAPILL when you undeploy.
You will be presented with VehicleTypes which has images with but no data whatsoever.
Although [GAPILL] has information in the BuildingTypes however