I brought this to the attention to some members of the TAS discord and they said that this is not the bug due to the hangable ceiling causing the upwarp. Sorry.

I should add that requiring Mupen64Plus runs to prove that it is Mupen64Plus by showing the full window is a good compromise that I'll willing to deal with.

How long should I wait to see if it's allowed?

Yes, and it would be incredibly nice if this emulator, which has no issues other then what seems to be a misunderstanding about its name to be unbanned. 


The (what seems to be) official advice of running PJ64 1.6 under WINE simply isn't an option to me because A.) I can't get the controller plugins to actually work with my controller, and B.) Anything but the outdated default plugins shipped with 1.6 will not work. I have spent countless hours trying to fix it and I have gotten exactly nowhere.


I think it's ridiculous that the current advice for Linux involves using a hacky implementation of Microsoft's API to use an emulator released in 2011 when Mupen64Plus works perfectly fine, and is just banned due to a simple misunderstanding about its name.

That is Mupen64. Not Mupen64Plus. They are separate.

***Edit: This is now irrelevant.***

I'm left in the dark here about why the emulator, Mupen64Plus, is banned. At first I was led to believe that it was due to inaccuracy, however it appears that one of the two valid emulators, OpenEmu (Which is just a frontend to Mupen64Plus) is allowed. The only other reason I could find is inside this thread: https://www.speedrun.com/sm64/thread/cs0v1 which seems to be a misunderstanding between Mupen64 and Mupen64Plus and how the original Mupen64 is used for TAS. 

Mupen64Plus uses its own plugin standard which is ***completely incompatible*** with any plugins written for either Project64 or the original Mupen64, and I have done countless searches in order to find any TAS plugins or features for Mupen64Plus and have come up dry every time. 

So my question is, what gives?