Revert to ProactorEventLoop
Tested the change and magically there isn't set_wakeup_fd errors
Can you give me a little background on this (or point me to some if it's out there already)? And which version of windows do you see the set_wakeup_fd errors?
So on previous bombsquad version you switced to using WindowsSelectorEventLoop due to the error set_wakeup_fd only works in the main thread, on test build 1.7.37 i reverted the change to the default windows event loop which is the ProactorEventLoop
and found that it works fine without the set_wakeup_fd errors.
I made this pull request to revert the loop to use the default which is the ProactorEventLoop so in future we detect what causes the errors maybe debug and fix it.
On the mod we made discord_richpresence to display what your currently doing on the game. I used external libraries to connect discord's api to bombsquad's.The libraries use the default event loops for each OS, this causes the module to conflict with the games code hence errors. I then have to manually edit the libraries scripts again inside the mod script making it tedious, modders then sometimes lose intrest.
Curious why this was closed? Did something change? (sorry I've been slow taking a proper close look at it).
I went ahead and did this change on my own in the latest build, so I'll go ahead and close this. Thanks!
@efroemling would you mind checking your dm