The problem I'm having: I'm unable to make the launchers for the custom missiles obey the structure-only targeting rules.
So, how would I make my custom missiles inherit their targeting rules from the 'structure-only' verses rules (so the launchers can only be ordered to attack structures and not units), while also generating the explosion that would harm infantry/vehicles? QUICK_EDIT
Custom missiles don't inherit any targeting rules from anything. Targeting is done by the missile launcher unit, not the missiles. You're looking at the wrong unit here. QUICK_EDIT
Custom missiles don't inherit any targeting rules from anything. Targeting is done by the missile launcher unit, not the missiles. You're looking at the wrong unit here.
Would I be creating 3 new 'launcher weapons' with their own warheads for those 3 units, then? QUICK_EDIT
Yes, you need new launcher weapons that can only target buildings.
Okay, should be simple enough. And just to be sure I'm understanding this properly:
1. The 'launcher weapon' is only handling targeting, and not the actual damage-dealing, correct?
2. I still need to make a 'launcher warhead' whose only purpose is to dictate what the launcher is capable of targeting, correct?
3. Assuming that the answer to the above two questions are both 'yes': Does that mean that, even if the missile warheads could damage 'anything', they would still be limited to only targeting and firing upon whatever the launcher weapon warheads were set to (while still being able to inflict 'splash damage' to the other targets)? QUICK_EDIT
If all launchers need to behave the same, then simply make one warhead, say [LauncherNoUnit], and assign it Verses=0%,0%,0%,0%,0%,0%,100%,100%,100%,0%,0%.
Then change all your launcher weapons, which I believe are [V3Launcher], [DredLauncher], and [CruiseLauncher] and assign Warhead=LauncherNoUnit.
That would basically be it. And yes, the launcher weapon does no damage, and only determines launch targeting. The warhead which is responsible for dealing the actual damage is determined by tags in [CombatDamage], namely these:
Code:
[CombatDamage]
...
V3Warhead=V3WH ; this is the warhead on a V3 Rocket
DMislWarhead=DMISLWH ; this is the warhead on a DredMissile
V3EliteWarhead=V3EWH ; this is the warhead on a V3 Rocket when the launcher is elite
DMislEliteWarhead=DMISLEWH ; this is the warhead on a DredMissile when the launcher is elite
CMislWarhead=CMISLWH ; this is the warhead on a DredMissile
CMislEliteWarhead=CMISLEWH ; this is the warhead on a DredMissile when the launcher is elite
So yes, even though your launcher can only target buildings, as long as you leave these warheads untouched, nothing will change about their damage properties. _________________ Formerly WoRmINaToR. I've created a new account to update to the name I've been using everywhere else for the last several years. QUICK_EDIT
If all launchers need to behave the same, then simply make one warhead, say [LauncherNoUnit], and assign it Verses=0%,0%,0%,0%,0%,0%,100%,100%,100%,0%,0%.
Then change all your launcher weapons, which I believe are [V3Launcher], [DredLauncher], and [CruiseLauncher] and assign Warhead=LauncherNoUnit.
That would basically be it. And yes, the launcher weapon does no damage, and only determines launch targeting. The warhead which is responsible for dealing the actual damage is determined by tags in [CombatDamage], namely these:
Code:
[CombatDamage]
...
V3Warhead=V3WH ; this is the warhead on a V3 Rocket
DMislWarhead=DMISLWH ; this is the warhead on a DredMissile
V3EliteWarhead=V3EWH ; this is the warhead on a V3 Rocket when the launcher is elite
DMislEliteWarhead=DMISLEWH ; this is the warhead on a DredMissile when the launcher is elite
CMislWarhead=CMISLWH ; this is the warhead on a DredMissile
CMislEliteWarhead=CMISLEWH ; this is the warhead on a DredMissile when the launcher is elite
So yes, even though your launcher can only target buildings, as long as you leave these warheads untouched, nothing will change about their damage properties.
This will be very useful for me to remember. I appreciate the assistance.
I've been making 'custom clones' of the default missiles anyway though, mostly because I wanted to leave the defaults in place as a 'fallback option'; it helps to have default numbers as a reference point, at least for me.
But yeah. I might just get hooked on Ares-type modding, at this rate. Thank you very much! QUICK_EDIT
One quick note as I look closer at your code, a few things stick out:
You have both Missile.Warhead and Missile.Weapon defined. You should only use one or the other. Both are used for the same thing: they are what gets detonated when the rocket hits its target, and are intended to be the thing that actually causes damage.
The Ares documentation doesn't specify which one takes precedence, but I assume the weapon does. This would override your Missile.Warhead and Missile.Damage settings. In your case, I would recommend simply removing the weapon entirely, delete the tag from your missile and delete all of this code as you don't need it:
Code:
; the infantry/vehicle-only 'explosion' weapons
[V3Explosion]
Damage=1
Projectile=InvisibleHigh
Warhead=V3ExplosionWH
In fact, I would delete your other warheads as well and start from scratch, copying from V3WH and tweaking values to your liking.
And Ares modding is a lot of fun! Hope you get hooked, lots of possibilities _________________ Formerly WoRmINaToR. I've created a new account to update to the name I've been using everywhere else for the last several years. QUICK_EDIT
One quick note as I look closer at your code, a few things stick out:
You have both Missile.Warhead and Missile.Weapon defined. You should only use one or the other. Both are used for the same thing: they are what gets detonated when the rocket hits its target, and are intended to be the thing that actually causes damage.
The Ares documentation doesn't specify which one takes precedence, but I assume the weapon does. This would override your Missile.Warhead and Missile.Damage settings. In your case, I would recommend simply removing the weapon entirely, delete the tag from your missile and delete all of this code as you don't need it:[code]; the infantry/vehicle-only 'explosion' weapons
In fact, I would delete your other warheads as well and start from scratch, copying from V3WH and tweaking values to your liking.
Way ahead of ya there; I removed the redundant entries already.
Sir Prize wrote:
And Ares modding is a lot of fun! Hope you get hooked, lots of possibilities
The mod I'm working on atm, aims to address some of the shortcomings of the vanilla game. Like how units would not auto-target nearby enemy structures, if said structures were unarmed (such as power plants; I actually managed to fix that problem already).
Additionally, the mod aims to crank up the dial on what C&C games did best; massed RTS combat.
With the missile problem solved, there's really only 1 problem left to address: Figuring out how to make Harriers and Black Eagles obey 'attack-move' commands, reducing the amount of sheer micro-management required to get full use out of them.
Not sure if that's an extra feature Ares has added yet (or plans on adding, sometime down the road).
If not, then the only 'workaound' I've been able to think of so far, is making a 'launcher weapon', attaching it to a structure, giving it infinite range, and making it spawn Harriers/Black Eagles. It's the same targeting logic that allows Aircraft Carriers to execute an attack-move command via launching their Hornet drones. QUICK_EDIT
The mod I'm working on atm, aims to address some of the shortcomings of the vanilla game. Like how units would not auto-target nearby enemy structures, if said structures were unarmed (such as power plants; I actually managed to fix that problem already).
Good stuff, though a word of caution on that: RA2 doesn't have the nice logic like StarCraft et. al. where a unit auto-attacking a structure will stop and target a unit if it comes within range. This can lead to undesired behavior where your units focus on structures and get killed, when they should really be focusing on the units shooting at them. I did this in my mod once upon a time but it got quite annoying after a while so I removed it.
Quote:
With the missile problem solved, there's really only 1 problem left to address: Figuring out how to make Harriers and Black Eagles obey 'attack-move' commands, reducing the amount of sheer micro-management required to get full use out of them.
Unfortunately Ares doesn't have this logic as far as I am aware. Fixes to aircraft behavior like this have been long-requested features since the very early days of 0.1, but they were never implemented due to the sheer volume of other feature requests. Official Ares development has been slow as of version 2.0p1, so I wouldn't hold your breath for this feature. You can ask AlexB though _________________ Formerly WoRmINaToR. I've created a new account to update to the name I've been using everywhere else for the last several years. QUICK_EDIT
Use waypoints and give your aircraft the order to guard along them. Works in TS and should do in RA2 as well. _________________ SHP Artist of Twisted Insurrection: Nod buildings
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
Help needed with Custom Missiles
