Sly 3 - "Hungry Croc" Softlock

Channel:

SlyCooperReloadCoded

Subscribers:

4,160

Published on March 7, 2023 11:29:09 AM ● Video Link: https://www.youtube.com/watch?v=3yy2tEhN_SM

Game:

Sly 3: Honor Among Thieves (2005)

Duration: 2:36

258 views

22

This is a recent discovery, and half of the glitch with the same name found on the Sly Cooper wiki, submitted in 2017:

"Hungry Croc softlock

In the job "Hungry Croc," if the player picks up an enemy right before the cutscene where Bentley tells Murray about the flashlight guard, when the cutscene concludes Murray will briefly be holding an invisible enemy. This is corrected shortly after. The rest of the mission will progress as normal, until Murray has to throw the guard to the crocodile. The crocodile will fail to spawn, and the thrown enemy will turn invisible after approximately one second after being thrown. This is a softlock, which prompts the user to restart the console."

The first part, where you pick up a guard and it disappears, has an answer but no recreation yet. Basically, due to the way the guards are handled in this part, and Bentley's voice line telling you about the flashlight guard marks the point where the game starts spawning guards normally again, it's likely that the submitter picked up a guard with ludicrously-precise timing and the game despawned a guard in his hands, which does cause the behavior the submitter described.

However, the second part was a bit more interesting to solve. Entities don't just despawn randomly, so I theorized he could've been proxied away, as I've seen the crocodile walk across the ground on rare occasions, and this game does have weird physics sometimes, even on PS2. However, it was found that if you use Guttural Roar when the crocodile is at the furthest-way-from-the-level point of his swimming path, he moves just far away enough to reach the edge of the map and die. It's likely the submitter used Guttural Roar without looking in the direction of the crocodile and just assumed that his literally 1-in-1,000,000,000,000 glitch had something to do with it.

Either way, it's nice to see this one finally figured out.

Other Statistics