Port to nextcord

[greeeen-dev]

Checklist

• [X] The same feedback was not posted yet.
• [X] This is not a suggestion for the moderation team.
• [X] All info applicable to the issue has been attached.

Is your feature request related to a problem? Please describe.

Unifier currently uses Novus, which is unfortunately well behind other discord.py forks.

Describe the solution you'd like

Port Unifier to use nextcord.

Describe alternatives you've considered

Considered porting to hikari and discord.py, however:

• hikari would take up too much time, preventing us from improving Unifier while we port it
• discord.py doesn't like context menu commands in cogs

Additional context

This will pretty much scrap Unifier v1.3.x. All of its planned features will be moved to a ported Unifier v2.

v1.1.x will have its lifetime extended while we develop v2, especially since Micro is still using it. Instead of upgrading Micro to v1.2.x base, it will jump directly to v2.0.x base.

Installer will continue to use Novus, however it will install nextcord when installing Unifier. Might add a Novus uninstaller, because I might need pycord for voice support but it also uses discord folder just like Novus and discord.py

[greeeen-dev]

After some further reading I've decided to use Nextcord.

[greeeen-dev]

Port to Nextcord is done, pending testing

(ui.py is a godsend, helped me get things done at least an hour or two faster)

[greeeen-dev]

Core features work flawlessly!

I've licensed ui.py under MIT license, because I feel like this could be really useful for Novus users wanting to switch to Nextcord and similar.

[greeeen-dev]

As of now 100% of Unifier has been ported