Jump to content

XML talk:BINA/PAR3: Difference between revisions

m
workaround: add a new root particle
m (exploring Mad Bomber particle)
m (workaround: add a new root particle)
Line 1: Line 1:
===Exploring Mad Bomber particle===
__TOC__
 
==Exploring Mad Bomber particle==
What triggers Mad Bomber's explosion?
What triggers Mad Bomber's explosion?


Line 60: Line 62:




===Discussion on <StopIfBreakable />===
===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.
 
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).
 
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.
 
 
==Discussion on <StopIfBreakable />==
'''Controversial phrase:'''
'''Controversial phrase:'''


8,168

edits