Fae

I would guess this is, yet again, the discord.py intents error. After version 1.5 of discord.py, you need to specify "Intents" which tells discords API and discord.py you actually intend...

Try adding the members intent to your bot and see if this error persists. Check here for more info on using intents in discord.py: https://discordpy.readthedocs.io/en/stable/intents.html

I'm not sure if I completely understand your issue here. The new verify builders do make the output a bit more lengthy, but you can still specify a message expression...

I may be wrong, but CraftSpider might be working on something related to setting or cleaning up the assertion errors. There was mention of a similar issue in the discord...

WordPress trac has a reference to the problem function, and maybe a more compatible solution than my first. > A typical way to do this would be to use `array_values()`...

`call_user_func_array` is at least faster than doing a manual loop. Unpack via `...` isn't available until 5.6 which I guess we can assume no one uses php older than that...

@kasparsd What can I do to help patch this bug? Shall I fork and make a PR for one of the changes I've mentioned in this issue? Which method would...

I don't have an M1 apple to test with, but this issue might have been resolved. See these two links for more details related to this error: https://github.com/Rapptz/discord.py/issues/8046 and https://github.com/python/cpython/issues/92892

This should be possible to implement via the use of [QMainWindow::tabifyDockWidget](https://doc.qt.io/qt-5/qmainwindow.html#tabifyDockWidget) @Mudlet/lua-interface should this be implemented as an argument on the existing lua function or as a new lua function?

Mudlet already supports some `dockingArea` features in the `openUserWindow` function parameters. I think the acceptable values would need to be reworked to support this feature. While I like the idea...