Bug / Glitch: Chrome Dome stunlock

[Pikachu]

Well, I was waiting until I had a clear idea of what or why was causing this, but honestly after trying to replicate it via story mode (for faster testing) alone and failing miserably Iaround 10 times 'm posting the only clues that I have.

The stunlock occurs when playing multiplayer, not being the host and playing as Leo, spamming the shoulder bash (2x Forward and attack) on the second phase of Chrome Dome causes him to stay stunlocked in a corner until the player stops doing it.

I'll try to replicate it with other characters / offline if I can to check what could be the cause of the problem.

EDIT: Tested as Raph and stunlocked with him too, you can do damage until 1 health, you can't defeat him until you stop stunlocking him and doing another round.

[Radical Rat]

Not sure if it's intended, but you can also stunlock stage 1 Bebop by chaining those shoulder bashes right at the beginning. Don't know if it's infinite, but it causes very weird pushback

There is also something wrong going on with Groundchuck's charge during online play - not sure if it's some sort of a desync caused by a high latency, but for non host players he charges at a very high angle or just skip frames and teleports from one place to another. And as a host i can see people being hit while on my screen he's in a different place

Sometimes he also shoots missiles backward while facing in the opposite direction or do this suddenly when hit by a player

[Pikachu]

Oh yeah, Groundchuck lately loves to do all of these things, especially the charge and teleport or shooting missiles in a "stunned" pose in the opposite direction that he's facing.

Dirtbat also has another problem with the blinding light, where he changes direction mid-attack, making that duo tedious to handle if they want to do a lot of.... "magic tricks"

[ÀlaReskoos]

Originally posted by Pikachu:

Well, I was waiting until I had a clear idea of what or why was causing this, but honestly after trying to replicate it via story mode (for faster testing) alone and failing miserably Iaround 10 times 'm posting the only clues that I have.

The stunlock occurs when playing multiplayer, not being the host and playing as Leo, spamming the shoulder bash (2x Forward and attack) on the second phase of Chrome Dome causes him to stay stunlocked in a corner until the player stops doing it.

I'll try to replicate it with other characters / offline if I can to check what could be the cause of the problem.

EDIT: Tested as Raph and stunlocked with him too, you can do damage until 1 health, you can't defeat him until you stop stunlocking him and doing another round.

Hello Pikachu,

Thanks a lot for your report and sorry for the inconvenience.

This is similar to a problem we already encountered.

We were able to reproduce a few related bugs. Many where we had to use tools to simulate a bad connection and a high ping.

If you can, we would need your logs, save and DxDiag in order to investigate with the team.

All the information here: https://dotemuhelp.groovehq.com/help/useful-files-for-bug-reports

You can use WeTransfer to add the files in your comment.

Thanks in advance.

At your disposal if needed ;D

[Pikachu]

DXDiag: https://www.dropbox.com/s/x8u9o7e7j4m31gj/DxDiag.txt?dl=0
Save: https://www.dropbox.com/s/vlwirt9d8ikfuw8/GameSave.sav?dl=0
Log: https://www.dropbox.com/s/3p3r4eiqodrc6cd/log.txt?dl=0

I'll try to upload the log whenever it happens again, the log that I have from yesterday doesn't have the correct timestamp, so I believe that's from another play session.

EDIT: Not exactly a stunlock but the last stun was a little off, I'm uploading because in that run Groundchuck did some teleports during the charge and a stone golem was harrasing us during the Traag intro, so maybe it can help.

Second Edit: Okay, I replicated it and saved the log, I'm not sure if the first one can be checked within the new log, because I'm an idiot and forgot to rename the file before uploading and Dropbox decided to overwrite it (it's the same URL)

[ÀlaReskoos]

Originally posted by Pikachu:

DXDiag: https://www.dropbox.com/s/x8u9o7e7j4m31gj/DxDiag.txt?dl=0
Save: https://www.dropbox.com/s/vlwirt9d8ikfuw8/GameSave.sav?dl=0
Log: https://www.dropbox.com/s/3p3r4eiqodrc6cd/log.txt?dl=0

I'll try to upload the log whenever it happens again, the log that I have from yesterday doesn't have the correct timestamp, so I believe that's from another play session.

EDIT: Not exactly a stunlock but the last stun was a little off, I'm uploading because in that run Groundchuck did some teleports during the charge and a stone golem was harrasing us during the Traag intro, so maybe it can help.

Second Edit: Okay, I replicated it and saved the log, I'm not sure if the first one can be checked within the new log, because I'm an idiot and forgot to rename the file before uploading and Dropbox decided to overwrite it (it's the same URL)

No problem, thank you very much for the files. We're taking a closer look.

[Radical Rat]

I saved log from last online game where Groundchuck suddenly changes his charge trajectory, then teleports back to a different place. He did this multiple times, and there were only two of us with ping oscilating around 200-250. I'll also remember to save files from where he shoots missiles in different directions, because it often results with a player down

https://www.dropbox.com/scl/fo/xiok1gg2hg5ob3fyb6fwl/h?dl=0&rlkey=6zv4rxrz0hdtit317j0l3ub8l

[ÀlaReskoos]

Originally posted by Radical Rat:

I saved log from last online game where Groundchuck suddenly changes his charge trajectory, then teleports back to a different place. He did this multiple times, and there were only two of us with ping oscilating around 200-250. I'll also remember to save files from where he shoots missiles in different directions, because it often results with a player down :lernie:

https://www.dropbox.com/scl/fo/xiok1gg2hg5ob3fyb6fwl/h?dl=0&rlkey=6zv4rxrz0hdtit317j0l3ub8l

It's passed on so that we can try to reproduce and find a fix. Thanks again for your help.

[Radical Rat]

I totally forgot to save log file, but during last online game that Chrome Dome stunlock glitch was very prominent, where entire party ganked on him and pushed to the wall where he wasn't able to do anything. His health stopped at minimum and we had to do one more throw to kill him, but he lost almost entire health bar without switching phases

[Pikachu]

Yeah, at first I thought that Leo was the one causing it, but when I moved to the left side and saw that it was only from normal combos I was like "oh well, time to remember, save that log" of course I forgot to upload it, but since I haven't started the game again I can save and upload it.

https://www.dropbox.com/s/taalry6uufnq2d1/chromedomelog.txt?dl=0

The one that I absolutely forgot to save and upload was one that I couldn't see Super Shredder's clones,

[ÀlaReskoos]

Originally posted by Pikachu:

Yeah, at first I thought that Leo was the one causing it, but when I moved to the left side and saw that it was only from normal combos I was like "oh well, time to remember, save that log" of course I forgot to upload it, but since I haven't started the game again I can save and upload it.

https://www.dropbox.com/s/taalry6uufnq2d1/chromedomelog.txt?dl=0

The one that I absolutely forgot to save and upload was one that I couldn't see Super Shredder's clones,

Hello Pikachu, thanks for the files. I add this to the report.

[Pikachu]

By the way, it still can happen:
https://www.twitch.tv/videos/1710480092?t=0h59m12s
Or like I said when Chrome Dome was finished: UNGA BUNGA.

[ÀlaReskoos]

Originally posted by Pikachu:

By the way, it still can happen:
https://www.twitch.tv/videos/1710480092?t=0h59m12s
Or like I said when Chrome Dome was finished: UNGA BUNGA.

Thanks again, I'll also take some fresh logs if possible.

[Pikachu]

Right, forgot to add it: https://www.dropbox.com/s/sd9wj5vdvst6epk/stunlocklog.txt?dl=0

[ÀlaReskoos]

Originally posted by Pikachu:

Right, forgot to add it: https://www.dropbox.com/s/sd9wj5vdvst6epk/stunlocklog.txt?dl=0

Perfect, I have everything. Thanks again for your help.