Generally, code like this doesn't simply stop working abruptly on its own. At least not under these particular circumstances. My guess is it has nothing to do with my code but rather internal changes to GameMaker's macOS runner which doesn't play well with my extension's pre-existing code. Meaning, I didn't break anything, but YoYoGames did. This is something I need to make accommodations for quite a bit over the years, because they constantly break how my code interacts with theirs, forcing me to either file a bug report, (and hope they fix it), or be left with having to attempt a workaround to the problems they created, on my end, even though it isn't my responsibility to fix what they break.

That said, thanks for bringing this to my attention. I'll see what I can do to get this resolved.

Hey, I updated the extension and it now works on macOS! I'm not sure what made the difference to be honest. I made some technical changes on how it is used and it no longer has the problem you mentioned. Please test it and let me know if it works on your end. Turns out I was way too quick to blame YoYoGames for this... Originally, I was trying to fix an issue that someone reported of it not working on Linux. When I fixed it on Linux, by some weird chance, it happened to fix the macOS bug as well. As usual, I recommend seeing what's different in the demo project; it is slightly different now.