Fixed / Improved Logics

Allow deploy controlled MCV

In vanilla, you cannot deploy a controlled vehicle to ConstructionYard=true building. Now you can customize it.

In rulesmd.ini:

[General]
AllowDeployControlledMCV=false   ; boolean

Chrono sparkle animation customization & improvements

• It is now possible to customize the frame delay between instances of [General] -> ChronoSparkle1 animations created on objects being warped by setting [General] -> ChronoSparkleDisplayDelay.

• By default on buildings with MaxNumberOccupants higher than 0, chrono sparkle animation would be shown at each of the MuzzleFlashX coordinates. This behaviour is now customizable, and supports MuzzleFlashX indices higher than 10.

  • [General] -> ChronoSparkleBuildingDisplayPositions can be set to show the sparkle animation on the building (building), muzzle flash coordinates of current occupants (occupants), muzzle flash coordinates of all occupant slots (occupantslots) or any combination of these.

    • If occupants or occupantslots is listed without building, a single chrono sparkle animation is still displayed on building if it doesn’t have any occupants or it has MaxNumberOccupants value less than 1, respectively.

• The chrono sparkle animation that is displayed on building itself is also now displayed at the center of it rather than at center of its topmost cell.

In rulesmd.ini:

[General]
ChronoSparkleDisplayDelay=24                         ; integer, game frames
ChronoSparkleBuildingDisplayPositions=occupantslots  ; List of chrono sparkle position enum (building | occupants | occupantslots | all)

Crate improvements

There are some improvements on goodie crate logic:

• The statistic distribution of the randomly generated crates is now more uniform within the visible map region by using an optimized sampling procedure.

• You can now limit the crates’ spawn region to land only by setting [CrateRules] -> CreateOnlyOnLand to true.

• The limit of vehicles a player can own before unit crates start giving money instead can now be customized by setting UnitCrateVehicleCap. Negative numbers disable the cap entirely.

• FreeMCV setting is now actually respected and can be used to disable the forced unit selected from [General] -> BaseUnit that is given if player picks a crate and has enough credits but no existing buildings or BaseUnit vehicles.

  • The previously hardcoded credits threshold that must be passed can also now be customized via FreeMCV.CreditsThreshold.

In rulesmd.ini:

[CrateRules]
CrateOnlyOnLand=false          ; boolean
UnitCrateVehicleCap=50         ; integer
FreeMCV=true                   ; boolean
FreeMCV.CreditsThreshold=1500  ; integer

Customizable unit image in art

• Image tag in art INI is no longer limited to AnimationTypes and BuildingTypes, and can be applied to all TechnoTypes (InfantryTypes, VehicleTypes, AircraftTypes, BuildingTypes).

• The tag specifies only the file name (without extension) of the asset that replaces TechnoType’s graphics. If the name in Image is also an entry in the art INI, no tags will be read from it.

• By default this feature is disabled to remain compatible with YR. To use this feature, enable it in rules with ArtImageSwap=true.

• This feature supports SHP images for InfantryTypes, SHP and VXL images for VehicleTypes and VXL images for AircraftTypes.

In rulesmd.ini:

[General]
ArtImageSwap=false  ; disabled by default

In artmd.ini:

[CAML]
Image=JOSH

[BFRT]
Image=SREF

Customize resource storage

• Now Ares Storage feature can set which Tiberium type from [Tiberiums] list should be used for storing resources in structures with Refinery.UseStorage=yes and Storage > 0.

• This tag can not be used without Ares.

In rulesmd.ini:

[General]
Storage.TiberiumIndex=-1  ; integer, [Tiberiums] list index

Customize the chained damage of the wall

• In vanilla, when the wall is damaged, it will deal 200 damage to the walls in the 4 nearby cells. This makes connected walls more vulnerable to damage compared to single walls.

• Now you can customize that damage by using the following flag.

In rulesmd.ini:

[CombatDamage]
AdjacentWallDamage=200  ; integer

Customizing effect of level lighting on air units

• It is now possible to customize how air units are affected by level lighting, separately for AircraftTypes and infantry/vehicles with Jumpjet Locomotor.

  • AircraftLevelLightMultiplier & JumpjetLevelLightMultiplier are direct multipliers to level lighting applied on the units, for height levels above the cell they are on.

In rulesmd.ini:

[AudioVisual]
AircraftLevelLightMultiplier=1.0  ; floating point value, percents or absolute
JumpjetLevelLightMultiplier=0.0   ; floating point value, percents or absolute

Customizing default ColorScheme

• In vanilla, an AltPalette=yes animation or Voxel=yes Projectile image that cannot properly remap will use the first Color Scheme in the [Colors] list; now it can be manually specified.

In rulesmd.ini:

[AudioVisual]
AnimRemapDefaultColorScheme=      ; ColorScheme name

Iron Curtain & Force Shield extra tint intensity

• It is now possible to specify additional tint intensity applied to Iron Curtained and Force Shielded units.

In rulesmd.ini:

[AudioVisual]
IronCurtain.ExtraTintIntensity=0.0  ; floating point value
ForceShield.ExtraTintIntensity=0.0  ; floating point value

Jumpjet climbing logic enhancement

• You can now let the jumpjets increase their height earlier by set JumpjetClimbPredictHeight to true. The jumpjet will raise its height 5 cells in advance, instead of only raising its height when encountering cliffs or buildings in front of it.

• You can also let them simply skip the stop check by set JumpjetClimbWithoutCutOut to true. The jumpjet will not stop moving horizontally when encountering cliffs or buildings in front of it, but will continue to move forward while raising its altitude.

  • When JumpjetClimbPredictHeight is enabled, if the height raised five grids in advance is still not enough to cross cliffs or buildings, it will stop and move horizontally as before, unless JumpjetClimbWithoutCutOut is also enabled.

In rulesmd.ini:

[General]
JumpjetClimbPredictHeight=false  ; boolean
JumpjetClimbWithoutCutOut=false  ; boolean

Move IvanBomb Position

In vanilla, IvanBomb images display and the bombs detonate at the top-leftmost cell of the building foundation instead of at the center of buildings. This can now be changed.

In rulesmd.ini:

[CombatDamage]
IvanBombAttachToCenter=false  ; boolean

RadialIndicator visibility

In vanilla game, a structure’s radial indicator can be drawn only when it belongs to the player. Now it can also be visible to observer. On top of that, you can specify its visibility from other houses.

In rulesmd.ini:

[AudioVisual]
RadialIndicatorVisibility=allies  ; List of Affected House Enumeration (owner/self | allies/ally | enemies/enemy | all)

Re-enable obsolete [JumpjetControls]

• Re-enable obsolete [JumpjetControls], the keys in it will be as the default value of jumpjet units.

  • Moreover, added two tags for missing ones.

In rulesmd.ini:

[JumpjetControls]
Crash=5.0        ; floating point value
NoWobbles=false  ; boolean

Skirmish AI behavior dehardcode

• In vanilla, there is a hardcoded behavior that when an skirmish AI player has no factory and has not taken damage for a while, it will sell its buildings and set its units to hunt. This can be customized now.

  • [General] -> AIFireSale and [General] -> AIAllToHunt control whether the AI will act selling and hunting respectively.

  • [General] -> AIFireSaleDelay defines a timer, it will only work if [General] -> AIFireSale is set to true. When the first time the AI reaches the trigger condition of vanilla behavior, the timer starts and prevents the selling behavior from happening until the timer is expired.

  • You can use these flags to make the AIs “all in” before they are defeated.

• Another hardcoded behavior is that, when the AI deploys a MCV, it will gather all of its forces to that place. This can be toggle off now.

  • [General] -> GatherWhenMCVDeploy controls this behavior.

In rulesmd.ini:

[General]
AIFireSale=true           ; boolean
AIFireSaleDelay=0         ; integer, number of frames
AIAllToHunt=true          ; boolean
GatherWhenMCVDeploy=true  ; boolean

Use 8-bit RGB parameters for [ColorAdd]

• In vanilla, the values in the [ColorAdd] entry are used as RGB565 (0-31 for red & blue, 0-63 for green). Now, with this setting, you can use the more user-friendly 8-bit RGB (0-255) for input.

• This works for LaserTargetColor, IronCurtainColor, BerserkColor and ForceShieldColor.

In rulesmd.ini:

[AudioVisual]
ColorAddUse8BitRGB=false  ; boolean

Veinholes & Weeds

[General]
VeinholeGrowthRate=300        ; integer
VeinholeShrinkRate=100        ; integer
MaxVeinholeGrowth=2000        ; integer
VeinDamage=5                  ; integer
VeinholeTypeClass=VEINTREE    ; TerrainType

[CombatDamage]
VeinholeWarhead=VeinholeWH    ; WarheadType

[VeinholeWH]
Veinhole=yes

[AudioVisual]
VeinAttack=VEINATAC           ; AnimationType

[TechnoType]
EliteAbilities=VEIN_PROOF
ImmuneToVeins=yes

[VEINTREE]
IsVeinhole=true
Strength=1000                 ; integer - the strength of the Veinhole

[OverlayTypes]
126=VEINS                     ; The veins (weeds)
167=VEINHOLE                  ; The Veinhole itself
178=VEINHOLEDUMMY             ; A technical overlay

[SOMESW]                                        ; SuperWeaponType
UseWeeds=no                                     ; boolean - should the SW use weeds to recharge?
UseWeeds.Amount=                                ; integer - how many? default is General->WeedCapacity
UseWeeds.StorageTimer=no                        ; boolean - should the counter on the sidebar display the % of weeds stored?
UseWeeds.ReadinessAnimationPercentage=0.9       ; double - when this many weeds % are stored, the SW will show it's ready on the building (open nuke/open chrono, etc.)

Voxel light source customization

Voxel by C&CrispS

• It is now possible to change the position of the light relative to the voxels. This allows for better lighting to be set up.

  • Only the direction of the light is accounted, the distance to the voxel is not accounted.

  • Vanilla light (assuming UseFixedVoxelLighting=false) is located roughly at VoxelLightSource=0.201,-0.907,-0.362.

In rulesmd.ini:

[AudioVisual]
UseFixedVoxelLighting=false  ; boolean, whether to fix the lighting
VoxelLightSource=            ; X,Y,Z - position of the light in the world relative to each voxel, floating point values

Waypoints for buildings

• In vanilla, buildings are forbidden to use waypoints. Now you can allow that using the following flag.

In rulesmd.ini:

[General]
BuildingWaypoints=false  ; boolean

Carryall pickup voice

• It is now possible to override VoiceMove for Carryall=true aircraft for when commanding it to pick up vehicles by setting VoicePickup.

In rulesmd.ini:

[SOMEAIRCRAFT]  ; AircraftType
VoicePickup=    ; Sound entry

Customize the scatter caused by aircraft attack mission

• In vanilla, when an aircraft attacks, it forces the target’s cell to trigger a scatter. Now you can disable this behavior by setting the following flag to false.

In rulesmd.ini:

[SOMEAIRCRAFT]            ; AircraftType
FiringForceScatter=true   ; boolean

Extended Aircraft Missions

• Aircraft will now be able to use waypoints.

• When a guard command ([G] by default) or a area guard command ([Ctrl]+[Alt]) is issued, the aircraft will search for targets around the position (for guard is the current location, for area guard is the target position) and return immediately when ammos are depleted.

  • If the target is not found, or if there is still ammo when the target is destroyed, it will continue to hover over the guarded area.

• When an attack move command ([Ctrl]+[Shift]) is issued, the aircraft will move towards the destination and search for nearby targets on the route for attack. Once ammo is depleted or the destination is reached, it will return.

  • If the automatically selected target is destroyed but ammo is not depleted yet during the process, the aircraft will continue flying to the destination.

• In addition, the actions of aircraft are also changed.

  • ExtendedAircraftMissions.SmoothMoving controls whether the aircraft will return to the airport when the distance to the destination is less than half of SlowdownDistance or its turning radius.

  • ExtendedAircraftMissions.EarlyDescend controls whether the aircraft not have to fly directly above the airport before starting to descend when the distance between the aircraft and the landing point is less than SlowdownDistance (also work for aircraft spawned by aircraft carriers).

  • ExtendedAircraftMissions.RearApproach controls whether the aircraft should start landing at the airport from the opposite direction of LandingDir.

  • ExtendedAircraftMissions.FastScramble controls whether the aircraft can scramble when its airport has been destroyed.

  • ExtendedAircraftMissions.UnlandDamage controls the damage suffered by the aircraft every 4 frames when there is no airport for the aircraft to land. If the value is negative, it will crash immediately. Not recommended to use when ExtendedAircraftMissions is not enabled.

In rulesmd.ini:

[General]
ExtendedAircraftMissions=false            ; boolean
ExtendedAircraftMissions.UnlandDamage=-1  ; integer

[SOMEAIRCRAFT]                            ; AircraftType
ExtendedAircraftMissions.SmoothMoving=    ; boolean, default to [General] -> ExtendedAircraftMissions
ExtendedAircraftMissions.EarlyDescend=    ; boolean, default to [General] -> ExtendedAircraftMissions
ExtendedAircraftMissions.RearApproach=    ; boolean, default to [General] -> ExtendedAircraftMissions
ExtendedAircraftMissions.FastScramble=    ; boolean, default to [General] -> ExtendedAircraftMissions
ExtendedAircraftMissions.UnlandDamage=    ; integer, default to [General] -> ExtendedAircraftMissions.UnlandDamage

Fixed spawn distance & spawn height for airstrike / SpyPlane aircraft

• It is now possible to have aircraft spawned from (Elite)AirstrikeTeamType or Type=SpyPlane superweapons to be created at fixed distance from their intended target/destination instead of from edge of the map by setting SpawnDistanceFromTarget.

• SpawnHeight can also be used to override the initial height of the aircraft, which defaults to FlightLevel, or if not set then [General] -> FlightLevel.

In rulesmd.ini:

[SOMEAIRCRAFT]            ; AircraftType
SpawnDistanceFromTarget=  ; floating point value, distance in cells
SpawnHeight=              ; integer, height in leptons

Landing direction

• By default aircraft land facing the direction specified by [AudioVisual] -> PoseDir. This can now be customized per AircraftType via LandingDir, defaults to [AudioVisual] -> PoseDir. If the building the aircraft is docking to has aircraft docking direction set, that setting takes priority over this.

  • Negative values are allowed as a special case for AirportBound=false aircraft which makes them land facing their current direction.

In rulesmd.ini:

[SOMEAIRCRAFT]  ; AircraftType
LandingDir=     ; Direction type (integers from 0-255). Accepts negative values as a special case.

Animation weapon and damage settings

• Weapon can be set to a WeaponType, to create a projectile and immediately detonate it instead of simply dealing Damage by Warhead. This allows weapon effects to be applied.

• Damage.Delay determines delay between two applications of Damage. Requires Damage to be set to 1.0 or above. Value of 0 disables the delay. Keep in mind that this is measured in animation frames, not game frames. Depending on Rate, animation may or may not advance animation frames on every game frame.

• Damage.DealtByInvoker, if set to true, makes any Damage dealt to be considered as coming from the animation’s invoker (f.ex, firer of the weapon if it is Warhead AnimList/SplashList animation, the destroyed vehicle if it is DestroyAnim animation or the object the animation is attached to). If invoker has died or does not exist, the house the invoker belonged to is still used to deal damage and apply Phobos-introduced Warhead effects etc. If not set, the animation’s owner house, or failing that, owning house of object it is attached to or the building it belongs to is used to deal the damage.

  • Damage.ApplyFirepowerMult determines whether or not firepower modifiers from the animation’s invoker are applied on the damage dealt from this animation, if exists.

• Damage.ApplyOncePerLoop, if set to true, makes Damage be dealt only once per animation loop (on single loop animations, only once, period) instead of on every frame or intervals defined by Damage.Delay. The frame on which it is dealt is determined by Damage.Delay, defaulting to after the first animation frame.

In artmd.ini:

[SOMEANIM]                      ; AnimationType
Weapon=                         ; WeaponType
Damage.Delay=0                  ; integer, animation frames
Damage.DealtByInvoker=false     ; boolean
Damage.ApplyOncePerLoop=false   ; boolean
Damage.ApplyFirepowerMult=false ; boolean

Attached animation position customization

• You can now customize position of attached animations via different values for AttachedAnimPosition.

  • default: Animation shows up at the parent object’s logical position (for buildings, this is the top-leftmost cell / cell #0).

  • center: Animation shows up at the parent object’s visual center.

  • ground: Animation shows up at the parent object’s visual center but forced to ground level. Note that the animations is still considered attached to the object and is likely to be drawn above objects that the object itself would cover unless other settings are used to compensate.

In artmd.ini:

[SOMEANIM]                   ; AnimationType
AttachedAnimPosition=default ; Attached animation position enumeration (default|center|ground)

Customizable debris & meteor impact and warhead detonation behaviour

• ExplodeOnWater can be set to true to make the animation explode on impact with water. ExpireAnim will be played and Warhead is detonated or used to deal damage / generate light flash.

• Warhead.Detonate, if set to true, makes the Warhead fully detonate instead of simply being used to deal damage and generate light flash if it has Bright=true.

• WakeAnim contains wake animations to play if ExplodeOnWater is not set and the animation impacts with water. Defaults to [General] -> Wake if IsMeteor is not set to true, otherwise no animation. If more than one animation is listed, a random one is selected.

• SplashAnims contains list of splash animations used if ExplodeOnWater is not set and the animation impacts with water.

  • If SplashAnims.PickRandom is set to true, picks a random animation from SplashAnims to use on each impact with water. Otherwise last listed animation from SplashAnims is used.

• ExtraShadow can be set to false to disable the display of shadows on the ground.

In artmd.ini:

[SOMEANIM]                    ; AnimationType
ExplodeOnWater=false          ; boolean
Warhead.Detonate=false        ; boolean
WakeAnim=                     ; List of AnimationTypes
SplashAnims=                  ; List of AnimationTypes, default to [CombatDamage] -> SplashList
SplashAnims.PickRandom=false  ; boolean
ExtraShadow=true              ; boolean

Customize whether Crater=yes animation would destroy tiberium

• In vanilla, the anim with Crater=yes is hardcoded to destroy the tiberium in its cell. Now you can disable this behavior by setting the following tags to false.

In rulesmd.ini:

[General]
AnimCraterDestroyTiberium=true  ; boolean

In artmd.ini:

[SOMEANIM]                      ; AnimationType
Crater.DestroyTiberium=         ; boolean, default to [General] -> AnimCraterDestroyTiberium

Fire animations spawned by Scorch & Flamer

• Tiberian Sun allowed Scorch=true and Flamer=true animations to spawn fire animations from [AudioVisual] -> SmallFire & LargeFire. This behaviour has been reimplemented and is fully customizable.

  • ConstrainFireAnimsToCellSpots controls whether or not spawned animations are locked to cell spots (e.g the subcell positions infantry are also constrained to).

  • FireAnimDisallowedLandTypes controls which landtypes the fire animations are not allowed to spawn on. Defaults to water,rock,beach,ice for Scorch=true, none otherwise.

  • AttachFireAnimsToParent controls if the spawned animations are attached to the owner of the parent animation if it is also attached. Defaults to true for Scorch=true, otherwise false.

  • SmallFireCount determines number of small fire animations to spawn by both Scorch=true and Flamer=true animations. Defaults to 2 for Flamer=true, otherwise 1.

    • SmallFireAnims can be used to set the animation types, defaults to [AudioVisual] -> SmallFire (single animation).

    • SmallFireChances is a list of probabilities for the animations to spawn, up to SmallFireCount amount of items are read. Last item listed is used if count exceeds the number of listed probabilities. Defaults to 1.0,0.5 for Flamer=true, 1.0 otherwise.

    • SmallFireDistances is a list of distances in cells for the animations to spawn at from the parent animation’s coordinates, up to SmallFireCount amount of items are read. Last item listed is used if count exceeds the number of listed probabilities. Defaults to 0.25,0.625 for Flamer=true, 0.0 otherwise.

  • LargeFireCount determines number of large fire animations to spawn by Flamer=true animations only.

    • LargeFireAnims can be used to set the animation types, defaults to [AudioVisual] -> LargeFire (single animation).

    • LargeFireChances is a list of probabilities for the animations to spawn, up to LargeFireCount amount of items are read. Last item listed is used if count exceeds the number of listed probabilities.

    • LargeFireDistances is a list of distances in cells for the animations to spawn at from the parent animation’s coordinates, up to LargeFireCount amount of items are read. Last item listed is used if count exceeds the number of listed probabilities.

In artmd.ini:

[SOMEANIM]                          ; AnimationType
ConstrainFireAnimsToCellSpots=true  ; boolean
FireAnimDisallowedLandTypes=        ; List of LandTypes (none | clear | road | water | rock | wall | tiberium | beach | rough | ice | railroad | tunnel | weeds)
AttachFireAnimsToParent=            ; boolean
SmallFireCount=                     ; integer
SmallFireAnims=                     ; List of AnimationTypes
SmallFireChances=                   ; List of floating point values (percent or absolute)
SmallFireDistances=                 ; List of floating point values, distance in cells
LargeFireCount=1                    ; integer
LargeFireAnims=                     ; List of AnimationTypes
LargeFireChances=0.5                ; List of floating point values (percent or absolute)
LargeFireDistances=0.4375           ; List of floating point values, distance in cells

Layer on animations attached to objects

• You can now customize whether or not animations attached to objects follow the object’s layer or respect their own Layer setting. If this is unset, attached animations use ground layer.

In artmd.ini:

[SOMEANIM]             ; AnimationType
Layer.UseObjectLayer=  ; boolean

Ore stage threshold for HideIfNoOre

• You can now customize which growth stage should an ore/tiberium cell have to have animation with HideIfNoOre displayed. Cells with growth stage less than specified value won’t allow the anim to display.

In artmd.ini:

[SOMEANIM]               ; AnimationType
HideIfNoOre.Threshold=0  ; integer, minimal ore growth stage

AI base construction modification

• AI can now have some new behaviors.

  • AIAutoDeployMCV controls whether AI will still automatically deploy the mcv after owning a construction yard.

  • AISetBaseCenter controls whether AI will still set the newly deployed construction yard as the base center after owning a construction yard.

  • AIBiasSpawnCell controls whether AI will preferentially select the construction yard close to the birth point as the base center (useless in campaign).

  • AIForbidConYard controls whether AI cannot place buildings with ConstructionYard=true. AI will try to build one after a construction yard is destroyed but will not put it down. After that, it will continue to build other buildings. Building a construction yard will still take some time. You can try to reduce the build time of it.

  • AINodeWallsOnly controls whether AI can only automatically connect adjacent walls when there are wall base nodes around.

  • AICleanWallNode controls whether AI cannot place walls when there are no ProtectWithWall buildings around. If it cannot be placed, this base node will also be removed.

In rulesmd.ini:

[AI]
AIAutoDeployMCV=true   ; boolean
AISetBaseCenter=true   ; boolean
AIBiasSpawnCell=false  ; boolean
AIForbidConYard=false  ; boolean
AINodeWallsOnly=false  ; boolean
AICleanWallNode=false  ; boolean

Aircraft docking direction

• It is now possible to customize the landing direction for docking aircraft via AircraftDockingDir(N) (N optionally replaced by 0-based index for each DockingOffset separately, AircraftDockingDir and AircraftDockingDir0 are synonymous and will be used if direction is not set for a specific offset) on the dock building. This overrides the aircraft’s own landing direction setting and defaults to [AudioVisual] -> PoseDir.

In rulesmd.ini:

[SOMEBUILDING]          ; BuildingType
AircraftDockingDir(N)=  ; Direction type (integers from 0-255)

Allows refineries to use multiple ActiveAnim simultaneously

• In vanilla, the refinery uses different ActiveAnims depending on the storage. You can now make it use multiple ActiveAnims simultaneously like any other building.

In artmd.ini:

[SOMEBUILDING]                         ; BuildingType
Refinery.UseNormalActiveAnim=false     ; boolean

Allowed / disallowed types for FactoryPlant

• It is now possible to customize which TechnoTypes benefit from bonuses of a FactoryPlant=true building by listing them on FactoryPlant.AllowTypes and/or FactoryPlant.DisallowTypes.

  • FactoryPlant.Multiplier (Ares feature) is still applied on the bonuses if they are in effect.

In rulesmd.ini:

[SOMEBUILDING]               ; BuildingType
FactoryPlant.AllowTypes=     ; List of TechnoTypes
FactoryPlant.DisallowTypes=  ; List of TechnoTypes

Apply ZShapePointMove during buildups

• By default buildings do not apply ZShapePointMove (which offsets the ‘z shape’ applied on buildings which is used to adjust them in depth buffer and is used to fix issues related to that such as corners of buildings getting cut off when drawn) when buildup is being displayed. This behaviour can now be toggled by setting ZShapePointMove.OnBuildup.

In artmd.ini:

[SOMEBUILDING]                   ; BuildingType
ZShapePointMove.OnBuildup=false  ; boolean

Buildings considered as vehicles

• By default game considers buildings with both UndeploysInto set and Foundation equaling 1x1 as vehicles, in a manner of speaking. This behaviour can now be toggled individually of these conditions by setting ConsideredVehicle. These buildings are counted as vehicles for unit count tracking, are not considered as base under attack when damaged and can be mass selected by default, for an example.

• When capturing such “buildings”, the player won’t be notified by EVA capture event.

In rulesmd.ini:

[SOMEBUILDING]      ; BuildingType
ConsideredVehicle=  ; boolean

Custom exit cell for infantry factory

• By default Factory=InfantryType buildings use exit cell for the created infantry based on hardcoded settings if any of GDIBarracks, NODBarracks or YuriBarracks are set to true. It is now possible to define arbitrary exit cell for such building via BarracksExitCell. Below is a reference of the cell offsets for the hardcoded values.

In rulesmd.ini:

[SOMEBUILDING]     ; BuildingType
BarracksExitCell=  ; X,Y - cell offset

Custom whether to synchronously change the owner of the RadioLink-linked units when the owner of a building changes

• In vanilla, buildings with RadioLink (f.ex. war factory and air base) will change the owner of the RadioLink-linked units when the owner of the building changes. Now you can toggle this behaviour off by the following flags.

In rulesmd.ini:

[General]
BuildingRadioLink.SyncOwner=true ; boolean

[SOMEBUILDING]                   ; BuildingType
BuildingRadioLink.SyncOwner=     ; boolean, default to [General] -> BuildingRadioLink.SyncOwner

Customizable garrison and bunker properties

• You can now customize damage or ROF multipliers of a garrison or tank bunker building.

• You can now customize enter or exit sound of a tank bunker building.

In rulesmd.ini:

[SOMEBUILDING]              ; BuildingType
OccupyDamageMultiplier=     ; floating point value, default to [CombatDamage] -> OccupyDamageMultiplier
OccupyROFMultiplier=        ; floating point value, default to [CombatDamage] -> OccupyROFMultiplier
BunkerDamageMultiplier=     ; floating point value, default to [CombatDamage] -> BunkerDamageMultiplier
BunkerROFMultMultiplier=    ; floating point value, default to [CombatDamage] -> BunkerROFMultMultiplier
BunkerWallsUpSound=         ; Sound entry, default to [AudioVisual] -> BunkerWallsUpSound
BunkerWallsDownSound=       ; Sound entry, default to [AudioVisual] -> BunkerWallsDownSound

Customizable selling buildup sequence length for buildings that can undeploy

• By default buildings with UndeploysInto will only play 23 frames of their buildup sequence (in reverse starting from last frame) when being sold as opposed to being undeployed. This can now be customized via SellBuildupLength.

In rulesmd.ini:

[SOMEBUILDING]        ; BuildingType
SellBuildupLength=23  ; integer, number of buildup frames to play

Customizable & new grinder properties

Using ally grinder, restricting to vehicles only and refund display (Project Phantom)

• You can now customize which types of objects a building with Grinding set can grind as well as the grinding sound.

  • Grinding.AllowAllies changes whether or not to allow units to enter allies’ buildings.

  • Grinding.AllowOwner changes whether or not to allow units to enter your own buildings.

  • Grinding.AllowTypes can be used to define InfantryTypes and VehicleTypes that can be grinded by the building. Listing any will disable grinding for all types except those listed.

  • Grinding.DisallowTypes can be used to exclude InfantryTypes or VehicleTypes from being able to enter the grinder building.

  • Grinding.PlayDieSound controls if the units’ DieSound and VoiceDie are played when entering the grinder.

  • Grinding.Sound is a sound played by when object is grinded by the building.

  • Grinding.Weapon is a weapon fired at the building & by the building when it grinds an object. Will only be fired if at least weapon’s ROF amount of frames have passed since it was last fired.

    • Grinding.Weapon.RequiredCredits can be set to have the weapon require accumulated credits from grinding to fire. Accumulated credits for this purpose are reset every time when the weapon fires.

• For money string indication upon grinding, please refer to DisplayIncome.

In rulesmd.ini:

[SOMEBUILDING]                     ; BuildingType
Grinding.AllowAllies=false         ; boolean
Grinding.AllowOwner=true           ; boolean
Grinding.AllowTypes=               ; List of InfantryTypes / VehicleTypes
Grinding.DisallowTypes=            ; List of InfantryTypes / VehicleTypes
Grinding.PlayDieSound=true         ; boolean
Grinding.Sound=                    ; Sound entry, default to [AudioVisual] -> EnterGrinderSound
Grinding.Weapon=                   ; WeaponType
Grinding.Weapon.RequiredCredits=0  ; integer

Customize overpower logic

• Now you can specific how building can be overpowerd.

In rulesmd.ini:

[SOMEWARHEAD]             ; WarheadType
ElectricAssaultLevel=1    ; integer

[SOMEBUILDING]            ; BuildingType
Overpower.KeepOnline=2    ; integer, negative values mean that cannot keep online
Overpower.ChargeWeapon=1  ; integer, negative values mean that weapons can never be switched

Disable DamageSound

• Now you can disable DamageSound of a building.

In rulesmd.ini:

[SOMEBUILDING]            ; BuildingType
DisableDamageSound=false  ; boolean

Exclude Factory from providing multiple factory bonus

• It is now possible to exclude a building with Factory from counting towards MultipleFactory bonus.

In rulesmd.ini:

[SOMEBUILDING]                         ; BuildingType
ExcludeFromMultipleFactoryBonus=false  ; boolean

Power plant damage factor

• It is possible to customize the power decrement of a power plant when it’s damaged. The actual power output for this plant will be: Power minuses the product of original power decrement and Powerplant.DamageFactor. Can’t reduce power output lower than 0.

  • Specifically, if the factor is set to 0.0, power output won’t be decreased by losing health for this power plant.

In rulesmd.ini:

[SOMEBUILDING]                     ; BuildingType
PowerPlant.DamageFactor=1.0        ; floating point value

Skip anim delay for burst fire

• In Red Alert 1, the tesla coil will attack multiple times after charging animation. This is not possible in Red Alert 2, where the building must play the charge animation every time it fires.

• Now you can implement the above logic using the following flag.

In artmd.ini:

[SOMEBUILDING]                     ; BuildingType
IsAnimDelayedBurst=true            ; boolean

Unit repair customization

• It is now possible to customize the repairing of units by UnitRepair=true, UnitReload=true and Hospital=true buildings.

  • Units.RepairRate customizes the rate at which the units are repaired. This defaults to [General] -> ReloadRate if UnitReload=true and if overridden per AircraftType (Ares feature) can tick at different time for each docked aircraft. Setting this overrides that behaviour. For UnitRepair=true buildings this defaults to [General] -> URepairRate.

    • On UnitReload=true building setting this to negative value will fully disable the repair functionality.

  • Units.RepairStep how much Strength is restored per repair tick.

  • Units.RepairPercent is a multiplier to cost of repairing (cost / (maximum health / repair step)). Note that the final cost is set to 1 if it is less than that.

    • Units.UseRepairCost can be used to customize if repair cost is applied at all. Defaults to false for infantry, true for everything else.

In rulesmd.ini:

[SOMEBUILDING]        ; BuildingType
Units.RepairRate=     ; floating point value, ingame minutes
Units.RepairStep=     ; integer, default to [General] -> RepairStep
Units.RepairPercent=  ; floating point value, percents or absolute, default to [General] -> RepairPercent
Units.UseRepairCost=  ; boolean

Customize if cloning need power

• In vanilla, cloning vats can work fine even low power. Starting from Ares 2.0, they need power to work. Now you can specific it.

In rulesmd.ini:

[SOMEBUILDING]        ; BuildingType
Cloning.Powered=true  ; boolean

Auto deploy for GI-like infantry

• In RA2, the GI-like infantry controlled by the AI will automatically deploy to use their more powerful secondary weapons when engaging the enemy. This feature was broken in Yuri’s Revenge. Now you can use the following flags to re-enable this feature.

In rulesmd.ini:

[General]
InfantryAutoDeploy=false      ; boolean

[SOMEINFANTRY]                ; InfantryType
InfantryAutoDeploy=           ; boolean, default to [General] -> InfantryAutoDeploy

Prone speed customization

• In vanilla, infantry has hardcoded prone speed. Now you can customize it.

In rulesmd.ini:

[General]
ProneSpeed.Crawls=0.67        ; floating point value, multiplier
ProneSpeed.NoCrawls=1.5       ; floating point value, multiplier

[SOMEINFANTRY]                ; InfantryType
ProneSpeed=                   ; floating point value, multiplier, by default, use the corresponding global value according to Crawls

Fire particle target coordinate adjustment when firer rotates

• By default particle systems with BehavesLike=Fire shift their target coordinates if the object that created the particle system (e.g firer of a weapon) is rotating. This behavior can now be disabled per particle system type.

In rulesmd.ini:

[SOMEPARTICLESYSTEM]               ; ParticleSystemType
AdjustTargetCoordsOnRotation=true  ; boolean

Customizable gas particle speed

• Gas particles can now drift at a custom speed.

In rulesmd.ini:

[GASPARTICLE]          ; Particle with BehavesLike=Gas
Gas.MaxDriftSpeed=2    ; integer (TS default is 5)

Airburst & Splits

• AirburstWeapon logic has been reimplemented and thus there are several additions & changes to it.

• Splits can be set to true to use projectile splitting logic from Firestorm, with the number of split projectiles defined by Cluster.

  • RetargetAccuracy defines the probability that the splitted projectiles head to the same target as the original projectile.

  • RetargetSelf determines if it is possible for the splitted projectiles to aim at the firer of the original projectile.

    • RetargetSelf.Probability is the probability that if the original firer is chosen as a target, it is kept as the target instead of rerolled to another.

  • Splits.TargetingDistance is the distance in cells that any potential target has to be within from the original target coordinates to be eligible for targeting by the splitted projectiles.

  • Splits.TargetCellRange is the distance in whole cells from the original target cell from which the splitted projectiles can pick new target cells if not enough TechnoType targets were found nearby.

  • Splits.UseWeaponTargeting, if set to true, enables weapon targeting filter for when checking targets for splitted projectiles. Target’s LegalTarget setting, Warhead Verses against Armor as well as AirburstWeapon weapon targeting filters & AttachEffect filters will be checked.

    • Do note that this overrides checking Warhead for AffectsAllies/Owner/Enemies for targeting. You can use CanTargetHouses on AirburstWeapon to achieve similar behaviour, however.

• Behaviour for if Airburst is set to true can also be customized.

  • AirburstSpread is the distance in cells that the effect covers, with each cell in range being targeted by AirburstWeapon by default.

  • Airburst.UseCluster, if set to true, makes it so that only number of cells in the affected area dictated by Cluster will be affected, instead of all of them.

    • If Airburst.RandomClusters is set to true, the cells affected will be picked by random. Otherwise they will be evenly spaced (counting from center to edges of affected area).

  • Airburst.TargetAsSource can be used to override source or ‘firing’ coordinate to match that of the intended target instead of projectile’s current position.

    • If Airburst.TargetAsSource.SkipHeight is also set, then projectile’s current height will be used instead of target’s height still.

• AroundTarget controls whether or not targets for projectiles created by Airburst or Splits are checked for in area around the original projectile’s intended target, or where the original projectile detonated. Defaults to value of Splits.

• AirburstWeapon.ApplyFirepowerMult determines whether or not firepower modifiers from the firer of the original projectile are applied on the projectiles created from AirburstWeapon.

• AirburstWeapon.SourceScatterMin and AirburstWeapon.SourceScatterMax can be used to scatter the source or ‘firing’ coordinate around the original coordinate.

In rulesmd.ini:

[SOMEPROJECTILE]                          ; Projectile
Splits=                                   ; boolean
RetargetAccuracy=0.0                      ; floating point value, percents or absolute (0.0-1.0)
RetargetSelf=true                         ; boolean
RetargetSelf.Probability=0.5              ; floating point value, percents or absolute (0.0-1.0)
Splits.TargetingDistance=5.0              ; floating point value, distance in cells
Splits.TargetCellRange=3                  ; integer, cell offset
Splits.UseWeaponTargeting=false           ; boolean
AirburstSpread=1.5                        ; floating point value, distance in cells
Airburst.UseCluster=false                 ; boolean
Airburst.RandomClusters=false             ; boolean
Airburst.TargetAsSource=false             ; boolean
Airburst.TargetAsSource.SkipHeight=false  ; boolean
AroundTarget=                             ; boolean
AirburstWeapon.ApplyFirepowerMult=false   ; boolean
AirburstWeapon.SourceScatterMin=0.0       ; floating point value, distance in cells
AirburstWeapon.SourceScatterMax=0.0       ; floating point value, distance in cells

Cluster scatter distance customization

• ClusterScatter.Min and ClusterScatter.Max can be used to set minimum and maximum distance, respectively, in cells from the original detonation coordinate any additional detonations if Cluster is set to value higher than 1 can appear at.

In rulesmd.ini:

[SOMEPROJECTILE]        ; Projectile
ClusterScatter.Min=1.0  ; floating point value, distance in cells
ClusterScatter.Max=2.0  ; floating point value, distance in cells

Customizable projectile gravity

• You can now specify individual projectile gravity.

  • Setting Gravity=0 is not recommended as it will cause the projectile to fly backwards and be unable to hit the target which is not at the same height. We suggest to use Straight Trajectory instead. See here.

In rulesmd.ini:

[SOMEPROJECTILE]        ; Projectile
Gravity=6.0             ; floating point value

Customizing initial facing behavior

• Previously projectiles that had Voxel=true images were hardcoded to have downwards initial trajectory. This behavior can now be toggled on for other types of projectiles or disabled for voxel projectiles. In addition to defaulting to true for Voxel=true projectiles, it also now defaults to true for any Vertical=true projectile.

In rulesmd.ini:

[SOMEPROJECTILE]        ; Projectile
VerticalInitialFacing=  ; boolean

FlakScatter distance customization

• By default FlakScatter=true makes Inviso=true projectiles scatter within a distance range calculated as [Minimum * 2, Maximum * 2] in cells, where the Minimum is 0 and Maximum is [CombatDamage] -> BallisticScatter, resulting in a range of 0 to 2 * BallisticScatter cells. This behavior can now be customized using BallisticScatter.Min to set the Minimum value and BallisticScatter.Max to set the Maximum value. If not set, the default values are used. When estimating the actual scatter range, remember that the original *2 multiplier mechanism still applies.

In rulesmd.ini:

[SOMEPROJECTILE]      ; Projectile
BallisticScatter.Min= ; floating point value, distance in cells
BallisticScatter.Max= ; floating point value, distance in cells

Shrapnel enhancements

Shrapnel appearing against ground & buildings in Project Phantom

• ShrapnelWeapon can now be triggered against ground & buildings via Shrapnel.AffectsGround and Shrapnel.AffectsBuildings.

• Setting Shrapnel.UseWeaponTargeting now allows weapon target filtering to be enabled for ShrapnelWeapon. Target’s LegalTarget setting, Warhead Verses against Armor as well as ShrapnelWeapon weapon targeting filters & AttachEffect filters will be checked.

  • Do note that this overrides the normal check of only allowing shrapnels to hit non-allied objects. Use CanTargetHouses=enemies to manually enable this behaviour again.

In rulesmd.ini:

[SOMEPROJECTILE]                   ; Projectile
Shrapnel.AffectsGround=false       ; boolean
Shrapnel.AffectsBuildings=false    ; boolean
Shrapnel.UseWeaponTargeting=false  ; boolean

Airstrike flare visual customizations

• It is now possible to customize color of airstrike flare tint on target on the TechnoType calling in the airstrike as well as customize the color of the line drawn to target.

  • LaserTargetColor can be used to set the index of color from [ColorAdd].

  • AirstrikeLineColor sets the color of the line and dot drawn from firer to target.

In rulesmd.ini:

[AudioVisual]
AirstrikeLineColor=255,0,0  ; integer - Red,Green,Blue

[SOMETECHNO]                ; TechnoType
LaserTargetColor=           ; integer - [ColorAdd] index, default to [AudioVisual] -> LaserTargetColor
AirstrikeLineColor=         ; integer - Red,Green,Blue, default to [AudioVisual] -> AirstrikeLineColor

Airstrike target eligibility

• By default whether or not a building can be targeted by airstrikes (Airstrike=true Warhead) depends on value of CanC4, which also affects other things. This can now be changed independently by setting AllowAirstrike. If not set, defaults to value of CanC4. For non-building targets, the default value is true.

• AirstrikeTargets determines what types of targets are valid airstrike targets for this Warhead.

• The airstrike aircraft will now aim at the target itself rather than the cell beneath its feet, therefore it is possible to properly designate air strikes against non-building targets.

In rulesmd.ini:

[SOMETECHNO]                ; TechnoType
AllowAirstrike=             ; boolean

[SOMEWARHEAD]               ; WarheadType
AirstrikeTargets=buildings  ; List of Affected Target Enumeration (none|infantry|units|buildings|all)

Alternate FLH customizations

• AlternateFLH.OnTurret can be used to customize whether or not AlternateFLH used for OpenTopped transport firing coordinates, multiple mind control link offsets etc. is calculated relative to the unit’s turret if available or body.

• AlternateFLH.ApplyVehicle can be used to customize whether or not a transport applies its AlternateFLH to passengers of the VehicleType, who by default use their own FLH, as opposed to passengers of the InfantryType who adhere to AlternateFLH.

In artmd.ini:

[SOMETECHNO]                     ; TechnoType
AlternateFLH.OnTurret=true       ; boolean
AlternateFLH.ApplyVehicle=false  ; boolean

Building-provided self-healing customization

• It is now possible to set a global cap for the effects of InfantryGainSelfHeal and UnitsGainSelfHeal by setting InfantryGainSelfHealCap & UnitsGainSelfHealCap under [General], respectively.

• Whether or not MultiplayPassive=true houses benefit from these effects can be controlled via GainSelfHealAllowMultiplayPassive.

• In campaign, whether or not these effects for player can be benefited by houses with PlayerControl=true can be controlled via GainSelfHealFromPlayerControl.

• Whether or not these effects can be benefited by allied houses can be controlled via GainSelfHealFromAllies.

• It is also possible to change the pip frames displayed from pips.shp individually for infantry, units and buildings by setting the frames for infantry & unit self-healing on Pips.SelfHeal.(Infantry/Units/Buildings) under [AudioVisual], respectively.

  • Pips.SelfHeal.(Infantry/Units/Buildings).Offset can be used to customize the pixel offsets for the displayed pips, individually for infantry, units and buildings.

• Whether or not a TechnoType benefits from effects of InfantryGainSelfHeal or UnitsGainSelfHeal buildings or neither can now be controlled by setting SelfHealGainType.

  • If SelfHealGainType is not set, InfantryTypes and VehicleTypes with Organic set to true gain self-healing from InfantryGainSelfHeal, other VehicleTypes from UnitsGainSelfHeal and AircraftTypes & BuildingTypes never gain self-healing.

In rulesmd.ini:

[General]
InfantryGainSelfHealCap=                ; integer, maximum amount of InfantryGainSelfHeal that can be in effect at once, must be 1 or higher
UnitsGainSelfHealCap=                   ; integer, maximum amount of UnitsGainSelfHeal that can be in effect at once, must be 1 or higher
GainSelfHealAllowMultiplayPassive=true  ; boolean
GainSelfHealFromPlayerControl=false     ; boolean
GainSelfHealFromAllies=false            ; boolean

[AudioVisual]
Pips.SelfHeal.Infantry=13,20            ; integer, frames of pips.shp for infantry & unit-self healing pips, respectively
Pips.SelfHeal.Units=13,20               ; integer, frames of pips.shp for infantry & unit-self healing pips, respectively
Pips.SelfHeal.Buildings=13,20           ; integer, frames of pips.shp for infantry & unit-self healing pips, respectively
Pips.SelfHeal.Infantry.Offset=25,-35    ; X,Y, pixels relative to default
Pips.SelfHeal.Units.Offset=33,-32       ; X,Y, pixels relative to default
Pips.SelfHeal.Buildings.Offset=15,10    ; X,Y, pixels relative to default

[SOMETECHNO]                            ; TechnoType
SelfHealGainType=                       ; Self-Heal Gain Type Enumeration (noheal|infantry|units)

Customizable ChronoSphere teleport delays for units

• It is now possible to customize (globally and per TechnoType) the warp-in delay for units teleporting through Type=ChronoSphere/Warp Superweapon, both before and after the jump.

In rulesmd.ini:

[General]
ChronoSphereDelay=0     ; integer, game frames
ChronoSpherePreDelay=60 ; integer, game frames

[SOMETECHNO]            ; TechnoType
ChronoSphereDelay=      ; integer, game frames, default to [General] -> ChronoSphereDelay
ChronoSpherePreDelay=   ; integer, game frames, default to [General] -> ChronoSpherePreDelay

Customizable harvester ore gathering animation

Custom ore gathering anims in Project Phantom

• You can now specify which anim should be drawn when a harvester of specified type is gathering specified type of ore.

In rulesmd.ini:

[SOMETECHNO]                     ; TechnoType
OreGathering.Anims=              ; List of AnimationTypes
OreGathering.FramesPerDir=15     ; List of integers
OreGathering.Tiberiums=0         ; List of Tiberium IDs

Customizable target evaluation map zone check behaviour

• By default, any non-AircraftType units seeking targets via ScriptType team mission (action) 0 Attack Target Type or any attack team missions introduced in Phobos check if the potential target is in same map zone as the attacking unit to be able to pick it as a target. This can now be customized to allow objects from any map zone with no constraints (TargetZoneScanType=any) or only if they are within weapon range (TargetZoneScanType=inrange).

In rulesmd.ini:

[SOMETECHNO]             ; TechnoType
TargetZoneScanType=same  ; target zone scan enumeration (same|any|inrange)

Customizable Teleport/Chrono Locomotor settings per TechnoType

Chrono Legionnaire and Ronco using different teleportation settings in YR: New War

• You can now specify Teleport/Chrono Locomotor settings per TechnoType to override default rules values. Unfilled values default to values in [General].

• Applicable to Techno that have Teleport/Chrono Locomotor attached, or being chronowarped by chronosphere.

  • Chronoshift.WarpOut and Chronoshift.WarpIn will override WarpOut and WarpIn respectively when the techno is being chronowarped by chronosphere, if set.

• WarpAway specify the anim when the techno is being erased by Temporal=yes warhead. Will override Ares’ Temporal.WarpAway tag on warhead, if set.

• If more than one animation is listed in WarpOut, WarpIn or WarpAway, a random one is selected.

In rulesmd.ini:

[SOMETECHNO]            ; TechnoType
WarpOut=                ; List of AnimationTypes (played when Techno warping out), default to [General] -> WarpOut
WarpIn=                 ; List of AnimationTypes (played when Techno warping in), default to [General] -> WarpIn
Chronoshift.WarpOut=    ; List of AnimationTypes (played when Techno warping out by chronosphere), default to [TechnoType] -> WarpOut
Chronoshift.WarpIn=     ; List of AnimationTypes (played when Techno warping in by chronosphere), default to [TechnoType] -> WarpIn
WarpAway=               ; List of AnimationTypes (played when Techno being erased by Temporal=yes warhead), default to [General] -> WarpAway
ChronoTrigger=          ; boolean, if yes then delay varies by distance, if no it is a constant
ChronoDistanceFactor=   ; integer, amount to divide the distance to destination by to get the warped out delay
ChronoMinimumDelay=     ; integer, the minimum delay for teleporting, no matter how short the distance
ChronoRangeMinimum=     ; integer, can be used to set a small range within which the delay is constant
ChronoDelay=            ; integer, delay after teleport for chronosphere

Customizable veterancy insignias

• You can now customize veterancy insignia of TechnoTypes.

  • Insignia.(Rookie|Veteran|Elite) can be used to set a custom insignia file, optionally for each veterancy stage. Like the original / default file, pips.shp, they are drawn using palette.pal as palette.

  • InsigniaFrame(.Rookie|Veteran|Elite) can be used to set (zero-based) frame index of the insignia to display, optionally for each veterancy stage. Using -1 uses the default setting. Default settings are -1 (none) for rookie, 14 for veteran and 15 for elite.

    • A shorthand InsigniaFrames can be used to list them in order from rookie, veteran and elite instead as well. InsigniaFrame(.Rookie|Veteran|Elite) takes priority over this.

    • These settings will be overriden by the properties set in InsigniaType, if InsigniaType is set.

  • Normal insignia can be overridden for specific weapon modes of Gunner=true units by setting Insignia(.Frame/.Frames).WeaponN where N stands for 1-based weapon mode index. If not set, defaults to non-mode specific insignia settings.

    • These settings will be overriden by the properties set in InsigniaType, if InsigniaType.WeaponN is set.

  • Normal insignia can be overridden when its current passenger size reaches a certain amount by setting Insignia(.Frame/.Frames).PassengersN where N stands for the current passenger size amount (from 0 to Passengers of the transport). If not set, defaults to non-passenger specific insignia settings. Will be overridden by weapon mode insignia settings, if set.

    • These settings will be overriden by the properties set in InsigniaType, if InsigniaType.PassengersN is set.

  • Insignia.ShowEnemy controls whether or not the insignia is shown to enemy players.

  • You can make insignias appear only on selected units using DrawInsignia.OnlyOnSelected.

  • Position for insignias can be adjusted by setting DrawInsignia.AdjustPos.Infantry for infantry, DrawInsignia.AdjustPos.Buildings for buildings, and DrawInsignia.AdjustPos.Units for others.

  • DrawInsignia.AdjustPos.BuildingsAnchor can be set to an anchor point to anchor the insignia position relative to the building’s selection bracket. By default the insignia position is not anchored to the selection bracket.

  • DrawInsignia.UsePixelSelectionBracketDelta can be set to use techno’s PixelSelectionBracketDelta to additionally adjust insignias vertically.

In rulesmd.ini:

[General]
EnemyInsignia=true                                          ; boolean

[AudioVisual]
DrawInsignia.OnlyOnSelected=false                           ; boolean
DrawInsignia.UsePixelSelectionBracketDelta=false            ; boolean
DrawInsignia.AdjustPos.Infantry=5,2                         ; X,Y, position offset from default
DrawInsignia.AdjustPos.Units=10,6                           ; X,Y, position offset from default
DrawInsignia.AdjustPos.Buildings=10,6                       ; X,Y, position offset from default
DrawInsignia.AdjustPos.BuildingsAnchor=                     ; Hexagon vertex enumeration (top|lefttop|leftbottom|bottom|rightbottom|righttop)

[SOMETECHNO]                                                ; TechnoType
Insignia=                                                   ; filename - excluding the .shp extension
Insignia.Rookie=                                            ; filename - excluding the .shp extension
Insignia.Veteran=                                           ; filename - excluding the .shp extension
Insignia.Elite=                                             ; filename - excluding the .shp extension
InsigniaFrame=-1                                            ; int, frame of insignia shp (zero-based) or -1 for default
InsigniaFrame.Rookie=-1                                     ; int, frame of insignia shp (zero-based) or -1 for default
InsigniaFrame.Veteran=-1                                    ; int, frame of insignia shp (zero-based) or -1 for default
InsigniaFrame.Elite=-1                                      ; int, frame of insignia shp (zero-based) or -1 for default
InsigniaFrames=-1,-1,-1                                     ; int, frames of insignia shp (zero-based) or -1 for default
Insignia.WeaponN=                                           ; filename - excluding the .shp extension
Insignia.WeaponN.Rookie=                                    ; filename - excluding the .shp extension
Insignia.WeaponN.Veteran=                                   ; filename - excluding the .shp extension
Insignia.WeaponN.Elite=                                     ; filename - excluding the .shp extension
InsigniaFrame.WeaponN=-1                                    ; int, frame of insignia shp (zero-based) or -1 for default
InsigniaFrame.WeaponN.Rookie=-1                             ; int, frame of insignia shp (zero-based) or -1 for default
InsigniaFrame.WeaponN.Veteran=-1                            ; int, frame of insignia shp (zero-based) or -1 for default
InsigniaFrame.WeaponN.Elite=-1                              ; int, frame of insignia shp (zero-based) or -1 for default
InsigniaFrames.WeaponN=-1,-1,-1                             ; int, frames of insignia shp (zero-based) or -1 for default
Insignia.PassengersN=                                       ; filename - excluding the .shp extension
Insignia.PassengersN.Rookie=                                ; filename - excluding the .shp extension
Insignia.PassengersN.Veteran=                               ; filename - excluding the .shp extension
Insignia.PassengersN.Elite=                                 ; filename - excluding the .shp extension
InsigniaFrame.PassengersN=-1                                ; int, frame of insignia shp (zero-based) or -1 for default
InsigniaFrame.PassengersN.Rookie=-1                         ; int, frame of insignia shp (zero-based) or -1 for default
InsigniaFrame.PassengersN.Veteran=-1                        ; int, frame of insignia shp (zero-based) or -1 for default
InsigniaFrame.PassengersN.Elite=-1                          ; int, frame of insignia shp (zero-based) or -1 for default
InsigniaFrames.PassengersN=-1,-1,-1                         ; int, frames of insignia shp (zero-based) or -1 for default
Insignia.ShowEnemy=                                         ; boolean, defaults to [General] -> EnemyInsignia

Customizable wake anim

• You can now specify the Wake anim per TechnoType to override default rules value.

  • Wake.Grapple and Wake.Sinking can be used to further customize wake anim when the techno is being parasited or sunken.

In rulesmd.ini:

[SOMETECHNO]         ; TechnoType
Wake=                ; Anim (played when Techno moving on the water), default to [General] -> Wake
Wake.Grapple=        ; Anim (played when Techno being parasited on the water), defaults to [TechnoType] -> Wake
Wake.Sinking=        ; Anim (played when Techno sinking), defaults to [TechnoType] -> Wake

Customize bridge falling down damage

Use different fall damage depending on whether it lands in water in Zero Boundary by @Stormsulfur

• Now you can customize the damage a unit receives when it falls from a bridge.

• FallingDownDamage customizes the damage a unit receives at the end of a fall. It can be a percentage or an integer.

• FallingDownDamage.Water customizes the damage a unit receives when it falls onto the water. Defaults to FallingDownDamage.

• If it is a negative percentage, corresponding damage will be dealt based on the current health of the unit.

In rulesmd.ini:

[SOMETECHNO]                    ; TechnoType
FallingDownDamage=              ; integer / percentage
FallingDownDamage.Water=        ; integer / percentage

Damaged speed customization

• In vanilla, units using drive/ship loco will has hardcoded speed multiplier when damaged. Now you can customize it.

• The max valuebale value is 1.0, you cannot make unit get faster on yellow condition by it.

In rulesmd.ini:

[General]
DamagedSpeed=0.75        ; floating point value, multiplier

[SOMETECHNO]             ; TechnoType
DamagedSpeed=            ; floating point value, multiplier

Debris voxel animations limitation

• Now, the original DebrisMaximums can be used in conjunction with new DebrisMinimums to limit the quantity of DebrisTypes when DebrisTypes.Limit is enabled.

  • The default value of DebrisTypes.Limit is whether the number of DebrisMaximums is greater than (not equal to) 1 (for compatibility reasons).

In rulesmd.ini:

[SOMETECHNO]        ; TechnoType
DebrisTypes.Limit=  ; boolean
DebrisMaximums=     ; List of integers
DebrisMinimums=     ; List of integers

DropPod

• DropPod properties can now be customized on a per-TechnoType (non-building) basis.

  • If you want to attach the trailer animation to the pod, set DropPod.Trailer.Attached to yes.

  • By default LaserTrails that are attached to the infantry will not be drawn if it’s on DropPod.

    • If you really want to use it, set DropPodOnly on the LaserTrail’s type entry in art.

  • If you want DropPod.Weapon to be fired only upon hard landing, set DropPod.Weapon.HitLandOnly to true.

  • The landing speed is not smaller than it’s current height /10 + 2 for unknown reason. A small DropPod.Speed value therefore results in exponential deceleration.

In rulesmd.ini:

[SOMETECHNO]                  ; TechnoType
DropPod.Angle=                ; double, default to [General] -> DropPodAngle, measured in radians
DropPod.AtmosphereEntry=      ; anim, default to [AudioVisual] -> AtmosphereEntry
DropPod.GroundAnim=           ; 2 anims, default to [General] -> DropPod
DropPod.AirImage=             ; SHP file, the pod's shape, default to POD
DropPod.Height=               ; int, default to [General] -> DropPodHeight
DropPod.Puff=                 ; anim, default to [AudioVisual] -> DropPodPuff
DropPod.Speed=                ; int, default to [General] -> DropPodSpeed
DropPod.Trailer=              ; anim, default to [General] -> DropPodTrailer, which by default is SMOKEY
DropPod.Trailer.Attached=     ; boolean, default to no
DropPod.Trailer.SpawnDelay=   ; int, number of frames between each spawn of DropPod.Trailer, default to 6
DropPod.Weapon=               ; weapon, default to [General] -> DropPodWeapon
DropPod.Weapon.HitLandOnly=   ; boolean, default to no

Exploding object customizations

• By default Explodes=true TechnoTypes have all of their passengers killed when they are destroyed. This behaviour can now be disabled by setting Explodes.KillPassengers=false.

• BuildingTypes with Explodes=true can by default explode even when they are still being built or sold. This can be disabled by setting Explodes.DuringBuildup to false. This causes them to behave as if Explodes was set to false while being built up or sold.

In rulesmd.ini:

[SOMETECHNO]                 ; TechnoType
Explodes.KillPassengers=true ; boolean

[SOMEBUILDING]               ; BuildingType
Explodes.DuringBuildup=true  ; boolean

Forbid parallel AI queues

• You can now set if specific types of factories do not have AI production cloning issue instead of Ares’ indiscriminate behavior of AllowParallelAIQueues=no.

  • If AllowParallelAIQueues=no (Ares feature) is set, the tags have no effect.

• You can also exclude specific TechnoTypes from being built in parallel by AI by setting ForbidParallelAIQueues to true on a TechnoType.

In rulesmd.ini:

[GlobalControls]
AllowParallelAIQueues=yes           ; must be set yes/true unless you don't use Ares
ForbidParallelAIQueues.Infantry=no  ; boolean
ForbidParallelAIQueues.Vehicle=no   ; boolean
ForbidParallelAIQueues.Navy=no      ; boolean
ForbidParallelAIQueues.Aircraft=no  ; boolean
ForbidParallelAIQueues.Building=no  ; boolean

[SOMETECHNO]                        ; TechnoType
ForbidParallelAIQueues=false        ; boolean

Force techno targeting in distributed frames to improve performance

• When you create many technos in a same frame (i.e. starting the game with a campaign map that initially has a large number of technos), they will always scan for targets in a synchronous period, causing game lag. Increasing targeting delay alone will not make things better, as their targeting is still synchronized.

• It is now possible to force them to seek targets separately. If DistributeTargetingFrame=true is set, techno’s targeting timer will be initiated with a random delay, ranging in [0,15]. This can distribute their targeting timing within 15 frames, thus alleviating the above-mentioned lag.

  • You can use DistributeTargetingFrame.AIOnly to make it only work for AI (Players are not likely to have so many technos.)

In rulesmd.ini:

[General]
DistributeTargetingFrame=false         ; boolean
DistributeTargetingFrame.AIOnly=true   ; boolean

[SOMETECHNO]                           ; TechnoType
DistributeTargetingFrame=              ; boolean

Iron Curtain & Force Shield effects on organics customization

• In vanilla game, when Iron Curtain is applied on Organic=true units like squids or infantry, they could only get killed instantly by C4Warhead. This behavior is now unhardcoded and can be set with IronCurtain.EffectOnOrganics globally and on per-TechnoType basis with IronCurtain.Effect. Following values are respected:

  • kill : Iron Curtain kills the organic object with a specifc warhead. This is the default value for Organic=true units and infantry if not otherwise specified.

  • invulnerable : Iron Curtain makes the organic object invulnerable like buildings and vehicles.

  • ignore : Iron Curtain doesn’t give any effect on the organic object.

• Identical controls are available for Force Shield as well.

In rulesmd.ini:

[CombatDamage]
IronCurtain.EffectOnOrganics=kill  ; Iron Curtain effect Enumeration (kill | invulnerable | ignore)
IronCurtain.KillOrganicsWarhead=   ; WarheadType, default to [CombatDamage] -> C4Warhead
ForceShield.EffectOnOrganics=kill  ; Iron Curtain effect Enumeration (kill | invulnerable | ignore)
ForceShield.KillOrganicsWarhead=   ; WarheadType, default to [CombatDamage] -> C4Warhead

[SOMETECHNO]                       ; TechnoType with Organic=true
IronCurtain.Effect=                ; IronCurtain effect Enumeration (kill | invulnerable | ignore)
IronCurtain.KillWarhead=           ; WarheadType, default to [CombatDamage] -> IronCurtain.KillOrganicsWarhead
ForceShield.Effect=                ; IronCurtain effect Enumeration (kill | invulnerable | ignore)
ForceShield.KillWarhead=           ; WarheadType, default to [CombatDamage] -> ForceShield.KillOrganicsWarhead

Jumpjet rotating on crashing toggle

• Jumpjet that is going to crash starts to change its facing uncontrollably, this can now be turned off.

In rulesmd.ini:

[SOMETECHNO]               ; TechnoType
JumpjetRotateOnCrash=true  ; boolean

Kill spawns on low power

• Powered=yes structures that spawn aircraft like Aircraft Carriers will stop targeting the enemy if low power.

• Spawned aircraft self-destruct if they are flying.

In rulesmd.ini:

[SOMESTRUCTURE]          ; BuildingType
Powered.KillSpawns=false ; boolean

PipScale pip customizations

• It is now possible to change the size of pips (or more accurately the pixel increment to the next pip drawn) displayed on PipScale.

  • Pips.Generic.(Buildings.)Size is for non-ammo pips on non-building TechnoTypes / buildings, accordingly, and Pips.Ammo.(Buildings.)Size is in turn for ammo pips, split similarly between non-building technos and buildings.

  • Ammo pip size can also be overridden on per TechnoType-basis using AmmoPipSize.

• Ammo pip frames can now also be customized.

  • AmmoPipFrame and EmptyAmmoPipFrame are frames (zero-based) of pips2.shp used for ammo pip and empty ammo pip (this is not set by default) for when PipWrap=0 (this is the default).

  • AmmoPipWrapStartFrame is used as start frame (zero-based, from pips2.shp) for when PipWrap is above 0. The start frame is the empty frame and up to Ammo divided by PipWrap frames after it are used for the different reload stages.

  • AmmoPipOffset can be used to shift the starting position of ammo pips.

• Pips for TechnoTypes with Spawns can now also be customized.

  • ShowSpawnsPips determines whether or not these pips are shown at all, as they are independent from PipScale setting.

  • SpawnsPipFrame and EmptySpawnsPipFrame are frames (zero-based) of pips.shp (for buildings) or pips2.shp (for others) used for a spawnee pip and empty spawnee pip, respectively.

  • SpawnsPipSize determines the pixel increment to the next pip drawn. Defaults to [AudioVisual] -> Pips.Generic.(Buildings.)Size if not set.

  • SpawnsPipoffset can be used to shift the starting position of spawnee pips.

• Pips for Storage can now also be customized via new keys in [AudioVisual].

  • Pips.Tiberiums.Frames can be used to list frames (zero-based) of pips.shp (for buildings) or pips2.shp (for others) used for tiberium types, in the listed order corresponding to tiberium type index. Defaults to 5 for tiberium type index 1, otherwise 2.

    • Pips.Tiberiums.EmptyFrame can be used to set the frame for empty slots, defaults to 0.

  • Pips.Tiberiums.DisplayOrder controls in which order the tiberium type pips are displayed, takes a list of tiberium type indices. Any tiberium type not listed will be displayed in sequential order after the listed ones.

  • Pips.Tiberiums.WeedFrame controls which frame is displayed on Technos with Weeder=yes, takes a (zero-based) index of a frame in pips.shp (for buildings) or pips2.shp (for others). Defaults to 1.

    • Pips.Tiberiums.WeedEmptyFrame can be used to set the frame for empty weed slots, defaults to 0.

In rulesmd.ini:

[AudioVisual]
Pips.Generic.Size=4,0                ; X,Y, increment in pixels to next pip
Pips.Generic.Buildings.Size=4,2      ; X,Y, increment in pixels to next pip
Pips.Ammo.Size=4,0                   ; X,Y, increment in pixels to next pip
Pips.Ammo.Buildings.Size=4,2         ; X,Y, increment in pixels to next pip
Pips.Tiberiums.EmptyFrame=0          ; integer, frame of pips.shp (buildings) or pips2.shp (others) (zero-based)
Pips.Tiberiums.Frames=2,5,2,2        ; List of integers, frames of pips.shp (buildings) or pips2.shp (others) (zero-based)
Pips.Tiberiums.DisplayOrder=0,2,3,1  ; List of integers, tiberium type indices
Pips.Tiberiums.WeedEmptyFrame=0      ; integer, frame of pips.shp (buildings) or pips2.shp (others) (zero-based)
Pips.Tiberiums.WeedFrame=1           ; integer, frame of pips.shp (buildings) or pips2.shp (others) (zero-based)

[SOMETECHNO]                         ; TechnoType
AmmoPipFrame=13                      ; integer, frame of pips2.shp (zero-based)
EmptyAmmoPipFrame=-1                 ; integer, frame of pips2.shp (zero-based)
AmmoPipWrapStartFrame=14             ; integer, frame of pips2.shp (zero-based)
AmmoPipSize=                         ; X,Y, increment in pixels to next pip
AmmoPipOffset=0,0                    ; X,Y, position offset from default
ShowSpawnsPips=true                  ; boolean
SpawnsPipFrame=1                     ; integer, frame of pips.shp (buildings) or pips2.shp (others) (zero-based)
EmptySpawnsPipFrame=0                ; integer, frame of pips.shp (buildings) or pips2.shp (others) (zero-based)
SpawnsPipSize=                       ; X,Y, increment in pixels to next pip
SpawnsPipOffset=0,0                  ; X,Y, position offset from default

Power drain for units

• Infantry, vehicles and aircraft can now drain or provide Power if UnitPowerDrain=true is set.

In rulesmd.ini:

[General]
UnitPowerDrain=false  ; boolean

[SOMETECHNO]          ; TechnoType
Power=0               ; integer, positive means output, negative means drain

RadarInvisible for non-enemy house

• In vanilla, RadarInvisible is ignored if the techno is allied with the current player. Now you can change this behavior.

In rulesmd.ini:

[SOMETECHNO]                         ; TechnoType
RadarInvisibleToHouse=               ; Affected House Enumeration (none|owner/self|allies/ally|team|enemies/enemy|all), default to enemy if RadarInvisible=true, none otherwise

Subterranean unit travel height and speed

• It is now possible to control the height at which units with subterranean (Tunnel) Locomotor travel, globally or per TechnoType.

• Subterranean movement speed is now also customizable, both globally and per TechnoType. If per-TechnoType value is negative, global value is used. This does not affect the speed at which the unit moves vertically when burrowing which is determined by Speed multiplied by [General] -> TunnelSpeed.

In rulesmd.ini:

[General]
SubterraneanHeight=-256  ; integer, height in leptons (1/256th of a cell)
SubterraneanSpeed=19     ; floating point value

[SOMETECHNO]             ; TechnoType
SubterraneanHeight=      ; integer, height in leptons (1/256th of a cell)
SubterraneanSpeed=-1     ; floating point value

Target scanning delay optimization

• In vanilla, the game used NormalTargetingDelay and GuardAreaTargetingDelay to globally control the target searching intervals. Increasing these values would make units stupid, while decreasing them would cause game lag.

• Now, you can define them per techno, also allowing different values for AI and players. The default values are the same as those originally defined by the vanilla flags.

  • You can also specific this delay for attack move mission. The default value is NormalTargetingDelay.

In rulesmd.ini:

[General]
AINormalTargetingDelay=              ; integer, game frames
PlayerNormalTargetingDelay=          ; integer, game frames
AIGuardAreaTargetingDelay=           ; integer, game frames
PlayerGuardAreaTargetingDelay=       ; integer, game frames
AIAttackMoveTargetingDelay=          ; integer, game frames
PlayerAttackMoveTargetingDelay=      ; integer, game frames

[SOMETECHNO]                         ; TechnoType
AINormalTargetingDelay=              ; integer, game frames
PlayerNormalTargetingDelay=          ; integer, game frames
AIGuardAreaTargetingDelay=           ; integer, game frames
PlayerGuardAreaTargetingDelay=       ; integer, game frames
AIAttackMoveTargetingDelay=          ; integer, game frames
PlayerAttackMoveTargetingDelay=      ; integer, game frames

Voxel body multi-section shadows

UH-0 helicopter with dynamic propeller and its shadow in Bellum Æternum

• It is also now possible for vehicles and aircraft to display shadows for multiple sections of the voxel body at once, instead of just one section specified by ShadowIndex, by specifying the section indices in ShadowIndices (which defaults to ShadowIndex) in unit’s artmd.ini entry.

  • ShadowIndex.Frame and ShadowIndices.Frame can be used to customize which frame of the HVA animation for the section from ShadowIndex and ShadowIndices is used to display the shadow, respectively. -1 is special value which means currently shown frame is used, and ShadowIndices.Frame defaults to this.

In artmd.ini:

[SOMETECHNO]          ; TechnoType
ShadowIndices=        ; List of integers (voxel section indices)
ShadowIndex.Frame=0   ; integer (HVA animation frame index)
ShadowIndices.Frame=  ; List of integers (HVA animation frame indices)

Voxel shadow scaling in air

• It is now possible to adjust how voxel air units (VehicleType & AircraftType) shadows scale in air. By default the shadows scale by AirShadowBaseScale (defaults to 0.5) amount if unit is ConsideredAircraft=true.

  • If HeightShadowScaling=true, the shadow is scaled by amount that is determined by following formula: Max(AirShadowBaseScale ^ (currentHeight / ShadowSizeCharacteristicHeight), HeightShadowScaling.MinScale), where currentHeight is unit’s current height in leptons, ShadowSizeCharacteristicHeight overrideable value that defaults to the maximum cruise height (JumpjetHeight, FlightLevel etc) and HeightShadowScaling.MinScale sets a floor for the scale.

In rulesmd.ini:

[AudioVisual]
AirShadowBaseScale=0.5            ; floating point value
HeightShadowScaling=false         ; boolean
HeightShadowScaling.MinScale=0.0  ; floating point value

[SOMETECHNO]                      ; TechnoType
ShadowSizeCharacteristicHeight=   ; integer, height in leptons

Allow techno type considered as other type when recruiting techno for teams

• It is now possible to make techno type considered as other type when recruiting techno for teams, both for AI team recruitment and Create Team action.

  • Only affect techno that’s presented on the map. Cannot make AI produce this type of techno if it doesn’t have any.

In rulesmd.ini:

[SOMETECHNO]                      ; TechnoType
TeamMember.ConsideredAs=          ; List of TechnoTypes

Animated TerrainTypes

Animated trees used in Ion Shock

• By default IsAnimated, AnimationRate and AnimationProbability only work on TerrainTypes with SpawnsTiberium set to true. This restriction has now been lifted.

  • Length of the animation can now be customized by setting AnimationLength as well, defaulting to half (or quarter if damaged frames are enabled) the number of frames in TerrainType’s image.

In rulesmd.ini:

[SOMETERRAINTYPE]  ; TerrainType
AnimationLength=   ; integer, number of frames

Custom palette

• You can now specify custom palette for TerrainTypes in similar manner as TechnoTypes can.

In artmd.ini:

[SOMETERRAINTYPE]  ; TerrainType
Palette=           ; filename - excluding .pal extension and three-character theater-specific suffix

Customizable ore spawners

Different ore spawners in Rise of the East

• You can now specify which type of ore certain TerrainType would generate.

• It’s also now possible to specify a range value for an ore generation area different compared to standard 3x3 rectangle. Ore will be uniformly distributed across all affected cells in a spread range.

• You can specify which ore growth stage will be spawned and how many cells will be filled with ore per ore generation animation. Corresponding tags accept either a single integer value or two comma-separated values to allow randomized growth stages from the range (inclusive).

In rulesmd.ini:

[SOMETERRAINTYPE]             ; TerrainType
SpawnsTiberium.Type=0         ; tiberium/ore type index
SpawnsTiberium.Range=1        ; integer, radius in cells
SpawnsTiberium.GrowthStage=3  ; integer - single or comma-sep. range
SpawnsTiberium.CellsPerAnim=1 ; integer - single or comma-sep. range

Damaged frames and crumbling animation

• By default game shows damage frame only for TerrainTypes alive at only 1 point of health left. Because none of the original game TerrainType assets were made with this in mind, the logic is now locked behind a new key HasDamagedFrames.

  • Instead of showing at 1 point of HP left, TerrainTypes switch to damaged frames once their health reaches [AudioVisual] -> ConditionYellow.Terrain percentage of their maximum health.

• In addition, TerrainTypes can now show ‘crumbling’ animation after their health has reached zero and before they are deleted from the map by setting HasCrumblingFrames to true.

  • Crumbling frames start from first frame after both regular & damaged frames and ends at halfway point of the frames in TerrainType’s image.

  • Sound event from CrumblingSound (if set) is played when crumbling animation starts playing.

  • Destroy animation & sound only play after crumbling animation has finished.

In rulesmd.ini:

[AudioVisual]
ConditionYellow.Terrain=  ; floating-point value, default to [AudioVisual] -> ConditionYellow

[SOMETERRAINTYPE]         ; TerrainType
HasDamagedFrames=false    ; boolean
HasCrumblingFrames=false  ; boolean
CrumblingSound=           ; Sound entry

Minimap color customization

• TerrainTypes can now be made to display on minimap with different colors by setting MinimapColor.

In rulesmd.ini:

[SOMETERRAINTYPE]  ; TerrainType
MinimapColor=      ; integer - Red,Green,Blue

Passable & buildable-upon TerrainTypes

• TerrainTypes can now be made passable or buildable upon by setting IsPassable or CanBeBuiltOn, respectively.

  • Movement cursor is displayed on IsPassable TerrainTypes unless force-firing.

  • CanBeBuiltOn=true terrain objects are removed when building is placed on them.

In rulesmd.ini:

[SOMETERRAINTYPE]   ; TerrainType
IsPassable=false    ; boolean
CanBeBuiltOn=false  ; boolean

Minimap color customization

• Ore can now be made to display on minimap with different colors by setting MinimapColor on Tiberiums.

In rulesmd.ini:

[SOMEORE]      ; Tiberium
MinimapColor=  ; integer - Red,Green,Blue

Allow miners do area guard

• In vanilla, when miners enter area guard mission, they immediately switch to harvest mission. Now you can make them perform area guard mission normally like other technos.

  • We made it work only for miners controlled by the player, because this will prevent AI’s miners from going work.

  • If Harvester.CanGuardArea.RequireTarget set to true, it’ll switch back to regular harvest mission when there’s no valid target within its guard range.

In rulesmd.ini:

[SOMEVEHICLE]                               ; VehicleType
Harvester.CanGuardArea=false                ; boolean
Harvester.CanGuardArea.RequireTarget=false  ; boolean

Bunker entering check dehardcode

• In vanilla, vehicles entering tank bunkers are subject to a series of hardcoding restrictions, including having to have turrets, having to have weapons, and not having Hover speed types. Now you can skip these restrictions.

• This needs to be used with Bunkerable=yes.

• This flag only skips the static check, that is, the check on the unit type. The dynamic check (cannot be parasitized) remains unchanged.

In rulesmd.ini:

[SOMEVEHICLE]              ; VehicleType
BunkerableAnyway=false     ; boolean

Custom Unit Crate Reroll Chance

• It is possible to influence weighting of units given from crates (CrateGoodie=true) via CrateGoodie.RerollChance, which determines the chance that if this type of unit is rolled, it will reroll again for another type of unit.

In rulesmd.ini:

[SOMEVEHICLE]                  ; VehicleType
CrateGoodie.RerollChance=0.0   ; floating point value, percents or absolute (0.0-1.0)

Customize harvester dump amount

• Now you can limit how much ore the harvester can dump out per time, like it in Tiberium Sun.

• Less than or equal to 0 means no limit, it will always dump out all at one time.

In rulesmd.ini:

[General]
HarvesterDumpAmount=0.0               ; float point value

[SOMEVEHICLE]                         ; VehicleType
HarvesterDumpAmount=                  ; float point value

Customize type selection for IFV

In vanilla game, when using type selection command on IFVs, all of them will be selected regardless of their current modes, which is allowed to customize now.

• WeaponGroupAsN determines which group the IFV is in when enabling WeaponN, where N stands for 1-based weapon mode index. IFVs in the same group will be selected together during type a selection, while not included those in different groups.

• TypeSelectUseIFVMode determines whether all IFV modes will be considered as its own group by default during a type selection.

  • If it’s set to true, WeaponGroupAsN will be default to N for each WeaponN, which makes each of them become a standalone type during a type selection.

  • If it’s set to false, WeaponGroupAsN will be default to 0 for all weapons, which makes type selection on IFVs work the same as before.

In rulesmd.ini:

[General]
TypeSelectUseIFVMode=false   ; boolean

[SOMEVEHICLE]                ; VehicleType
WeaponGroupAsN=              ; string, default to N if [General] -> TypeSelectUseIFVMode=true, and 0 if false

Customizing crushing tilt and slowdown

• Vehicles with Crusher=true and OmniCrusher=true / MovementZone=CrusherAll were hardcoded to tilt when crushing vehicles / walls respectively. This now obeys TiltsWhenCrushes but can be customized individually for these two scenarios using TiltsWhenCrusher.Vehicles and TiltsWhenCrusher.Overlays, which both default to TiltsWhenCrushes.

• CrushForwardTiltPerFrame determines how much the forward tilt is adjusted per frame when crushing overlays or vehicles. Defaults to -0.02 for vehicles using Ship locomotor crushing overlays, -0.050000001 for all other cases.

• CrushOverlayExtraForwardTilt is additional forward tilt applied after an overlay has been crushed by the vehicle.

• It is possible to customize the movement speed slowdown when MovementZone=CrusherAll vehicle crushes walls by setting CrushSlowdownMultiplier.

• You can also disable the slowdown completely by using the flag SkipCrushSlowdown. This is not the same as CrushSlowdownMultiplier=1.0. Used to avoid a bug where the vehicle sometimes loses speed when Accelerates=true and MovementZone=CrushAll are set.

In rulesmd.ini:

[SOMEVEHICLE]                      ; VehicleType
TiltsWhenCrushes.Vehicles=         ; boolean
TiltsWhenCrushes.Overlays=         ; boolean
CrushForwardTiltPerFrame=          ; floating point value
CrushOverlayExtraForwardTilt=0.02  ; floating point value
CrushSlowdownMultiplier=0.2        ; floating point value
SkipCrushSlowdown=false            ; boolean

Destroy animations

• DestroyAnim has been extended to work with VehicleTypes, with option to pick random animation if DestroyAnim.Random is set to true. These animations store owner and facing information for use with CreateUnit logic.

In rulesmd.ini:

[SOMEVEHICLE]                          ; VehicleType
DestroyAnim=                           ; List of AnimationTypes
DestroyAnim.Random=true                ; boolean

IsSimpleDeployer vehicle ammo change on deploy

• Ammo.AddOnDeploy determines the number of ammo added or subtracted after the vehicle has deployed or undeployed.

  • Ammo count cannot go below 0 or above the maximum ammo for vehicle’s type (in case the deploy results in type conversion, type is the one after the conversion).

In rulesmd.ini:

[SOMEVEHICLE]       ; VehicleType
Ammo.AddOnDeploy=0  ; integer

IsSimpleDeployer customizations

• It is possible to enable checking if the deployed unit (if type conversion is in use, the conversion result will be used for these checks) is allowed to deploy on the cell which will also affect deploy cursor availability by setting IsSimpleDeployer.ConsiderPathfinding to true.

  • You can explicitly disable deploying on cells of specified land types using IsSimpleDeployer.DisallowedLandTypes. Defaults to water,beach for units with Jumpjet or Hover locomotor with DeployToLand=true, none for others.

• In vanilla game only units with DeployingAnim were constrained to a specific deploy facing and it was not customizable per unit. DeployDir can be set to override this per unit (defaults to [AudioVisual] -> DeployDir for units with DeployingAnim, -1 otherwise), including using value of -1 to disable the facing restriction.

• Multiple new options for deploy animations:

  • DeployingAnims can be used instead of DeployingAnim (if both are set, DeployingAnims takes precedence) to define a list of direction-specific deploy animations to play. Largest power of 2 the number of listed animations falls to is used as number of directions/animations. Less than 8 animations listed results in only first listed one being used.

  • DeployingAnim.KeepUnitVisible determines if the unit is not hidden while the animation is playing.

  • DeployingAnim.ReverseForUndeploy controls whether or not the animation is played in reverse for undeploying.

  • DeployingAnim.UseUnitDrawer controls whether or not the animation is displayed in the unit’s palette and team colours or regular animation palette, including a potential custom palette.

In rulesmd.ini:

[SOMEVEHICLE]                               ; VehicleType
IsSimpleDeployer.ConsiderPathfinding=false  ; boolean
IsSimpleDeployer.DisallowedLandTypes=       ; List of LandTypes (none | clear | road | water | rock | wall | tiberium | beach | rough | ice | railroad | tunnel | weeds)
DeployDir=                                  ; Facing type (integers from 0-7 or -1)
DeployingAnims=                             ; List of AnimationTypes
DeployingAnim.KeepUnitVisible=false         ; boolean
DeployingAnim.ReverseForUndeploy=true       ; boolean
DeployingAnim.UseUnitDrawer=true            ; boolean

Make harvesters do addtional scan after unload

• In vanilla, miners will remember their current location when they reach full load and move to that location after unloading. This makes miners to gradually move deeper into the mine and ignore the closer minerals.

• Now you can have the miner search for the nearest mineral again after unloading. If a closer mineral is found, the miner will go to that location instead of the previously recorded location.

In rulesmd.ini:

[General]
HarvesterScanAfterUnload=false     ; boolean

[SOMEVEHICLE]                      ; VehicleType
HarvesterScanAfterUnload=          ; boolean, default to [General] -> HarvesterScanAfterUnload

Preserve Iron Curtain / Force Shield status on type conversion

Bugfix in action

• Iron Curtain status is now preserved by default when converting between TechnoTypes via DeploysInto / UndeploysInto. Force Shield status preservation is turned off by default.

  • This behavior can be turned on/off per-TechnoType and on global basis.

  • IronCurtain.Modifier / ForceShield.Modifier (whichever is applicable) is re-applied upon type conversion.

In rulesmd.ini:

[CombatDamage]
IronCurtain.KeptOnDeploy=true   ; boolean
ForceShield.KeptOnDeploy=false  ; boolean

[SOMETECHNO]                    ; VehicleType with DeploysInto or BuildingType with UndeploysInto
IronCurtain.KeptOnDeploy=       ; boolean, default to [CombatDamage] -> IronCurtain.KeptOnDeploy
ForceShield.KeptOnDeploy=       ; boolean, default to [CombatDamage] -> ForceShield.KeptOnDeploy

Retain target on movement command

• It is now possible for vehicles to retain their target when issued movement command by setting KeepTargetOnMove to true.

  • Note that no check is done whether or not the vehicle or the weapon can actually fire while moving, this is on modder’s discretion.

  • The target is automatically reset if the vehicle moves beyond the weapon’s range from the target.

• KeepTargetOnMove.Weapon determines the weapon to be used for range check. If set to -1, the game will select the weapon against the target by default logic.

  • It’s recommended to set it to a specific weapon for better performance, unless there’s a need to use multiple weapons for different targets.

• KeepTargetOnMove.NoMorePursuit controls whether the unit will restart chasing the target for attack when it stops again, otherwise it will clear the target when it moves away.

• KeepTargetOnMove.ExtraDistance can be used to modify the distance considered ‘out of range’ from the target (it is added to weapon range), negative values work to reduce the distance.

In rulesmd.ini:

[SOMEVEHICLE]                        ; VehicleType
KeepTargetOnMove=false               ; boolean
KeepTargetOnMove.Weapon=-1           ; integer, weapon slot index
KeepTargetOnMove.NoMorePursuit=true  ; boolean
KeepTargetOnMove.ExtraDistance=0     ; floating point value, distance in cells

Sinking behavior dehardcode

• In vanilla, whether a ship sinks when it dies on the water is determined by multiple settings of hardcoding. The speed of the sinking is hardcoded to 5 Leptons per frame.

• Now you can determine whether a ship sinks with a dedicated flag Sinkable, and use SinkSpeed to customize the speed at which the ship sinks.

• Sinkable.SquidGrab controls the behavior of a ship when it is killed by a squid. Set it to false to cause the ship to take a lethal damage instead of sinking directly at that time (and thus obey Sinkable settings).

In rulesmd.ini:

[SOMEVEHICLE]              ; VehicleType
Sinkable=                  ; boolean
SinkSpeed=5                ; integer, leptons per frame
Sinkable.SquidGrab=true    ; boolean

Stationary vehicles

• Setting VehicleType Speed to 0 now makes game treat them as stationary, behaving in very similar manner to deployed vehicles with IsSimpleDeployer set to true. Should not be used on buildable vehicles, as they won’t be able to exit factories.

Turret recoil

• Now you can use TurretRecoil to control units’ turret/barrel recoil effect when firing.

  • TurretTravel and BarrelTravel control the maximum recoil distance.

  • TurretRecoil.Suppress can prevent the weapon from producing this effect when firing.

In rulesmd.ini:

[SOMEVEHICLE]             ; VehicleType
TurretRecoil=no           ; boolean
TurretTravel=2            ; integer, pixels
TurretCompressFrames=1    ; integer, game frames
TurretHoldFrames=1        ; integer, game frames
TurretRecoverFrames=1     ; integer, game frames
BarrelTravel=2            ; integer, pixels
BarrelCompressFrames=1    ; integer, game frames
BarrelHoldFrames=1        ; integer, game frames
BarrelRecoverFrames=1     ; integer, game frames

[SOMEWEAPON]              ; WeaponType
TurretRecoil.Suppress=no  ; boolean

Unit Without Turret Always Turn To Target

• Now vehicles without turret will attempt to turn to the target while the weapon is cooling down, rather than after the weapon has cooled down, by setting NoTurret.TrackTarget to true.

In rulesmd.ini:

[General]
NoTurret.TrackTarget=false   ; boolean

[SOMEVEHICLE]                ; VehicleType
NoTurret.TrackTarget=        ; boolean, defaults to [General] -> NoTurret.TrackTarget

Voxel turret shadow

• Vehicle voxel turrets can now draw shadows if [AudioVisual] -> DrawTurretShadow is set to true. This can be overridden per VehicleType by setting TurretShadow in the vehicle’s artmd.ini section.

In rulesmd.ini:

[AudioVisual]
DrawTurretShadow=false  ; boolean

In artmd.ini:

[SOMEVEHICLE]   ; VehicleType
TurretShadow=   ; boolean

Customizable debris & meteor impact and warhead detonation behaviour

• The INI keys and behaviour is mostly identical to the equivalent behaviour available to regular animations. Main difference is that the keys must be listed in the VoxelAnim’s entry in rulesmd.ini, not artmd.ini.

Customizable debris trailer anim spawn delay

• You can now customize the generation interval of VoxelAnim’s trailer animation.

In rulesmd.ini:

[SOMEVOXELANIM]       ; VoxelAnimType
Trailer.SpawnDelay=2  ; integer, game frames

Allowing damage dealt to firer

• You can now allow warhead to deal damage (and apply damage-adjacent effects such as KillDriver and DisableWeapons/Sonar/Flash.Duration (Ares features)) on the object that is considered as the firer of the Warhead even if it does not have DamageSelf=true.

  • Note that effect of Psychedelic=true, despite being tied to damage will still fail to apply on the firer as it does not affect any objects belonging to same house as the firer, including itself.

In rulesmd.ini:

[SOMEWARHEAD]            ; WarheadType
AllowDamageOnSelf=false  ; boolean

Combat light customizations

• You can now set minimum detail level at which combat light effects are shown by setting [AudioVisual] -> CombatLightDetailLevel or CombatLightDetailLevel on Warhead.

• You can now set a percentage chance a combat light effect is shown on Warhead impact by setting CombatLightChance.

• Setting CLIsBlack to true on Warhead will now turn the flash black like on hitting an Iron Curtained object, irregardless of other color settings.

In rulesmd.ini:

[AudioVisual]
CombatLightDetailLevel=0  ; integer

[SOMEWARHEAD]             ; WarheadType
CombatLightDetailLevel=   ; integer, default to [AudioVisual] -> CombatLightDetailLevel
CombatLightChance=1.0     ; floating point value, percents or absolute (0.0-1.0)
CLIsBlack=false           ; boolean

Custom debris animations and additional debris spawn settings

• You can now use DebrisAnims to specify a list of debris animations to spawn instead of animations from [General] -> MetallicDebris when Warhead with MaxDebris > 0 and no DebrisTypes (VoxelAnims) listed is detonated.

• Debris.Conventional, if set to true, makes DebrisTypes or DebrisAnims only spawn if Warhead is fired on non-water cell.

In rulesmd.ini:

[SOMEWARHEAD]              ; WarheadType
DebrisAnims=               ; List of AnimationTypes
Debris.Conventional=false  ; boolean

Custom debris voxel animations limitation

• Now, the original DebrisMaximums can be used in conjunction with new DebrisMinimums to limit the quantity of DebrisTypes when DebrisTypes.Limit is enabled.

  • The default value of DebrisTypes.Limit is whether the number of DebrisMaximums is greater than (not equal to) 1 (for compatibility reasons).

In rulesmd.ini:

[SOMEWARHEAD]       ; WarheadType
DebrisTypes.Limit=  ; boolean
DebrisMaximums=     ; List of integers
DebrisMinimums=     ; List of integers

Customizable rocker amplitude

• The rocker amplitude of warheads with Rocker=yes used to be determined by Damage value of the weapon. You can now override it with fixed value and add a multiplier to it.

  • When both multiplier and override values are set - both are used.

In rulesmd.ini:

[SOMEWARHEAD]                   ; WarheadType
Rocker.AmplitudeMultiplier=1.0  ; floating point value, multiplier
Rocker.AmplitudeOverride=       ; integer

Customizable Warhead animation behaviour

• It is possible to make game play random animation from AnimList by setting AnimList.PickRandom to true. The result is similar to what EMEffect=true produces, however it comes with no side-effects (EMEffect=true prevents Inviso=true projectiles from snapping on targets, making them miss moving targets).

• If AnimList.CreateAll is set to true, all animations from AnimList are created, instead of a single anim based on damage or random if AnimList.PickRandom is set to true.

• If AnimList.CreationInterval is set to a value higher than 0, there will be that number of detonations of the Warhead before animations from AnimList will be created again. If the Warhead had a TechnoType firing it, this number is remembered by the TechnoType across all Warheads fired by it, otherwise it is shared between all detonations of same WarheadType period. This can be useful for things like Airburst with large spread where one might want uniform distribution of animations to appear but not on every detonation.

• AnimList.ScatterMin & AnimList.ScatterMax can be used to set a range in cells around which any created animations will randomly scatter around from the impact point.

• SplashList can be used to override animations displayed if the Warhead has Conventional=true and it hits water.

  • SplashList.PickRandom, SplashList.CreateAll, SplashList.CreationInterval and SplashList.Scatter(Min/Max) apply to these animations in same manner as the AnimList equivalents.

• • CreateAnimsOnZeroDamage, if set to true, makes it so that AnimList or SplashList animations are created even if the weapon that fired the Warhead deals zero damage.

• Setting Conventional.IgnoreUnits to true on Warhead with Conventional=true will make the Warhead detonate on non-underwater VehicleTypes on water tiles as if they are water tiles, instead of treating it as land. This determines whether to use AnimList or SplashList when hitting surface ships.

In rulesmd.ini:

[SOMEWARHEAD]                   ; WarheadType
AnimList.PickRandom=false       ; boolean
AnimList.CreateAll=false        ; boolean
AnimList.CreationInterval=0     ; integer
AnimList.ScatterMin=0.0         ; floating point value, distance in cells
AnimList.ScatterMax=0.0         ; floating point value, distance in cells
SplashList=                     ; List of AnimationTypes, default to [CombatDamage] -> SplashList
SplashList.PickRandom=false     ; boolean
SplashList.CreateAll=false      ; boolean
SplashList.CreationInterval=0   ; integer
SplashList.ScatterMin=0.0       ; floating point value, distance in cells
SplashList.ScatterMax=0.0       ; floating point value, distance in cells
CreateAnimsOnZeroDamage=false   ; boolean
Conventional.IgnoreUnits=false  ; boolean

Customizable Warhead trigger conditions

• AffectsBelowPercent and AffectsAbovePercent can be used to set the health percentage thresholds that target needs to be below/equal and/or above of for the Warhead to detonate. If target has zero health left this check is bypassed.

• If set to false, AffectsNeutral makes the warhead can’t damage or affect target that belongs to neutral house.

• If set to false, EffectsRequireVerses makes the Phobos-introduced warhead effects trigger even if it can’t damage the target because of it’s current ArmorType (e.g. 0% in Verses).

In rulesmd.ini:

[SOMEWARHEAD]               ; WarheadType
AffectsBelowPercent=1.0     ; floating point value, percents or absolute
AffectsAbovePercent=0.0     ; floating point value, percents or absolute
AffectsNeutral=true         ; boolean
EffectsRequireVerses=false  ; boolean

Customizing decloak on damaging targets

• You can now specify whether or not the warhead decloaks objects that are damaged by the warhead.

In rulesmd.ini:

[SOMEWARHEAD]               ; WarheadType
DecloakDamagedTargets=true  ; boolean

Customizing parasite

• Now you can specify which targets the parasite will culling them.

• Squid grapple anim is hardcoded to use SQDG in vanilla, Now you can choose it.

In rulesmd.ini:

[AudioVisual]
Parasite.GrappleAnim=             ; animation

[SOMEWARHEAD]                     ; WarheadType
Parasite.CullingTarget=infantry   ; List of Affected Target Enumeration (none|aircraft|infantry|units|all)
Parasite.GrappleAnim=             ; animation

Dehardcode the ZAdjust of warhead anim

• In vanilla, the animations generated by AnimList have a hard-coded ZAdjust=-15. Now you can customize it in the following ways.

  • If these flags are set to 0, the ZAdjust defined by the anim will be used.

In rulesmd.ini:

[AudioVisual]
WarheadAnimZAdjust=-15           ; Integer

[SOMEWARHEAD]                    ; WarheadType
AnimZAdjust=                     ; Integer, default to [AudioVisual] -> WarheadAnimZAdjust

Delay automatic attack on the controlled unit

• Now you can make the techno that has just been mind controlled not be automatically attacked by its original friendly forces for a period of time defined by MindControl.ThreatDelay on the mind control warhead.

  • This will not affect the manual selection of attacks and is useless with permanent mind control.

In rulesmd.ini:

[General]
MindControl.ThreatDelay=0     ; integer, game frames

[SOMEWARHEAD]                 ; WarheadType
MindControl.ThreatDelay=      ; integer, game frames, default to [General] -> MindControl.ThreatDelay

Nonprovocative Warheads

• You can now make Warheads behave in nonprovocative fashion. Warheads with Nonprovocative=true exhibit following behaviours:

  • They will not generate any EVA announcements upon hitting targets, be it for attacking ore miners, base buildings or ally base buildings.

  • They will not spring ‘attacked’ / ‘attacked by’ events. Note that if the Warhead deals actual damage, events that check for that can still be sprung.

  • They will not evoke defense response from AI players when used to attack base buildings, ToProtect=true TechnoTypes or members of TeamTypes with Whiner=true.

  • They will not evoke retaliation from TechnoTypes hit by the Warhead.

In rulesmd.ini:

[SOMEWARHEAD]         ; WarheadType
Nonprovocative=false  ; boolean

Restricting screen shaking to current view

• You can now specify whether or not the warhead can only shake screen (ShakeX/Ylo/hi) if it is detonated while visible on current screen view.

In rulesmd.ini:

[SOMEWARHEAD]       ; WarheadType
ShakeIsLocal=false  ; boolean

AmbientDamage customizations

• You can now specify separate Warhead used for AmbientDamage via AmbientDamage.Warhead or make it never apply to weapon’s main target by setting AmbientDamage.IgnoreTarget to true.

In rulesmd.ini:

[SOMEWEAPON]                      ; WeaponType
AmbientDamage.Warhead=            ; WarheadType
AmbientDamage.IgnoreTarget=false  ; boolean

Can attack allies

• Weapons now support AttackFriendlies and AttackCursorOnFriendlies. They override the firer’s AttackFriendlies and AttackCursorOnFriendlies.

In rulesmd.ini:

[SOMEWEAPON]                ; WeaponType
AttackFriendlies=           ; boolean
AttackCursorOnFriendlies=   ; boolean

Charge turret delays

• It is now possible to customize the delay of IsChargeTurret=true unit turret animation per weapon, per Burst shot instead of defaulting to weapon’s rearm timer (ROF, Burst.Delays etc). Delay in the list corresponding to burst shot is used, or last delay listed if number of listed values is lower than the current burst index. Delay of 0 or less means previous delay, if applicable, is not restarted.

  • Note that unlike the default rearm timer that uses ROF, any modifiers are not applied to explicitly set charge turret delays.

In rulesmd.ini:

[SOMEWEAPON]          ; WeaponType
ChargeTurret.Delays=  ; List of integers - game frames

Customizable disk laser radius

• You can now set disk laser animation radius using a new tag.

In rulesmd.ini:

[SOMEWEAPON]          ; WeaponType
DiskLaser.Radius=240  ; integer
; 240 is the default saucer disk radius

Customizable ROF random delay

• By default weapon ROF has a random delay of 0 to 2 frames added to it. This random delay is now customizable, globally and on per-WeaponType basis.

In rulesmd.ini:

[CombatDamage]
ROF.RandomDelay=0,2  ; integer - single or comma-sep. range (game frames)

[SOMEWEAPON]         ; WeaponType
ROF.RandomDelay=     ; integer - single or comma-sep. range (game frames), default to [CombatDamage] -> ROF.RandomDelay

Customizing whether passengers are kicked out when an aircraft fires

• You can now customize whether aircraft will forcefully eject passengers (vanilla behavior) or fire its weapon when attempting to fire.

In rulesmd.ini:

[SOMEWEAPON]            ; WeaponType
KickOutPassengers=true  ; boolean

Disable FireOnce resetting infantry sequence

• It is now possible to disable FireOnce=true weapon resetting infantry sequences after firing via FireOnce.ResetSequence. Target will be forgotten like before, the firing sequence will simply continue playing after firing if there are any frames left.

In rulesmd.ini:

[SOMEWEAPON]                 ; WeaponType
FireOnce.ResetSequence=true  ; boolean

Electric bolt customizations

EBolt customization utilized for different Tesla bolt weapon usage (RA2: Reboot)

• You can now specify individual bolts you want to disable for IsElectricBolt=true weapons. Note that this is only a visual change.

• By default IsElectricBolt=true effect draws a bolt with 8 arcs. This can now be customized per WeaponType with Bolt.Arcs. Value of 0 results in a straight line being drawn.

• Bolt.Duration can be specified to explicitly set the overall duration of the visual electric bolt effect. Only values in range of 1 to 31 are accepted, values outside this range are clamped into it.

• Bolt.FollowFLH can be used to override the default behaviour where the electric bolt source coordinates change to match the unit’s firing coord on every frame (making it follow unit’s movement, rotation etc). Defaults to true on vehicles, false for everything else.

In rulesmd.ini:

[SOMEWEAPON]           ; WeaponType
Bolt.Disable1=false    ; boolean
Bolt.Disable2=false    ; boolean
Bolt.Disable3=false    ; boolean
Bolt.Arcs=8            ; integer
Bolt.Duration=17       ; integer, game frames
Bolt.FollowFLH=        ; boolean

Single-color lasers

Comparison of IsSingleColor=yes lasers with higher thickness to regular ones (RA2: Reboot)

• You can now set laser to draw using only LaserInnerColor by setting IsSingleColor, in same manner as IsHouseColor lasers do using player’s team color. These lasers respect laser thickness. Note that this is not available on prism support weapons.

In rulesmd.ini:

[SOMEWEAPON]         ; WeaponType
IsSingleColor=false  ; boolean