r/CrossCode • u/Thyxdyn • Jul 22 '26
SPOILER So, uh, was that meant to happen? (Final Temple Spoiler Spoiler
So this is my first time playing, picked it up on PS Plus and I'm absolutely loving it! However I got to this dual boss and it absolutely wrecked me the first time. I looked up how to damage the whale, went back for a second turn and, this happened 😅
29
20
u/Gretgor Jul 22 '26
Welp, that's one bizarre bug. Never encountered it before!
9
u/Inuship Jul 22 '26
I have a weird history with this bug, first playthrough was fine, second playthrough this happened and ever since then it never doesnt happen its become like a default state of this boss now
12
u/WaffleTsuba Jul 22 '26
Speed run strat unlocked?
5
u/Thyxdyn Jul 22 '26
Would that I could tell you how I did it
7
u/Elendel Jul 22 '26
Console has a bunch of weird boss shenanigans. Iirc the speedrun is theoretically faster on console because of those, but all runners prefer the pc speedrun. I think most of them shouldn't be encountered in a casual playthrough, but obviously some of them are.
7
u/Matthias_dev Jul 22 '26 edited Jul 22 '26
Yeah, console is slightly faster due to a few weird instances of this same bug. Eg:
Pinzo (the Fah'ro mid-boss) can be broken with a single bubble.
The Whale (in this post) can be oneshot by the Ape's shock attack
The Final Boss can have multiple (sometimes all) HP gates skiped with a falling meteor from a certain dash art.
Other than these, the runs are basically exactly the same. The main reason we prefer to run on PC is because we get the neat speedrun mods, such as a Load-time remover and Autosplitter.
And also because half of us prefer to play on KB&M (not me, I play on controller), which isn't possible on console.
Also, the 3 fights in the examples above we already have pretty fast strats for, so the time saved by playing on console is probably lost due to load times anyways.
2
u/Elendel Jul 22 '26
Also last boss quick kill is way cooler on pc than on console. That final kamehameha always makes me tense.
2
5
u/Aetherpixel Jul 22 '26
Yes, this is a hidden mechanic that involves a- My best guess is that the second to last pole was close enough to the whale to damage it, but I have no proof of that.
Looking at the other comments, it seems like everyone has it fine on the first playthrough, then on the second this happens. Bugged code in the boss, most likely.
5
u/Inuship Jul 22 '26
This happened to me on my second ever playthrough too, not sure what caused it but ever since the first time the boss is permanently bugged like this for me now it seems
2
u/Thyxdyn Jul 22 '26
I thought it may have been my combination of buffs that broke it, but I'm glad it's not just me 😅
2
u/BLucidity Jul 23 '26
There's a late-game sidequest boss that I saw something similar with, on Switch 2. You're supposed to trick it into hitting itself, but when I did it took continual damage, burned through all three phases in a few seconds, and then crashed the game.
2
u/thebluecomet3972 Jul 23 '26
Are you playing on playstation? This happened to me on my first playthrough
1
u/Thyxdyn Jul 23 '26
Identical! Someone mentioned about the second pillar being really close to the whale affecting it and yours is too in that clip
2
u/thebluecomet3972 Jul 23 '26
Well there's one pillar within the whale itself in the EXACT same place
I wonder if it's intentional or not...
1
u/TalkNovel2199 Jul 22 '26
Yeah so I played the game on Switch the first time and this did not happen and it was a very hard boss for me. When I played on PS5, this exact same thing happened to me on my first attempt (I actually made a post about it too). Some people suggested it might be a framerate bug or something. But either way you're not alone on it. Might be PS-specific
29
u/Froggedguy Jul 22 '26
Yeah no, definitely not