-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow group creation outside of cogs #4
Comments
I understand the issue but this is intended, you must define the group before adding any commands to it. Otherwise, the library would have to replace all missing and unloaded groups with placeholders, which is unnecessarily complex and would create confusion. |
I am not sure if we are on the same page or if i am missing things that work behind the curtain, but as per my example above, i want to create the group before loading any extensions. The problem is that currently, i am forced to always load the cog that creates the group. If i change the load order or want to remove it, there is no group anymore and the rest of the cogs will fail to load too, which completly defeats the purpose of having dynamic loadable cogs/extensions. You could seperate group creation and adding to a group like in my example above or even put both into the same decorator, which then checks if that group exists and creates it if not. Something like |
What you're asking for requires an overhaul of the storage and loading systems for cogs and commands. I will try my best to write a clean implementation. Don't expect it too soon though. |
Update: I now have a working implementation, waiting on Pycord-Development/pycord#2299. The next release of |
Currently it seems like a cog must create a group for other cogs to be able to join it. This only works if you have an always loaded (at least in the beginning) cog that spawns the group. This is counterproductive as cogs are meant to by dynamically loaded and unloaded.
Something like this should go around that issue but it does not work.
The text was updated successfully, but these errors were encountered: