Lord Raiden General Discussion Thread

[fluffybunbunkittens]

Yes, this movie Raiden looks like he gets lost in his hat.

 

[Marlow]

@Marinjuana You've inspired me with your hipster Raiden. I'm going to give a Storm Cell/Super Bolt/Lightning Rod build a try, just for kicks.

 

[Marinjuana]

Superman punch can high profile and punish Cassie's low but mid gunshot. Right as Raiden releases it he'll go over it. It's not something you could do on demand(maybe when you are charging it and react) but it's evasive enough to make it more worthwhile to do.

 

[Mandolore1123]

Oh dear, I've had the lightning storm AMP bug happen to me twice in a set. Even cost me a game Has anyone had it happen to them a lot?

 

[Marlow]

Oh dear, I've had the lightning storm AMP bug happen to me twice in a set. Even cost me a game Has anyone had it happen to them a lot?

What's that again?

 

[Mandolore1123]

What's that again?

There's a weird bug where if you do AMP float and the lightning hits at a certain frame it will auto cancel the float without you doing the input leaving you very unsafe sometimes

 

[Marlow]

Oh yeah. I haven't messed around with Float enough for that to happen. Does it happen anywhere on screen? And does it happen with both the regular float and the DUB version of the float?

 

[Mandolore1123]

Oh yeah. I haven't messed around with Float enough for that to happen. Does it happen anywhere on screen? And does it happen with both the regular float and the DUB version of the float?

I haven't tested it thoroughly because that was the first time it happened to me and I don't really do the Back version of float to know. (I actually forgot that move existed .-.)

 

[Marlow]

It might not make a difference. When I've tried to do it I haven't noticed much of a discernable difference. Hopefully the error doesn't crop up too much.

 

[Mandolore1123]

It might not make a difference. When I've tried to do it I haven't noticed much of a discernable difference. Hopefully the error doesn't crop up too much.

So this is the bug I was talking about. However it doesn't just happen in the corner, not just off that string, and not just on the first lightning AMP lol. I saved the footage. Maybe I'll make a video with the inputs on and we can see the inputs too but idk if I still have the recording saved in the game

 

[NeroOps]

So this is the bug I was talking about. However it doesn't just happen in the corner, not just off that string, and not just on the first lightning AMP lol. I saved the footage. Maybe I'll make a video with the inputs on and we can see the inputs too but idk if I still have the recording saved in the game

If you allow his lightning storm to recover on its own as in not pressing anything after amplifying the move it triggers the bug. Nice find by the way.

 

[Mandolore1123]

If you allow his lightning storm to recover on its own as in not pressing anything after amplifying the move it triggers the bug. Nice find by the way.

I'm pretty sure it's random because I have no trouble in delaying the 3 during my play. It also doesn't explain why in the video it auto cancels after the first lightning since you will want to wait for all 3 lightning to come out before you press your next button anyway

 

[NeroOps]

I'm pretty sure it's random because I have no trouble in delaying the 3 during my play. It also doesn't explain why in the video it auto cancels after the first lightning since you will want to wait for all 3 lightning to come out before you press your next button anyway

I have no idea why you brought up 3 when I said let amplified lightning storm recover without pressing anything afterwards.
I have no idea either on why it auto cancels after the first lightning strike when amplified.
I'm not a developer for nrs but from my opinion I would think it has something to do with the properties of lightning storm which triggers the bug after you recover from a amplified lightning storm.
Also after the bug triggers if you delay amplifying lightning storm it fixes itself.

 

[Mandolore1123]

I have no idea why you brought up 3 when I said let amplified lightning storm recover without pressing anything afterwards.

Because if according to you the bug (where float AMP auto cancels) happens if I let it recover without pressing anything I should not be able to cancel into 3 in future attempts because the bug has been triggered and should happen every time, but I can.

 

[NeroOps]

Because if according to you the bug (where float AMP auto cancels) happens if I let it recover without pressing anything I should not be able to cancel into 3 in future attempts because the bug has been triggered and should happen every time, but I can.

This video shows exactly what i've been stating

Mortal Kombat 11

Watch "Mortal Kombat 11" on Streamable.

streamable.com

 

[Mandolore1123]

This video shows exactly what i've been stating

Mortal Kombat 11

Watch "Mortal Kombat 11" on Streamable.

streamable.com

I appreciate the vid and I’ve been able to replicate it in training. However on rewatching my own match footage I had the bug happen even without letting the float recover on it’s own. Which is why there must be another reason why the bug occurs beyond what you said. I’ve saved an example and I’ll try to upload it but I don’t have a USB with me right now so you might have to wait.

 

[NeroOps]

I appreciate the vid and I’ve been able to replicate it in training. However on rewatching my own match footage I had the bug happen even without letting the float recover on it’s own. Which is why there must be another reason why the bug occurs beyond what you said. I’ve saved an example and I’ll try to upload it but I don’t have a USB with me right now so you might have to wait.

In your video your input list on the side was never reset so you could've triggered the bug before it was cut out the beginning of the video.
Theirs moments where raiden recovers faster than he normally does after the amplified lightning storm without pressing 4 to cancel the float.
Maybe that occurred for you but the bug seems to trigger more consistently the way I demonstrated in the video.
If you can find a more consistent way to trigger the bug please share when you can.

 

[Mandolore1123]

In your video your input list on the side was never reset so you could've triggered the bug before it was cut out the beginning of the video.
Theirs moments where raiden recovers faster than he normally does after the amplified lightning storm without pressing 4 to cancel the float.
Maybe that occurred for you but the bug seems to trigger more consistently the way I demonstrated in the video.
If you can find a more consistent way to trigger the bug please share when you can.

My point is that it's inconsistent in occurring in the first place. The video I shared isn't mine. I had the bug occur to me in a real match when I didn't use your method and it occurred as a one-off thing. That's why I found it weird. I've found the match and I'll share here with the inputs when I can.

 

[Mandolore1123]

In your video your input list on the side was never reset so you could've triggered the bug before it was cut out the beginning of the video.
Theirs moments where raiden recovers faster than he normally does after the amplified lightning storm without pressing 4 to cancel the float.
Maybe that occurred for you but the bug seems to trigger more consistently the way I demonstrated in the video.
If you can find a more consistent way to trigger the bug please share when you can.

Hey sorry for the delay here's my video. It happens right at the end. If you notice the inputs I don't cancel float but it happens automatically, and if you watch the video there's no sign of me letting float AMP recovery on it's own. So while your way is the consistent way to get the bug to happen, it still happens randomly without having to trigger it manually. Hope this makes more sense
https://youtu.be/v4KhO7zL6IA

 

[NeroOps]

Hey sorry for the delay here's my video. It happens right at the end. If you notice the inputs I don't cancel float but it happens automatically, and if you watch the video there's no sign of me letting float AMP recovery on it's own. So while your way is the consistent way to get the bug to happen, it still happens randomly without having to trigger it manually. Hope this makes more sense
https://youtu.be/v4KhO7zL6IA

I see your point but random or not a more consistent way would be the ideal of figuring out what causes the bug. The move seems to be not implemented correctly. It's like the game can't handle processing the move multiple times without causing an error in the coding. The move shouldn't be canceling itself automatically after amplifying it.

I've noticed two ways that the bug triggers.

1. If you let raiden completely recover after amplifying lightning storm.
2. When lightning storm cancels itself with out pressing 4 after amplifying the move.

Easy way to see the second one occurring is to cancel the amplified lightning storm when raiden closes his mouth while floating mid air. Then repeat the move again without canceling it manually you should see raiden canceling itself automatically faster than if you were to let him recover on his own. If you do it again it triggers the bug regardless of what move you throw out before doing a amplifying lightning storm for the third time.
The only way to get rid of the bug is by delaying the amp version which was shown at the end of my video.

 

[Mandolore1123]

I see your point but random or not a more consistent way would be the ideal of figuring out what causes the bug. The move seems to be not implemented correctly. It's like the game can't handle processing the move multiple times without causing an error in the coding. The move shouldn't be canceling itself automatically after amplifying it.

I've noticed two ways that the bug triggers.

1. If you let raiden completely recover after amplifying lightning storm.
2. When lightning storm cancels itself with out pressing 4 after amplifying the move.

Easy way to see the second one occurring is to cancel the amplified lightning storm when raiden closes his mouth while floating mid air. Then repeat the move again without canceling it manually you should see raiden canceling itself automatically faster than if you were to let him recover on his own. If you do it again it triggers the bug regardless of what move you throw out before doing a amplifying lightning storm for the third time.
The only way to get rid of the bug is by delaying the amp version which was shown at the end of my video.

To be honest I don't care much to investigate the specific conditions for triggering the bug. I can only hope NRS knows about this and they will fix it at some point down the line. This shouldn't happen period.

 

[NeroOps]

To be honest I don't care much to investigate the specific conditions for triggering the bug. I can only hope NRS knows about this and they will fix it at some point down the line. This shouldn't happen period.

Understandable and i doubt they will when they still haven't fixed the whiffing issues jo push has when pushing the opponent towards the corner or out the corner at max distance.
Either tolerate that issue lightning storm has or don't use that ability.

 

[Mandolore1123]

Understandable and i doubt they will when they still haven't fixed the whiffing issues jo push has when pushing the opponent towards the corner or out the corner at max distance.
Either tolerate that issue lightning storm has or don't use that ability.

Yeah I'll keep using Storm, the bug doesn't happen often to me and we know how to get rid of it if it keeps happening so I guess it's all good at a casual level. I just hope after Pro Komp they fix all the custom moves and we can get some more variety in variations for all the characters

 

[Szkarad]

I though to maybe liven this thread up a bit: what is your preffered way to finish the combos in the corner? That's pretty important for us since we get to be in the corner often thanks to the superman. I know some people like to end with J3 -> B2, but honestly I don't really like going for that KB. On the other hand I've recently started using J3 -> F32 (and I've never seen anyone do it). From standard B12 you get around 28% damage so yes, suboptimal, but the ~40 frames of advantage you get is pretty amazing. Provided you play someone with a bad U2 wakeup you can jump in for a meaty, or backdash and use someting with a good range. Also pretty easy on execution, and recently I've started going for slightly easier combos I know I will do 100% of the time rather than the optimals that I might just drop and potentially lose the round because of that.
Thoughts?

 

[Mandolore1123]

I though to maybe liven this thread up a bit: what is your preffered way to finish the combos in the corner? That's pretty important for us since we get to be in the corner often thanks to the superman. I know some people like to end with J3 -> B2, but honestly I don't really like going for that KB. On the other hand I've recently started using J3 -> F32 (and I've never seen anyone do it). From standard B12 you get around 28% damage so yes, suboptimal, but the ~40 frames of advantage you get is pretty amazing. Provided you play someone with a bad U2 wakeup you can jump in for a meaty, or backdash and use someting with a good range. Also pretty easy on execution, and recently I've started going for slightly easier combos I know I will do 100% of the time rather than the optimals that I might just drop and potentially lose the round because of that.
Thoughts?

To be fair you really only need to worry about them breaking away. I haven't really tested it yet but doing J3, F32 should be the safest, whereas doing 243 means you have to be pretty mindful in hit confirming or else it's an easy punish for the opponent. Not to mention with TW you get to teleport behind them to punish some U2/U3s on a read too, though walking back is definitely the safer option