This is fine. 🔥 Good job Matt
It's pretty crazy how much faster this run has gotten. Ironically, it's probably a little less entertaining to me now since so many stages are skipped, but the play is great. Yes vote.
This kind of thing happens sometimes, where glitches in published runs are discovered to be emulation bugs . I believe Super Mario Land 2 had an issue like this as well? Since we don't unpublish runs for any reason, the only thing to do is to just submit an improvement run that doesn't use the glitch, or in your case I suppose it means using the glitch in a different way that doesn't crash on console. It won't have any impact on how the run is judged, don't worry. It's the same sort of thing as when we get new, more accurate emulators, and we end up getting improvement runs that are actually "slower" than published runs (note that the obsoleted run appears to be over 10 seconds faster, but this is due to the new run including the PS1 BIOS). The more console-accurate run will always be preferred, even if the accuracy makes it slower in the end. Hopefully that clears things up!
Judging from the title, the provided video appears to be on console, so it looks like it's being handled correctly on BizHawk. If the glitch only works without crashing on PSXjin, that'd be an emulation error, and it wouldn't be allowed. I imagine the only reason it was allowed then is due to the fact that PSXjin is the best we had at the time, and there wasn't enough research done to know whether or not that particular glitch worked the same way on console. It's unfortunate, but that's the way it goes with accuracy.
