Joe & Mac 2 / GAME HISTORY
Why Joe & Mac 2 Freezes at the Dinosaur Door
The music kept playing, but the door would not open. A long-running report now has a targeted patch and a clearer explanation.
Short answer
Entering the locked Murky Swampland door with the key while riding a ground dinosaur can stall Joe & Mac 2. Snaphat’s published analysis says the door clears the riding marker, but ground-mount movement keeps running. The door then waits for a player state that never arrives. [1]
Scope: SNES Joe & Mac 2: Lost in the Tropics, USA version targeted by the linked patch. Historical reports and published code analysis; Patchlo has not tested the patch.

The music carries on. Your character does not.
The August 2020 Snes9x report describes a very specific stop: touch the door while riding the dinosaur and control disappears, while the music continues. That is a better starting point than “this game crashes,” because it tells us what the player was doing when progress stopped. [2]
The report lived on an emulator tracker, so an emulator problem was an understandable suspicion. In 2021, a contributor discussed timing but said the exact cause was still unknown. A 2024 reply then reported the same freeze on a real SNES using an EverDrive. That is a user report, not our own hardware test—and not evidence that someone tested an original cartridge.
The door and the dinosaur disagree
On October 19, 2026, snaphat linked a patch in the old discussion. Its explanation is straightforward: the door starts getting the rider ready to enter, but the ground dinosaur's movement code does not notice that the riding marker has been cleared. The sequence never gets as far as requesting the key animation. [1]
The patch adds a check to the ground-mount handlers, following a check already used for the flying mount. When the marker is gone, the game goes to the existing dismount routine. This is the author's code-level explanation and proposed fix; we have not independently run it.
The useful change in the story is the evidence. First came a stuck character, then reports beyond one emulator, then a patch aimed at a particular version and condition. Blaming Snes9x alone no longer accounts for everything in the thread. Calling every release fixed would go too far in the other direction.
Join the conversation
Have a question, correction or a different take? Share it below. Comments appear immediately after submission.
Reader comments
Loading comments…