Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Patching extra functionality into <gamemd.exe>
The whole point of this is that there is no owner. If Damage is dealt by a Particle, that Particle is the owner of the Damage - it doesn't know the Particle is owned by a ParticleSystem which was fired by a weapon which belongs to a unit which has an owner.

So telling a weapon it is OwnedByFirer, when the Firer is FireParticle5, is no use at all Wink
Forum Rules

(01.06.2011, 05:43:25)kenosis Wrote: Oh damn don't be disgraced again!

(25.06.2011, 20:42:59)Nighthawk Wrote: The proverbial bearded omni-bug may be dead, but the containment campaign is still being waged in the desert.
Maybe I worded my reply wrongly. I meant that the tag tells the weapon that everything that is subsequently spawned by it, be that particles or debris or animations etc. will be owned by the house that fired the original weapon, so instead of the particle's firer being FireParticle5, it would be Player@A, or Player@B etc.
Also, why does this topic keep getting pinned then unpinned?
Ares Project Manager.
[Image: t3wbanner.png]
[Image: cncgsigsb_sml.png]
Open Ares positions: Documentation Maintainer, Active Testers.
PM if interested.
Could be a problem with quick reply...only in this forum, all checkboxes are deselected on it by default...maybe it interprets a missing "stick thread" as an order to "do unsticky thread".
Forum Rules

(01.06.2011, 05:43:25)kenosis Wrote: Oh damn don't be disgraced again!

(25.06.2011, 20:42:59)Nighthawk Wrote: The proverbial bearded omni-bug may be dead, but the containment campaign is still being waged in the desert.
Quote:Could a tag be used on a weapon to tell it that it is owned by the firer, something like OwnedByFirer=yes/no, then if that tag is present on the weapon, all effects (bounty, mutation, etc.) are applied to the firer's house.
It's impossible!

Two new super weapons added:
1)DropPod
2)IonCannon

So, I rename ParaDropInf, ParaDropInfNum, ParaDropUnits, ParaDropUnitsNum tags
to DropInf, DropInfNum, DropUnits, DropUnitsNum.

DROPPODS AVAILABLE!


Attached Files Thumbnail(s)
   
ARM forever - x86 sucks!


CnCVK Wrote:So, I rename ParaDropInf, ParaDropInfNum, ParaDropUnits, ParaDropUnitsNum tags
to DropInf, DropInfNum, DropUnits, DropUnitsNum.
Why rename? Would that not interfere with the New Paradrop superweapons, not to mention all the mods it would mess up.
Ares Project Manager.
[Image: t3wbanner.png]
[Image: cncgsigsb_sml.png]
Open Ares positions: Documentation Maintainer, Active Testers.
PM if interested.
WOHO DROP POD Smile Big Grin you rock VK Smile, i have waited for this for a long time
But what are a Ion Cannon? You can make these with any clone righ now
Is it planned or accidental that the Apocs don't have DropPods?
TheMan Wrote:...
But what are a Ion Cannon? You can make these with any clone righ now

If works like Tiberian Sun SW (local tags of AIIonCannonConYardValue=,AIIonCannonWarFactoryValue= ... ) will to be more customizable than an emulated Ion Cannon...
[Image: cncr_beta_download_2.png]
5 different armies: GDI, Nod, Allies, Soviets & Yuri... & converted TS Terrain!!
MCV Wrote:Is it planned or accidental that the Apocs don't have DropPods?

Look at the picture:
Picture Wrote:DropPodUnit=APOC

CNCVK Wrote:So, I rename ParaDropInf, ParaDropInfNum, ParaDropUnits, ParaDropUnitsNum tags
to DropInf, DropInfNum, DropUnits, DropUnitsNum.
Like Nighthawk200 said, what will then happens to Paradrop?
The apocs probably have problems because of the Drop Pods can only carry infantry. Not vehicles. Drop pods would have to be a vehicle to carry units, like amphib transport, not a plane. But, that is also fixable. Eh, VK?
And Ion Cannon just makes things easier, like if you try to add anim before it hits.
Quote:If you realize that all things change, there is nothing you will try to hold on to. If you are not afraid of dying, there is nothing you cannot achieve.

Don't beg for things; Do it yourself, or you'll never get anything.
Quote:Why rename? Would that not interfere with the New Paradrop superweapons, not to mention all the mods it would mess up.
Because now it use by DropPod too Smile

Quote:Is it planned or accidental that the Apocs don't have DropPods?
However tanks have some problems Smile

Quote:Like Nighthawk200 said, what will then happens to Paradrop?
It's have the same INI tags.

Quote:If works like Tiberian Sun SW (local tags of AIIonCannonConYardValue=,AIIonCannonWarFactoryValu e= ... ) will to be more customizable than an emulated Ion Cannon...
No. You can use AITargetingType Smile

Changes: LStorm and Nuke Actions (Triggers) now is dependent from SW
so when you use Nuke trigger action -> the first SW with Nuke type will be used.
ARM forever - x86 sucks!


will you add a new unhardcoded codes for stolentech that you told you would do long time ago? Smile
Quote:will you add a new unhardcoded codes for stolentech that you told you would do long time ago?
No. Probably new stolen tech system comes.
ARM forever - x86 sucks!


since you can have as many tech centres per side as you want (like CDA has 5) I'd say to do something like your new infdeaths, where the unit that becomes available has "RequiresStolenTech=TATECH" on it for example, then spying on TATECH will make the unit available.
In combinaion with the old stolen tech tags that would make for some awsome tech-combinations like stealing from ConYards to get buildings, tech centres to get special tech, airpads to get new aircraft, etc.

And it would be more useable than "RequiresStolenFourthSideTech="
(Which would be a pain to type also.)




Users browsing this thread: 1 Guest(s)