ModEnc² - User contributions [en]

Adding A Tank Drop

2008-03-23T12:52:34Z

91.66.51.170:

You thought you needed RockPatch for this feature? Well, not exactly. Though it won't be fired as a superweapon, the following instructions will help you create an aircraft that can load vehicles and drop them on parachutes:

First, you make yourself an aircraft. The stats are up to you, but it needs to have:

...
[[Primary]]=ParadropWeapon ; or whatever name you want to give to this dummy weapon
[[Carryall]]=yes
[[Ammo]]=1
...

Now, when targeting, the weapon this aircraft mounts will be considered in the same way a normal weapon would. Meaning that you can (in RA2 and YR in combination with the [[Fighter]] flag on the aircraft itself), modify the dropping behaviour, just in the same way as explained in the [[Adding Paratroopers to TS]] tutorial. Just to be safe, the weapon should have a non-damaging warhead, though.

Now, to use your tank drop, simply pick up a vehicle with your aircraft, then attack any enemy unit or building, or force-fire on the ground. Instead of firing your weapon, the aircraft will drop the vehicle on a parachute.

This supposedly works in both TS / FS and RA2 / YR, but in RA2 / YR, you might rather use an AircraftType with [[SizeLimit]] set large enough to accomodate tanks and in TS / FS, there's a little bug to it. Do you remember how in TS, the parachute is drawn in the center of an infantry selection bracket when dropping infantry, instead of above it? Well, first the good news: when dropping vehicles, the parachute will be drawn correctly above the dropping vehicle. The bad news are that the selection bracket will ''still'' focus on the parachute. The voxel of the vehicle in question will partially be drawn ''underneath'' the selection bracket, and it will stay that way once the vehicle has landed, meaning the engine will draw the voxel slightly underneath the location where it actually exists (the selection bracket is the object considered to be moving, for example, which will cause the voxel to be drawn inside buildings whne moving next to them, for example. The selection bracket will also be the target for enemy units to fire upon, not the voxel itself...). Picking the vehicle up with a Carryall and setting it down again has been reported to reverse the effect, though.

[[Category:Tutorials]]

Agent

2008-03-20T10:29:40Z

91.66.51.170:

{{flag
|name={{PAGENAME}}
|files=rules(md).ini
|values={{Values|booleans}}
|default=no
|types=InfantryTypes
|ts=yes
|fs=yes
|ets=yes
|ra2=yes
|yr=yes
|rp=yes}}

__TOC__

==In TS==
Can be set to 'yes' or 'no'. An InfantryType with this and [[Infiltrate]] set to 'yes' gain the ability to enter enemy structures to various effects:

If an ''Agent'' enters a...
* Building with [[Factory]]= set to any valid type, the cameo of whatever object the owning player is currently constructing will be displayed to the infiltrating player above the selected building whenever the infiltrated building is selected by the infiltrating player. The cameo will however be displayed in a wrong [[palette]] (building palette?).
* Building with [[Radar]] set to 'yes', the infiltrating player will not only see all terrain the owner of the infiltrated building has yet discovered, but will also see all terrain that player discovers ''after'' his building was infiltrated. Through a bug in this logic, the terrain that is discovered by other players will also be seen.
* Refinery - ''no effect (?)''
* Building with [[Power]] set to a number greater than "0" - Shows the power levels of the infiltrated player.
* Tech Center - ''no effect (?)''

In TS, this is only used on the Chameleon Spy, which is only available to the player in one single player mission in the unmodded game. in this mission, the flag does not show its entire potential, because the mission objective is the infiltration of only one structure. The effect of the flag is actually much more extensive and might hint to a feature that the game designers possibly planned, but cut from the final game.

Note that this logic may cause IEs when an InfantryType is an [[Agent]] and [[Engineer]], [[C4]] bomber or [[Thief]] at the same time, though this needs further testing. The '''Thief''' is the less likely to cause IEs in this respect.

==In RA2==
{{DeeZireInclusion}} 
Can be set to 'yes' or 'no' and determines if this InfantryType has the properties of a Spy when it enters specific structures. Also requires Infiltrate=yes set on the unit. Note that this applies to the Spy logic from Red Alert 2 (not the logic from the original Red Alert) and thus is dependant upon the structure that the Spy enters. NOTE: a unit cannot be an Agent= and an Assaulter= - only one or the other.

Agent

2008-03-19T21:09:14Z

91.66.51.170:

==In TS==
Can be set to 'yes' or 'no'. An InfantryType with this and [[Infiltrate]] set to 'yes' gain the ability to enter enemy structures to various effects:

If an ''Agent'' enters a...
* Building with [[Factory]]= set to any valid type, the cameo of whatever object the owning player is currently constructing will be displayed to the infiltrating player above the selected building whenever the infiltrated building is selected by the infiltrating player. The cameo will however be displayed in a wrong [[palette]] (building palette?).
* Building with [[Radar]] set to 'yes', the infiltrating player will not only see all terrain the owner of the infiltrated building has yet discovered, but will also see all terrain that player discovers ''after'' his building was infiltrated.
* Refinery - ''no effect (?)''
* Power Plant - ''no effect (?)''
* Tech Center - ''no effect (?)''

In TS, this is only used on the Chameleon Spy, which is only available to the player in one single player mission in the unmodded game. in this mission, the flag does not show its entire potential, because the mission objective is the infiltration of only one structure. The effect of the flag is actually much more extensive and might hint to a feature that the game designers possibly planned, but cut from the final game.

Note that this logic may cause IEs when an InfantryType is an [[Agent]] and [[Engineer]], [[C4]] bomber or [[Thief]] at the same time, though this needs further testing. The '''Thief''' is the less likely to cause IEs in this respect.

==In RA2==
{{DeeZireInclusion}} 
Can be set to 'yes' or 'no' and determines if this InfantryType has the properties of a Spy when it enters specific structures. Also requires Infiltrate=yes set on the unit. Note that this applies to the Spy logic from Red Alert 2 (not the logic from the original Red Alert) and thus is dependant upon the structure that the Spy enters. NOTE: a unit cannot be an Agent= and an Assaulter= - only one or the other.

Agent

2008-03-19T21:03:43Z

91.66.51.170: /* In TS */

==In TS==
Can be set to 'yes' or 'no'. An InfantryType with this and [[Infiltrate]] set to 'yes' gain the ability to enter enemy structures to various effects:

If an ''Agent'' enters a...
* Building with [[Factory]]= set to any valid type, the cameo of whatever object the owning player is [[currently constructing will be displayed to the infiltrating player above the selected building whenever the infiltrated building is selected by the infiltrating player. The cameo will however be displayed in a wrong [[palette]] (building palette?).
* Building with [[Radar]] set to 'yes', the infiltrating player will not only see all terrain the owner of the infiltrated building has yet discovered, but will also see all terrain that player discovers ''after'' his building was infiltrated.
* Refinery - ''no effect (?)''
* Power Plant - ''no effect (?)''
* Tech Center - ''no effect (?)''

In TS, this is only used on the Chameleon Spy, which is only available to the player in one single player mission in the unmodded game. in this mission, the flag does not show its entire potential, because the mission objective is the infiltration of only one structure. The effect of the flag is actually much more extensive and hints to a feature that the game designers possibly planned, but cut from the final game.

Note that this logic may cause IEs when an InfantryType is an [[Agent]] and [[Engineer]], [[C4]] bomber or [[Thief]] at the same time, though this needs further testing. The '''Thief''' is the less likely to cause IEs in this respect.

==In RA2==
{{DeeZireInclusion}} 
Can be set to 'yes' or 'no' and determines if this InfantryType has the properties of a Spy when it enters specific structures. Also requires Infiltrate=yes set on the unit. Note that this applies to the Spy logic from Red Alert 2 (not the logic from the original Red Alert) and thus is dependant upon the structure that the Spy enters. NOTE: a unit cannot be an Agent= and an Assaulter= - only one or the other.

Agent

2008-03-19T21:02:10Z

91.66.51.170:

==In TS==
Can be set to 'yes' or 'no'. An InfantryType with this and [[Infiltrate]] set to 'yes' gain the ability to enter enemy structures to various effects:

If an ''Agent'' enters a...
* Building with [[Factory]]= set to any valid type, the cameo of whatever object the owning player is [[currently constructing will be displayed to the infiltrating player above the selected building whenever the infiltrated building is selected by the infiltrating player. The cameo will however be displayed in a wrong [[palette]] (building palette?).
* Building with [[Radar]] set to 'yes', the infiltrating player will not only see all terrain the owner of the infiltrated building has yet discovered, but will also see all terrain that player discovers ''after'' his building was infiltrated.
* Refinery - ''no effect (?)''
* Power Plant - ''no effect (?)''
* Tech Center - ''no effect (?)''

In TS, this is only used on the Chameleon Spy, which is only available to the player in one single player mission in the unmodded game. in this mission, the flag does not show its entire potential, because the mission objective is the infiltration of only one structure. The effect of the flag is actually much more extensive and hints to a feature that the game designers possibly planned, but cut from the final game.

Note that this logic may cause IEs when an InfantryType is an [[Agent]] and [[Engineer]], [[C4]] bomber or [[Thief]] at the same time, though this needs further testing. Because of how the TS engine works, the '''Thief''' is the less likely to cause IEs in this respect (low ''parse_p'', if I'm not mistaken).

==In RA2==
{{DeeZireInclusion}} 
Can be set to 'yes' or 'no' and determines if this InfantryType has the properties of a Spy when it enters specific structures. Also requires Infiltrate=yes set on the unit. Note that this applies to the Spy logic from Red Alert 2 (not the logic from the original Red Alert) and thus is dependant upon the structure that the Spy enters. NOTE: a unit cannot be an Agent= and an Assaulter= - only one or the other.

Speed

2008-03-19T11:11:05Z

91.66.51.170:

{{Flag
|name={{PAGENAME}}
|files={{Categ|Rules(md).ini}}
|values={{values|float}}
|special=
|default=none
|types={{Categ|JumpjetControls}}, {{Categ|InfantryTypes}}, {{Categ|VehicleTypes}}, {{Categ|AircraftTypes}}, {{Categ|BuildingTypes}}, {{Categ|WeaponTypes}}
|ra=yes
|cs=yes
|am=yes
|ts=yes
|fs=yes
|ets=yes
|ra2=yes
|yr=yes
|rp=yes
}}

== On ObjectTypes ==

Specifies the movement speed of this ObjectType.

== On WeaponTypes ==
Specifies the speed the weapon's projectile will have when fired. This only works on projectiles with a [[ROT]] larger than 0.

== On JumpJet Controls ==

Specifies the default speed of JumpJet units. Individual units can override this using the {{TTL|JumpjetSpeed}} flag.

== In Powerups ==

{{Flag
|name={{PAGENAME}}
|files={{Categ|Rules(md).ini}}
|values={{values|special}}
|special=
|default=none
|types={{Categ|Powerups}}
|ra=yes
|cs=yes
|am=yes
|ts=yes
|fs=yes
|ets=yes
|ra2=yes
|yr=yes
|rp=yes
}}

See [{{TTL|Powerups}}].

Who crushes whom

2008-02-22T21:24:42Z

91.66.51.170:

This page details how the crushing system works. The table shows whether a defender can be crushed by an attacker, depending on how the flags {{TTL|Crusher}}, {{TTL|Crushable}}, {{TTL|OmniCrusher}} and {{TTL|OmniCrushResistant}} are set.

<div align="center">
{| style='text-align: center;'
|+ '''Can Defender be crushed by Attacker?'''
|-
|rowspan=3 |
|colspan=2 |
!colspan=4 style="border: 1px solid #000000;"|Defender
|-
|colspan=2 |
|colspan=2 |{{TTL|Crushable}}
|colspan=2 |{{TTL|OmniCrushResistant}}
|-
|colspan=2 |
|style="background:#e5e5e5;"|{{Tt|yes}}
|style="background:#e5e5e5;"|{{Tt|no}}
|style="background:#e5e5e5;"|{{Tt|yes}}
|style="background:#e5e5e5;"|{{Tt|no}}
|-
!rowspan=4 style="border: 1px solid #000000;"|  A   t t a c k e r
|rowspan=2 style='vertical-align: middle;' |{{TTL|Crusher}}
|style="background:#e5e5e5;"|{{Tt|yes}}
|style="background:#F0F0F0;"|{{Y}}
|style="background:#F0F0F0;"|{{N}}
|style="background:#F0F0F0;"|{{N}}
|style="background:#F0F0F0;"|
|-
|style="background:#e5e5e5"|{{Tt|no}}
|style="background:#F0F0F0;"|{{N}}
|style="background:#F0F0F0;"|{{N}}
|style="background:#F0F0F0;"|{{N}}
|style="background:#F0F0F0;"|{{N}}
|-
|rowspan=2 |{{TTL|OmniCrusher}}
|style="background:#e5e5e5;"|{{Tt|yes}}
|style="background:#F0F0F0;"|{{Y}}
|style="background:#F0F0F0;"|{{Y}}
|style="background:#F0F0F0;"|{{N}}
|style="background:#F0F0F0;"|{{Y}}
|-
|style="background:#e5e5e5;"|{{Tt|no}}
|style="background:#F0F0F0;"|
|style="background:#F0F0F0;"|{{N}}
|style="background:#F0F0F0;"|{{N}}
|style="background:#F0F0F0;"|{{N}}
|}

:OmniCrusher and OmniCrushResistant are only available in [[Yuri's Revenge]].
</div>

Empty cells signal that one property does not influence the other, specifically:
*{{tt|Crusher=yes}} checks for {{tt|Crushable}} - it doesn't care whether the target can be crushed by OmniCrushers.
*Just because a target is not an OmniCrusher, doesn't mean it can't crush a {{tt|Crushable=yes}} - that's determined by {{tt|Crusher}}.

'''The flags in detail:'''
*{{TTL|Crusher}} determines if this VehicleType can crush objects.
*{{TTL|Crushable}} determines if this object can be crushed by Crushers.
:''Only if the Attacker is {{tt|Crusher=yes}} and the Defender is {{tt|Crushable=yes}}, the crushing can happen.''
*{{TTL|OmniCrusher}}, if enabled, allows the VehicleType to crush objects who are set {{tt|Crushable=no}}.
*{{TTL|OmniCrushResistant}}, if enabled, prevents all crushing.

*''Note that setting the flag {{tt|Train&#;yes}} on a {{tt|UnitType}} in '''[[Tiberian Sun]]''' allows that unit to destroy ("crush") '''any''' unit, and even buildings, it comes in contact with. However, this effect is difficult to use in-game and requires minutious commanding of the unit in order to crush buildings, as there is no corresponding {{TTL|MovementZone}} to this behaviour and any {{TTL|MovementZone}} will try to avoid contact with buildings. Wether this works on other types (infantry, aircraft) and in RA2 needs further testing. It has also not been verified that such a unit can also crush walls and objects which are {{TTL|Immune}}. It is likely, if the flag is valid and parsed in RA2, none of the aforementioned resistance flags would protect from destruction through such a contact.''

[[Category: General Editing Information]]

Who crushes whom

2008-02-22T21:23:16Z

91.66.51.170:

This page details how the crushing system works. The table shows whether a defender can be crushed by an attacker, depending on how the flags {{TTL|Crusher}}, {{TTL|Crushable}}, {{TTL|OmniCrusher}} and {{TTL|OmniCrushResistant}} are set.

<div align="center">
{| style='text-align: center;'
|+ '''Can Defender be crushed by Attacker?'''
|-
|rowspan=3 |
|colspan=2 |
!colspan=4 style="border: 1px solid #000000;"|Defender
|-
|colspan=2 |
|colspan=2 |{{TTL|Crushable}}
|colspan=2 |{{TTL|OmniCrushResistant}}
|-
|colspan=2 |
|style="background:#e5e5e5;"|{{Tt|yes}}
|style="background:#e5e5e5;"|{{Tt|no}}
|style="background:#e5e5e5;"|{{Tt|yes}}
|style="background:#e5e5e5;"|{{Tt|no}}
|-
!rowspan=4 style="border: 1px solid #000000;"|  A   t t a c k e r
|rowspan=2 style='vertical-align: middle;' |{{TTL|Crusher}}
|style="background:#e5e5e5;"|{{Tt|yes}}
|style="background:#F0F0F0;"|{{Y}}
|style="background:#F0F0F0;"|{{N}}
|style="background:#F0F0F0;"|{{N}}
|style="background:#F0F0F0;"|
|-
|style="background:#e5e5e5"|{{Tt|no}}
|style="background:#F0F0F0;"|{{N}}
|style="background:#F0F0F0;"|{{N}}
|style="background:#F0F0F0;"|{{N}}
|style="background:#F0F0F0;"|{{N}}
|-
|rowspan=2 |{{TTL|OmniCrusher}}
|style="background:#e5e5e5;"|{{Tt|yes}}
|style="background:#F0F0F0;"|{{Y}}
|style="background:#F0F0F0;"|{{Y}}
|style="background:#F0F0F0;"|{{N}}
|style="background:#F0F0F0;"|{{Y}}
|-
|style="background:#e5e5e5;"|{{Tt|no}}
|style="background:#F0F0F0;"|
|style="background:#F0F0F0;"|{{N}}
|style="background:#F0F0F0;"|{{N}}
|style="background:#F0F0F0;"|{{N}}
|}

:OmniCrusher and OmniCrushResistant are only available in [[Yuri's Revenge]].
</div>

Empty cells signal that one property does not influence the other, specifically:
*{{tt|Crusher=yes}} checks for {{tt|Crushable}} - it doesn't care whether the target can be crushed by OmniCrushers.
*Just because a target is not an OmniCrusher, doesn't mean it can't crush a {{tt|Crushable=yes}} - that's determined by {{tt|Crusher}}.

'''The flags in detail:'''
*{{TTL|Crusher}} determines if this VehicleType can crush objects.
*{{TTL|Crushable}} determines if this object can be crushed by Crushers.
:''Only if the Attacker is {{tt|Crusher=yes}} and the Defender is {{tt|Crushable=yes}}, the crushing can happen.''
*{{TTL|OmniCrusher}}, if enabled, allows the VehicleType to crush objects who are set {{tt|Crushable=no}}.
*{{TTL|OmniCrushResistant}}, if enabled, prevents all crushing.

*''Note that setting the flag {{TTL|Train}} on a {{TTL|UnitType}} in '''[[Tiberian Sun]]''' allows that unit to destroy ("crush") '''any''' unit, and even buildings, it comes in contact with. However, this effect is difficult to use in-game and requires minutious commanding of the unit in order to crush buildings, as there is no corresponding {{TTL|MovementZone}} to this behaviour and any {{TTL|MovementZone}} will try to avoid contact with buildings. Wether this works on other types (infantry, aircraft) and in RA2 needs further testing. It has also not been verified that such a unit can also crush walls and objects which are {{TTL|Immune}}. It is likely, if the flag is valid and parsed in RA2, none of the aforementioned resistance flags would protect from destruction through such a contact.''

[[Category: General Editing Information]]

Adding An Airstrike To TS

2008-02-16T21:20:00Z

91.66.51.170:

==Morpher's foundation...==

This is a relatively simple method of making an airstrike.
However there are obviously good things and bad things.The only bad thing is,is that the plane can't be shot down.I will supply you with some template shps to use (bear in mind there not perfect).

First of all you need to add the following to your rules.ini

I used a chemical missile to base this off.

; Chem weapon.
[ChemicalSpecial]
Name=Air Strike
IsPowered=true
RechargeVoice=
ChargingVoice=
ImpatientVoice=
SuspendVoice=
RechargeTime=
Type=AttackWaypoint
SidebarImage=MltiIcon
Action=AttackWaypoint ---nicer target icon
WeaponType=ChemLauncher --- nothing special there just a name change
and stopped it needing weeds.

This is the weapon that we will edit orignally from the chemical missile

; Chemical missile launcher
[ChemLauncher]
Damage=0
ROF=1 ; 0
Range=6
Projectile=Invisible
Speed=35 -------depending on the speed you could make it have a delay or make it longer
for the plane to reach its destination
Report=none

your warhead for the airstrike

; Air Strike Warhead
[STRIKE]
Spread=3
Wall=no
Wood=no
Rocker=no
Verses=1%,1%,1%,1%,1%
Conventional=no
InfDeath=3
AnimList=BOMBPAS
ProneDamage=0%

Thats the rules done.

Now we move onto to art.ini

Simply add the following

As I said earlier I have supplied templates for this to work

[BOMBPAS] ----plane flying over dropping bombs/mines
Normalized=yes
Translucent=no
AltPalette=yes
Rate=370
Next=SEXPB

[SEXPB] --- 1st bomb going off (starts from the left on this tut)
Translucent=yes
UseNormalLight=yes
Report=EXPNEW13
Damage=30
Crater=yes
Scorch=yes
Rate=900
Next=SEXPB2

[SEXPB2] --- 2nd bomb
Translucent=yes
UseNormalLight=yes
Report=EXPNEW13
Crater=yes
Damage=30
Scorch=yes
Rate=900
Next=SEXPB3

[SEXPB3] --- 3rd bomb
Translucent=yes
UseNormalLight=yes
Report=EXPNEW13
Crater=yes
Damage=30
Scorch=yes
Rate=900
Next=SEXPB4

[SEXPB4] --- 4th bomb
Translucent=yes
UseNormalLight=yes
Report=EXPNEW13
Crater=yes
Scorch=yes
Damage=30
Rate=900
Next=SEXPB5

[SEXPB5] --- 5th bomb
Translucent=yes
UseNormalLight=yes
Report=EXPNEW13
Crater=yes
Scorch=yes
Damage=30
Rate=900
Next=SEXPB6

[SEXPB6] -- 6th bomb
Translucent=yes
UseNormalLight=yes
Report=EXPNEW13
Crater=yes
Damage=30
Scorch=yes
Rate=900

You can make each indivual bomb more powerful than the last,or just change all of their damages to the same.30 damage is a weak damage amount and the explosions occur in different places,you may wish to increase the damage.

Also remember the building you wish this to be triggered by or effectively come from must have NukeSilo=yes.

Enjoy this.

[[Media:Airstrike.zip|Airstrike tools]]

== ...and Millennium's extension ==

The method of using an animation containing a passing plane can also be used via another method to create an airstrike. Here, the plane needs the flag <tt>[[IsMeteor]]=yes</tt> and a high maximum X velocity with a minimal Y velocity. The <tt>[[Trailer]]</tt> is set to another animation, which is the acctual bomb. This bomb animation is set to be a meteor as well, anc can be copied right from METLARGE or METSMALL, however, both the image and damage should be revised.

[[Category:Tutorials]]
[[Category:TS]]

Cluster

2008-02-16T19:08:51Z

91.66.51.170:

{{Flag
|name=Cluster
|files={{Categ|Rules(md).ini}}
|values=Unsigned integers
|default=0
|types={{Categ|Projectile|Projectiles}}
|ts=yes
|fs=yes
|ets=yes
|ra2=yes
|yr=yes
|rp=yes
}}

This flag defines the amount of <tt>[[AirburstWeapon]]=</tt> shots to fire if the projectile has <tt>[[Airburst]]=yes</tt> set. With no <tt>[[AirburstWeapon]]=</tt> set, this defines the number of seperate explosions caused when the projectile hits. The explosions are spread around the point of impact.

''Do these explosions each account for full damage, or is the Damage= divided by Cluster=? And what is the spread pattern?''