All Chars Update(June of 2017)

Started by DivineWolf, June 28, 2017, 05:57:25 PM

Previous topic - Next topic

Trololo

No. That glitch was about Sagat's repeat of that intro at the second round of the normal fight.
While all the triggeredall triggers made this intro restricted to first round, they were all trigger1, so restrictions are worked only on Adon by HЃh, but MY Adon was on trigger2, so it isn't restricted at all and it can reappear in 3rd, 4th and so on rounds.

I know the screen isn't definitive, but believe me: try to pull versus at second round and you'll see.

DivineWolf


Shadic12

Hey DW are you planning on working on Zero after Strider or you already have someone else in mind for the next WIP?

DivineWolf

@[user id=82064]Trololo[/user]:

Fixed. Though be a pal and confirm for me please? :heart:




Quote from: Shadic12 on September 11, 2017, 04:59:17 PM
Hey DW are you planning on working on Zero after Strider or you already have someone else in mind for the next WIP?

I'm actually gonna get back to work on the collab project I was doing with @[user id=47125]Sky79[/user]:
The female vampire char. I was working on her for awhile, but progress got halted. Sky asked if I could get something going by Halloween. I told him no promises, but I'll see what I can do. So, I stop procrastinating with Hiryu and am putting other stuff on hold for now.

Shadic12


PeXXeR

#45
Wolf, this is what Jman said about the shake on the projectiles, I hope it helps bro.

Jmorphman:
the shaking is cuz the projectiles still have active hitdefs with envshake in them, but there's no hitsparks are sounds activating cuz they're not hitting a player
if the envshake was removed and applied in its own sctrl it wouldn't happen

Jmorphman

Wrong thread, dude!

also I was just thinking out loud, I never ended up posting the envshake thing to DivineWolf cuz then the envshake would never activate against other (non-Ouroboros) projectiles too! It's something I'm still thinking about!

PeXXeR

#47
I confused the threads :/

Trololo

DW, I'm here to confirm: the glitch is truly fixed. Thanks a lot!