XML talk:BINA/PAR3: Difference between revisions

m
→‎The Scarlett case: marked dead link
(removing dead links and code longer relevant as links are dead and the issue has been solved and documentated on XML:BINA/PAR3)
m (→‎The Scarlett case: marked dead link)
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
__TOC__
__TOC__
==Particle statistics==
http://paradox.oni2.net/wiki/particle_statistics.txt


==Particle subtype investigation==
==Particle subtype investigation==
Line 107: Line 110:


===The Scarlett case===
===The Scarlett case===
Scarlett bound [http://oni.bungie.org/forum/viewtopic.php?id=2991 mad_x01 to a character animation] which spawns the particle at global 0; 0; 0.
Scarlett bound mad_x01 to a character animation (<nowiki>http://oni.bungie.org/forum/viewtopic.php?id=2991</nowiki>, dead link) which spawns the particle at global 0; 0; 0.


I don't know yet what's wrong with the spawning but obviously its supposed to work differently.
I don't know yet what's wrong with the spawning but obviously its supposed to work differently.


That bug (or new "feature") can be avoided by introducing a new root emitter. For tests I used [https://dl.dropboxusercontent.com/u/139715/OniGalore/BINA3RAP_Talk/BINA3RAPh2h_powerup_e01a.xml h2h_powerup_e01a] (Syndicate compound level, daodan blast).
That bug (or new "feature") can be avoided by introducing a new root emitter. For tests I used h2h_powerup_e01a (<nowiki>https://dl.dropboxusercontent.com/u/139715/OniGalore/BINA3RAP_Talk/BINA3RAPh2h_powerup_e01a.xml</nowiki>, dead link) (Syndicate compound level, daodan blast).


For <SelfImmune>1 to take effect, x01 <HasDamageOwner> must be set to "true". (h2h_powerup_e01a has that already. A complete ''chain of ownage'' is essential.)
For <SelfImmune>1 to take effect, x01 <HasDamageOwner> must be set to "true". (h2h_powerup_e01a has that already. A complete ''chain of ownage'' is essential.)


Creating and renaming particle clones would be ideal to introduce the actual changes so that the originals aren't affected. However, over here, the new explosion file isn't recognized which leads to new questions and investigations. But for now, ... not now.
Creating and renaming particle clones would be ideal to introduce the actual changes so that the originals aren't affected. However, over here, the new explosion file isn't recognized which leads to new questions and investigations. But for now, ... not now.


==Discussion on <StopIfBreakable />==
==Discussion on <StopIfBreakable />==