Reworked Sion Gameplay bugs

On the PBE, I have so far encountered two bugs with the reworked Sion.

  The first is an issue with his passive not activating properly. I was playing a hexakill game and I was killed by the enemy Katarina in lane. Her health was low so I was eagerly waiting for my passive to activate but instead after the initial passive animation I died instantly. When I checked my death recap it said I was killed by 168 damage from a bouncing blade and that was the only damage that hit me. This is the only time I have seen this happen so far, but my uneducated guess is that a bouncing blade bounced to me after I had initially died because my corpse was still targetable to the already thrown blade, and due to the way Sion's new passive is coded, this killed me a second time before my health was able to refill. If this is caused by the bounce targeting mechanic on bouncing blades, this bug may also occur with other bouncing spells such as those used by Ryze and Fiddlesticks.

  The second bug in which I have seen three times is that when Sion is running in his ult animation, if an enemy Nautilus throws his anchor at Sion, he immediately stops running, but the fire effects remain around Sion and he continues to channel despite not moving at all. The only way to stop the animation is to wait it out or to cancel it as it becomes impossible to collide with anything.

Bug 1 (Passive revive): (I have not replicated this bug, however this is how I believe it works)

1. Die as Sion with a Katarina on the enemy team
2. Either during, or after (not sure which) death, have the enemy Katarina throw her bouncing blades so that they bounce to you during your passive animation.
3. If everything replicates properly, Sion should not revive and immediately die again.

Bug 2 (Sion ultimate):

1. Have Sion activate his ultimate and run towards an enemy Nautilus.

2. Have Nautilus throw his anchor directly at Sion

3. If everything replicates properly, Sion should stop running but still continue channeling his ultimate.

   I have not personally tried to replicate either of these bugs, I have just seen them occur in my own games, so they may not replicate every time. However they did happen, so that means there is an issue, even if it isn't one that will occur on every occasion.