This Banana took forever for me to get as a kid
https://invidious.snopyta.org/watch?v=wQspd_6ppO8
@coolboymew
I can't wait for someone to create a DK64 decomp so we can finally fix this poorly coded mess of a game, especially that memory leak that made this game require the expansion pak in the first place.
@coolboymew Even with the expansion pak, the game will still crash after around 10 hours (really only a problem if you are playing with save states). And it is still theoretically possible to bypass the no-expanison pak detected screen with gameshark codes, so we can see if the game really made use of the expansion pak and see how frequent these memory leaks happen.
@coolboymew I don't know that much about GameShark, but I heard it took years to find a way to load Citadel from Goldeneye using it. I could imagine the same for this. And I think the story with the expansion pak came from a recent-ish interview, so someone might be working on it as we speak.
But still, that has to be way harder than skipping the expansion pak check
@coolboymew I almost never hear of DK64 hacking, so I expect the hacking community to be small compared to Goldeneye's hacking community which is probably at the levels of modding communities of most PC games at this point.
And even with a huge hacking community it still takes years to access or bypass something like the DK64 expansion-pak check. For example, the PAL and iQue versions of SM64 has a crash debugger that still nobody knows how to access. (The decomp is the NTSC version which lacks this debugger)
