Multiple instances of same type of super weapon
Add an option for super weapon that if a player owns N buildings that provide this super weapon then that player gets N super weapons of this type.
I already asked Alex about this.
AlexB wrote:
because the game has one SW per type, and they are always global and unconnected to buildings This would have to be changed completely. I don't think that's gonna happen.
No problem. That's why I have my backup request on turning off NCO eva for a certain building so that I can duplicate the building & SW nicely. _________________
I would like to get back on the prototyping mechanic that was discussed a few weeks ago. Perhaps the current extent of this function could be expanded to allow for a hierarchy of prototype code to be imported into a single type, so that tags would be imported into a section A from the section highest in section A's prototype hierarchy in which they are set.
For example, if the position of a section X in a section Y's prototyping hierarchy decreases with increasing numerical index, counting from left to right, of section X's ID in the section IDs separated from section Y's ID by colons and other section IDs, this
would import Brute's Strength into Brute Gunner, as Brute Gunner is higher in the prototype hierarchy than Yuri Fanatic, overriding Strength=40 with the definition of Strength=200 in Brute. However, Yuri Fanatic also defines OccupyPip, which is not re-defined in the Brute's section, which means it would get imported into Brute Gunner from Yuri Fanatic.
Of course, other notations could be devised to allow the setting of such a hierarchy in the INI, but this appears to be the closest to the notation already implemented for the existing feature. QUICK_EDIT
I don't know if this is possible but can I suggest "some CrateGoodie units can only obtain on certain side/country"?
I mean, for example:
- Tank Destroyer is a CrateGoodie=yes.
- Only Americans, Africans, and YuriCountry can get that Tank Destroyer CrateGoodie. Other countries won't get that Tank Destroyer via crates.
Also another suggestion. Customizing radiation CellSpread for weapons with RadLevel tag. For instance, a weapon with a RadLevel tag and its warhead's CellSpread is .3 but I want its radiation's CellSpread higher like 2. QUICK_EDIT
I'm not sure what you mean with a radiation CellSpread? You can already make a radiation field as big or small as you want.
Means that radiation spread would be separate from weapon's damage spread. You could use separate warhead but this approach has its problems as RadLevel does not work from Shrapnel/AirburstWeapon and making the splitted weapon deal the actual damage means any damage modifiers on the unit (AE, crates etc.) are ignored since they are only applied to weapons directly attached to the unit. The IonCannon functionality recently introduced in Ares would be another option to deal damage using another warhead but this method grants no experience. _________________ QUICK_EDIT
I'm not sure what you mean with a radiation CellSpread? You can already make a radiation field as big or small as you want.
Really? I don't think so because size of radiation field is always based on CellSpread. I really prefer that you can adjust the size of radiation field without adjusting the CellSpread. QUICK_EDIT
I recently came across something: someone used the Abductor logic for a vehicle that "can teleport units away from harm".
But this comes at a cost: the 'evacuator' has to be manually unloaded.
Basically: Something like AutoUnload that forces a transport to deploy.
AutoUnload=Primary/Secondary (for 'evacuators', see above examlpe).
I'm pretty sure this can be expanded upon. Last edited by TAK02 on Mon Jun 04, 2018 1:06 am; edited 1 time in total QUICK_EDIT
I recently came across something: someone used the Abductor logic for a vehicle that "can teleport units away from harm".
But this comes at a cost: the 'evacuator' has to be manually unloaded.
Basically: Something like AutoUnload that forces a transport to deploy.
AutoUnload=Primary/Secondary (for 'evacuators', see above examlpe).
I'm pretty sure this can be expanded upon.
I would rather suggest moving DeployToFire tag to weapons _________________
I recently came across something: someone used the Abductor logic for a vehicle that "can teleport units away from harm".
But this comes at a cost: the 'evacuator' has to be manually unloaded.
Basically: Something like AutoUnload that forces a transport to deploy.
AutoUnload=Primary/Secondary (for 'evacuators', see above examlpe).
I'm pretty sure this can be expanded upon.
I would rather suggest moving DeployToFire tag to weapons
Would that really do the trick? Isn't unloading passengers and deploying into building/changing into deployed state completely different from one another?
Also, I'm sure moving flags is a bad idea _________________ One and only developer of the Command & Conquer Dune "C&C D" mod.
m7 wrote:
I tend to release things I create so that assets are never lost to hard drive problems, accidental deletion, or me having to pretend to care about rippers taking things from my project when it is done.
I recently came across something: someone used the Abductor logic for a vehicle that "can teleport units away from harm".
But this comes at a cost: the 'evacuator' has to be manually unloaded.
Basically: Something like AutoUnload that forces a transport to deploy.
AutoUnload=Primary/Secondary (for 'evacuators', see above examlpe).
I'm pretty sure this can be expanded upon.
I would rather suggest moving DeployToFire tag to weapons
Would that really do the trick? Isn't unloading passengers and deploying into building/changing into deployed state completely different from one another?
Also, I'm sure moving flags is a bad idea
Why don't you try it yourself and stop making false assumption _________________
Properly adding more than two weapons (and actually picking the best one, not just defining them using WeaponN) is complex. The original Ares 0.3 was supposed to have a lot of changes, like unlimited WeaponN, better options to pick the right weapon instead of Land Targeting and Naval Targeting (that's features like selecting by range, for example). This is nigh-impossible to do in a backwards-compatible way, so it would require a totally new design of the weapon handling code, and this hasn't happened yet.
Though, one could say that Ares is prepared to eventually have this, because the unlimited IFV modes feature actually also implemented unlimited weapons. Now it's just a matter of adding code to find the best of N matches, with several options to fine tune, without having a bad impact on performance. After all, weapon selection happens thousands of times per frame, and expensive computations will hurt performance... but the foundation is in place.
Also, it would most likely be possible to have a weapon be picked if mind-control is full. If done right, such special cases would be doable quite naturally by defining a list of flags on each weapon. Wouldn't allow for all special cases, but at least a few hopefully useful ones. The code for such a list of flags is already in place, too. I wrote the first version of that years ago, finally added it this year and gave it a test run with the new elite abilities.
Tertiary weapon work like primary (land targeting, naval targeting, deploy fire etc.), quaternary weapon work like secondary. QUICK_EDIT
Properly adding more than two weapons (and actually picking the best one, not just defining them using WeaponN) is complex. The original Ares 0.3 was supposed to have a lot of changes, like unlimited WeaponN, better options to pick the right weapon instead of Land Targeting and Naval Targeting (that's features like selecting by range, for example). This is nigh-impossible to do in a backwards-compatible way, so it would require a totally new design of the weapon handling code, and this hasn't happened yet.
Though, one could say that Ares is prepared to eventually have this, because the unlimited IFV modes feature actually also implemented unlimited weapons. Now it's just a matter of adding code to find the best of N matches, with several options to fine tune, without having a bad impact on performance. After all, weapon selection happens thousands of times per frame, and expensive computations will hurt performance... but the foundation is in place.
Also, it would most likely be possible to have a weapon be picked if mind-control is full. If done right, such special cases would be doable quite naturally by defining a list of flags on each weapon. Wouldn't allow for all special cases, but at least a few hopefully useful ones. The code for such a list of flags is already in place, too. I wrote the first version of that years ago, finally added it this year and gave it a test run with the new elite abilities.
Tertiary weapon work like primary (land targeting, naval targeting, deploy fire etc.), quaternary weapon work like secondary.
Sorry but I think OpenTopped + InitialPayload + Experience.PromotePassengers= + AlternateFLH# is doing much more than 2 more primary-like weapons ever could. _________________ "Don't beg for things; Do it yourself or you'll never get anything." QUICK_EDIT
Very original idea - adaptanium armor from Andivionic Scientific Alliance. Adaptanium is a heavy dark blue metal, with the original properties very similar to osmium. It has an abnormally plastic molecular structure, which under various influences changes so as to become maximally unresponsive to them. For example, with sufficiently frequent loads, the adaptanium bar becomes harder, it loses its heat property from high temperatures, and if it is exposed to sound or other fluctuations for a long time, it stops vibrating. From it, you can make ideal insulators - but if the adaptive part created, for example, to reflect gamma rays, instead will be used as protection against acids, it will become resistant to them, but soon again will start to pass radiation. In game code adaptanium armor have flag ResistantTypesNumber= and flags ResistantType.X= (X is a number). In ResistantType.X are warheads. If unit with AdaptaniumArmor=yes has been attacked by weapon with warhead from ResistantType.X, it gain modifier to resistance to warheads from ResistantType.X. But if unit has been attacked weapon with warhead from ResistantType.Y, it loss resistance modifier to warheads from ResistantType.X, but gain resistant modifier to warheads from ResistantType.Y. Sorry for my bad English. QUICK_EDIT
Properly adding more than two weapons (and actually picking the best one, not just defining them using WeaponN) is complex. The original Ares 0.3 was supposed to have a lot of changes, like unlimited WeaponN, better options to pick the right weapon instead of Land Targeting and Naval Targeting (that's features like selecting by range, for example). This is nigh-impossible to do in a backwards-compatible way, so it would require a totally new design of the weapon handling code, and this hasn't happened yet.
Though, one could say that Ares is prepared to eventually have this, because the unlimited IFV modes feature actually also implemented unlimited weapons. Now it's just a matter of adding code to find the best of N matches, with several options to fine tune, without having a bad impact on performance. After all, weapon selection happens thousands of times per frame, and expensive computations will hurt performance... but the foundation is in place.
Also, it would most likely be possible to have a weapon be picked if mind-control is full. If done right, such special cases would be doable quite naturally by defining a list of flags on each weapon. Wouldn't allow for all special cases, but at least a few hopefully useful ones. The code for such a list of flags is already in place, too. I wrote the first version of that years ago, finally added it this year and gave it a test run with the new elite abilities.
Tertiary weapon work like primary (land targeting, naval targeting, deploy fire etc.), quaternary weapon work like secondary.
Sorry but I think OpenTopped + InitialPayload + Experience.PromotePassengers= + AlternateFLH# is doing much more than 2 more primary-like weapons ever could.
I think he/she was trying to get at an alternative for more weapons that doesn't utilise the InitialPassengers logic, probably because he/she wants a multi-weaponed transport where the "Weapons" don't show on the pipscale, and not just not exit with MovementRestrictedTo=water.
RIAKTOR wrote:
Very original idea - adaptanium armor from Andivionic Scientific Alliance. Adaptanium is a heavy dark blue metal, with the original properties very similar to osmium. It has an abnormally plastic molecular structure, which under various influences changes so as to become maximally unresponsive to them. For example, with sufficiently frequent loads, the adaptanium bar becomes harder, it loses its heat property from high temperatures, and if it is exposed to sound or other fluctuations for a long time, it stops vibrating. From it, you can make ideal insulators - but if the adaptive part created, for example, to reflect gamma rays, instead will be used as protection against acids, it will become resistant to them, but soon again will start to pass radiation. In game code adaptanium armor have flag ResistantTypesNumber= and flags ResistantType.X= (X is a number). In ResistantType.X are warheads. If unit with AdaptaniumArmor=yes has been attacked by weapon with warhead from ResistantType.X, it gain modifier to resistance to warheads from ResistantType.X. But if unit has been attacked weapon with warhead from ResistantType.Y, it loss resistance modifier to warheads from ResistantType.X, but gain resistant modifier to warheads from ResistantType.Y. Sorry for my bad English.
It's not your English you should apologise for, but not getting to the point and using paragraphs where needed
In any case: RIAKTOR wants something like adaptive armor.
Armor that changes its properties (including possible immunity) depending on what it was last blasted with, be it permanent or temporary.
And add switching shenanigans between these ArmorType's properties as well.
Code:
TECHNOTYPE
AdaptiveArmor=yes
ResistanceWarheads.1=DesoWarhead, Warhead9001 ;OVER 9000!
ResistanceWarheads.2=Warhead2
...
Resist.1=ImmuneToRadiation
Resist.2=Warhead2 ;Techno is now immune to all attacks from weapons with Warhead2, but swaps it for ImmuneToRadiation.
Then maybe add something like ResistanceSwitchDelay.1= for the time (in frames) until the effects of Resist.1 wear off, regardless of whether or not the Techno isn't getting hit anymore or it's adapting to something else (unless you want to change that).
Then there should be ResistanceWarheads.0= for what this Techno is immune to by default, and a Adapt.Full= if you want to have a Techno either keep the default immunity after getting hit or adapt fully to the new enviroment.
Am I right so far, RIAKTOR?
Now that I think about, this sounds like a nice feature, but I don't want to know how much pain Alex has to go through for this _________________ One and only developer of the Command & Conquer Dune "C&C D" mod.
m7 wrote:
I tend to release things I create so that assets are never lost to hard drive problems, accidental deletion, or me having to pretend to care about rippers taking things from my project when it is done.
would it be possible to implement ordering multiple units in a single shift + LMB? It seems to be not a hard to do yet nice feature to have, as more modern strategies have such thing. _________________ Using MagicaVoxel to create voxel models :: Phobos YR Engine Extension
So, AlexB was asking what trigger events could be added with the support of Ares. Here're some examples:
- Driver Killed: Fire when killing the dirver of vehicle with such tag.
- Get EMP: Fire when the unit with the tag is EMP'd.
- Weapon Disabled: Similar to get EMP but fire by Weapon Disabler.
- Destroyed By (certain house): The object is destroyed by a specific house, similar to Attacked By (house).
- Techtype Not Exist extension: we can actually make its param useful - it would fire when the amount of the techtype is below the param X instead of doesn't exist at all.
Now we're opening for suggestions for more of them. If you come up with any events that might be useful in the map, please share your ideas.
Here're some of mine:
- Techtype Exist/Not Exist extension: could we made an extended version that specific to certain house?
- Superweapon Charge to: similar to the Chronosphere /Iron Curtain ones in AI trigger, fire when certain superweapon charge to a specific percentage. It could make IronCurtain type superweapon more useful.
- Destroyed #: the sum of Destroyed Buildings # and Destroyed Units #, considering all of the three have an 'Destroyed All' version.
- Iron Curtain'd/Force Shielded/Drained: similar to the above examples except it's firing when the object is under Iron Curtain/Force Shield/Drain.
- Attacks: Fire when the attached object begins to use its weapons.
- Radar Off/On: fire when player's (or specific house's) rader on or off.
- Full health: fire when the objects' health is full. Could be used to check if some broken thing is repaired.
... QUICK_EDIT
Been thinking about the MARV and it made me come up with this:
ProcessRate= frames between processing one content (a bale for ore, or the first unit for passengers), defaults to -1, which disables the logic.
ProcessMult= a multiplier to the amount of money given upon successful processing of content (based on soylent for units and... whatever gives ore value)
This allows not only things like the MARV but also hings like a Chrono Prison that slowly erases its prisoners. QUICK_EDIT
[SuperWeapon]->KeepTimer=yes
If a SuperWeapon is once available, its timer won't reset if it becomes unavailable and then available again. The timer stops when it's unavailable and resumes when it's available again.
[Weapon]->FireInTransport=list of TechnoTypes
This weapon can be fired when its owner is inside these OpenTopped=yes transports.
PreImpactAnim.MoveBullet=yes
If PreImpactAnim can move, e.g. FLAMEGUY, debris, then the bullet moves with the anim, and shrapnel/airburst weapon would be spawned at the new location. _________________
Joined: 05 Sep 2013 Location: LocationNotFoundException at RealLife.Location.find() at line: -1
Posted: Fri Jul 13, 2018 2:34 pm Post subject:
If we are actually discussing events for maps, then I would suggest something like Super Weapon Fired, which is true if the house of the trigger fires a specified SW. This could be useful as the one can't predict when a player will launch a SW.
Also something like Techno (or attached object) (owned by trigger owner) Enters (building or cell) would allow to be more specific as to what should enter what, and also sometimes allow to use less extra houses for this purpose. QUICK_EDIT
is there a way to make superweapons inaccurate? I have a Sonar Pulse special, and the computer targets my units dead-on every time, a controllable "accuracy" entry might be nice, like, you say set AIInaccuracy=12 and the computer picks its firing spot, and fires the superweapon at a randomly picked tile within 12 tiles of where it wants to.
This is purely to give the computer the appearance that it can't see all your units, stealthed or not, but might be nice with stuff like paradrops and things too.
This tag would only effect the AI. _________________ MIdAS - Turning wages into beer since 2002 QUICK_EDIT
Joined: 09 Mar 2008 Location: Osaka (JP)/Hong Kong/Germany
Posted: Mon Jul 23, 2018 8:16 pm Post subject:
Starkku wrote:
The IonCannon functionality recently introduced in Ares would be another option to deal damage using another warhead but this method grants no experience.
Could you (or someone else who knows) elaborate how IonCannon function (which is a SuperWeapon type, to my knowledge) could be used to achieve to separate radiation spread from the spread of damage for normal weapons (which I assume you are speaking about, since the lack of experience gain from its use would obviously not be a notable drawback of a superweapon, unless you were making a general statement about the drawbacks of superweapons and a SW with the function of separate radiation and damage spread would not be free from the drawback of AE and crate boni not figuring into the damage calculation, at least according to my straight-forward understanding of how such a separation would be achieved)? _________________
Mao Zedong wrote:
Our mission, unfinished, may take a thousand years.
I thought about this, long ago already. There's no good way to do this, without adding several new tags for this.
What about SWs where mission triggers set a preferred target cell? Should that cell be taken as the literal target, or should it be affected by inaccuracy, too? Cell Spread inaccuracy, or perfect circle? Any cell equally likely, or following a normal distribution rather? Affecting AI only, or also auto-fired human SWs?
Would it be consistent if a super weapon requires to be launched at an enemy building, but after inaccuracy is applied, it would fire on an empty cell?
If Inaccuracy isn't set, then everything would work, and if it is set, it's only because the modder set it consciously, so this would have to be expected to be inaccurate. Modders would be responsible to not use inaccuracy on super weapons where it would break them. That is, ignoring targeting issues, and maybe only affecting non-preferred targets set by map actions, then this would be doable. _________________ QUICK_EDIT
I'll repeat a few of my suggestions, so they dont get totally forgotten.
1. [TechnoType] FakeOf = TechnoType
At least this is the result of what we talked about a while ago - the goal is to trick the veterancy selection hotkey that displays the value of units selected, which reveals whether a fake building or decoy unit for example - thus ruining their effect.
So [FakeWarFactory] FakeOf = RealWarFactory would make FakeWarFactory display the cost of RealWarFactory instead.
2. [TechnoType] SelfHealing.CombatDelay = int
If a unit is damaged then it starts this timer before being allowed to apply self healing again, so units only heal outside of combat.
3. [Animation] Damage.FrameDelay = int
Allows you set it how often the animation warhead or weapon is applied, so its not necessarily every single frame. Would be practically useful but I also worry about performance issues, particularly online, when things are detonated so regularly. QUICK_EDIT
I thought about this, long ago already. There's no good way to do this, without adding several new tags for this.
What about SWs where mission triggers set a preferred target cell? Should that cell be taken as the literal target, or should it be affected by inaccuracy, too? Cell Spread inaccuracy, or perfect circle? Any cell equally likely, or following a normal distribution rather? Affecting AI only, or also auto-fired human SWs?
Would it be consistent if a super weapon requires to be launched at an enemy building, but after inaccuracy is applied, it would fire on an empty cell?
If Inaccuracy isn't set, then everything would work, and if it is set, it's only because the modder set it consciously, so this would have to be expected to be inaccurate. Modders would be responsible to not use inaccuracy on super weapons where it would break them. That is, ignoring targeting issues, and maybe only affecting non-preferred targets set by map actions, then this would be doable.
My idea was pretty much your last few lines, if inaccuracy isn't set, then it's essentially Inaccuracy=0 and modders would be trusted to not put it on, say, a nuke.
I'd also say have a tag for which distribution method you'd prefer, my idea was every cell has an equal weight, to emphasize the AI is "Firing blind" as it were, useful for stuff like reveal specials, sonar pulses, and spy planes.
I'd say triggers should be effected by inaccuracy, but again, it's down to the modder to not bugger up something that shouldn't be messed with.
if it's easier, cell spread inaccuracy is fine, my idea is just to make stuff like Sonar Pulse not always hit targets perfectly.
also, this tag would affect the AI only, or not if you want to code a separate tag for it. _________________ MIdAS - Turning wages into beer since 2002 QUICK_EDIT
I think I might have missed a discussion on this at some point, but is there any particular reason why we don't have STOL aircraft like in games like RON?
Something like RateOfAscent / RateOfDescent that would control how many leptons a unit goes up or down per cell of forward movement. Setting these to 0 (default) would effectively emulate the current VTOL movement. A value of 1 could mean an ascent/descent of 1024 leptons over 10 cells; 2 over 5 cells, and 3 over 3.33 cells, and so on.
Or even a more simpler system, with just 2 options of either VTOL (default) or STOL (something like what RoN had) QUICK_EDIT
I have a question with regards to the weapons with passengers in aircraft unit types. Is it possible for the aircraft unit not to drop or parachute its passenger while firing its main or sub weapons ?
If not is it possible to add a tag to not do such thing ? example:
Bu7loos, yeah, I would also like to see aircraft respecting GuardRange, so once they are put on guard, and target approaches that range, aircraft immediatelly take off and go to attack.
OmegaBolt wrote:
2. [TechnoType] SelfHealing.CombatDelay = int
If a unit is damaged then it starts this timer before being allowed to apply self healing again, so units only heal outside of combat.
Yeah, I also would use that. Very useful feature. I think I have seen this somewhere in some game.
However, as majority I still wait Unit-to-Unit transformation on double click. Feature No1 for happier times _________________
Also I found out targeting issues for Long Range AA defenses Specifically Ranges= 12 to 29 or when place either above or below or near a cliff or elevation in which some time it can only shoot for when the aircraft's gets way too close.
Also, for ranges above 29 tags HasRadialIndicator=true and ConcentricRadialIndicator=true does not show correctly and looks broken. QUICK_EDIT
Apologies if this has already been requested, but, if possible, any chance of seeing something like the shield of the Ordos vehicles from Emperor?
Basically, the shield soaks up damage and then replenishes itself.
The shield either takes hitpoints/strenght like a normal Techno or a percentage of the 'carrier-Techno's strength.
Then add "Shield.SelfHealPoints" and "Shield.SelfHealInterval"...
Unless Attach-Effect or some other existing Ares-feature/logic can emulate this? QUICK_EDIT
Is it possible to make building auto placed outside the map upon construstion completed?
The main propose of it is to make something like techno-research which providing map-wide AttachEffects or various modifers.
The problem of that would be that there might not be enough space (even for a 1x1 building) outside the playable boundries.
That, and I think you should be able of getting the same result using inviso BalloonHover infantry (regarding prerequisites. Not sure about AttachEffect).
I'd link to the topic here, but either it's gone or search is broken. And I don't know who did it either, but I think it was cxtian.
Topic had to do something with RA3 Empire upgrades in RA2 using Ares, IIRC. QUICK_EDIT
I'm using 0x0 building to perform special tasks. It's generated only once by conyard's UDSW and it's generated at the center of conyard.
It's not invisible tho, see the building called "Your Territory?" Its image is a glowing hexagon network.
You can make it perfectly invisible, 0x0 takes no physical space hence can't block anything.
I'm using 0x0 building to perform special tasks. It's generated only once by conyard's UDSW and it's generated at the center of conyard.
It's not invisible tho, see the building called "Your Territory?" Its image is a glowing hexagon network.
You can make it perfectly invisible, 0x0 takes no physical space hence can't block anything.
I'm using 0x0 building to perform special tasks. It's generated only once by conyard's UDSW and it's generated at the center of conyard.
It's not invisible tho, see the building called "Your Territory?" Its image is a glowing hexagon network.
You can make it perfectly invisible, 0x0 takes no physical space hence can't block anything.
Customizing radiation CellSpread for weapons with RadLevel tag. For instance, a weapon with a RadLevel tag and its warhead's CellSpread is .3 but I want its radiation's CellSpread higher like 2.
No that won't work. Already tried that anyway and someone already mentioned that it won't work.
Just tested it & it works fine, make the main weapon produce the rad field & the second splits weapon do the damage. The only drawback is as Starkku mentioned, any damage buffs from attach effect &/or crates aren't applied. _________________
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