Removing Assassinate was a mistake

[YukikoKurosawa]

So as of EW, Assassinate, rather than part of a combo with Dream within a Dream, now just gets converted into the latter at lvl 50. Though functionally this isn't a big deal, for me anyway, it takes away a bit of the appeal of the Ninja. Assassinate was one of Ninjas coolest, arguable, the coolest, ability. I would say it was a signature ability of the job.

Taking it away and just leaving us with Dream within a Dream just feels.......pointless? Since it was only able to be used following Dream within a Dream, if the problem was just having too many buttons to press, why not do what they've done with so many other abilities and just have Dream within a Dream turn into Assassinate when used? it feels like something is missing now from my job that should be there. You didn't replace it with anything, you just made my job less interesting.

Again, not a big deal, but it certainly makes the job feel less appealing and loses a bit of it's flavour and I'm just left wondering what was even the reason?

[AC9Breaker]

Nah, trick attack is the signature move. Also more ninja magic is cooler IMHO. The constant gap closer raiju and bhavchakra combo is much more interesting to me.

[Seraphor]

Nope. Goodbye animation lock, you won't be missed.

[Kolsykol]

I am not a fan of it being removed either, and I rly still don't understand the people going on about the animation lock.
The reason why you died wasn't because of the lock, people need to stop blaming the game for their own mistakes.
I don't believe that there was any situation where someone used it and died *because* of the animation lock, but there probably were a lot of situations were people like to believe that they did.

Dream Within a Dream just felt way better with Assassinate imo, I liked the extra ogcd and it felt cool to use.

[Raikai]

The reason why you died wasn't because of the lock, people need to stop blaming the game for their own mistakes.

The animation lock prevented me from moving out of AoEs in time in the past, especially on new fights where I was still learning the telegraphs. Unless you're suggesting that what really kills people is their inability to predict that an AoE will spawn right when Assassinate locks you from moving away from that.

[Kolsykol]

The animation lock prevented me from moving out of AoEs in time in the past, especially on new fights where I was still learning the telegraphs. Unless you're suggesting that what really kills people is their inability to predict that an AoE will spawn right when Assassinate locks you from moving away from that.

What I am saying is that the animation lock was extremely short, if you got hit by an AoE because of it then it wasn't because of the animation lock it was because you didn't know the mechanics and used it when it was already too late.
There's not a single AoE in the game that the lock would get you killed specifically because of it, they just simply don't happen that fast.
If you got hit by it then it was because the AoE '' cast '' was already in progress and going through when you pressed the button and you most likely wouldn't have dodged it to begin with.

I think that what really happens in these cases is that people get hit by it and they feel dumb and blame animation locks when in reality they would've been hit regardless.

[Atamis]

Just making room for the Assassin class. Nothing to see here citizens.

[Awarewolf]

What I am saying is that the animation lock was extremely short, if you got hit by an AoE because of it then it wasn't because of the animation lock it was because you didn't know the mechanics and used it when it was already too late.
There's not a single AoE in the game that the lock would get you killed specifically because of it, they just simply don't happen that fast.
If you got hit by it then it was because the AoE '' cast '' was already in progress and going through when you pressed the button and you most likely wouldn't have dodged it to begin with.

I think that what really happens in these cases is that people get hit by it and they feel dumb and blame animation locks when in reality they would've been hit regardless.

I agree with this. I mained Ninja in ShB and never got hit with an AoE while assassinating. I think letting DwaD and Assass share the same oGCD button would of been great.

I stopped playing my Ninja for other reasons, but this little change didn’t help.

[Grimoire-M]

What I am saying is that the animation lock was extremely short, if you got hit by an AoE because of it then it wasn't because of the animation lock it was because you didn't know the mechanics and used it when it was already too late.

It’s fine you got your animation lock back by force in Raiju spam please look forward to it.

[Satarn]

Unless you're suggesting that what really kills people is their inability to predict that an AoE will spawn right when Assassinate locks you from moving away from that.

I mean, yes actually? There is no such thing as random AoE in this game, the fights are entirely scripted. Even slightly random things are just "at timestamp xx:xx, execute either A, B or C out of the set" type of stuff at most. So yeah, you should be able to predict when you may have to move the Assasinate in your rotation in order to not be killed and that was part of the fun in the ability (along with the TCJ lock). It was something to play around.

And yes, of course in your first time/few times in the fight you will not know it that well yet and may eat that AoE, but... it's the same for every other mechanic you are still learning to execute.