-
Notifications
You must be signed in to change notification settings - Fork 12
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 channel-specific modules #49
Comments
Perhaps just make the list show only enabled modules and have a !list all
|
I don't think that's a viable solution. Any time I bring Kurea to a channel, I always do !toggle all-on to enable everything. Maybe this would function like a blacklist. |
So you want to whitelist modules per channel? Would this be defined in the module or at runtime? |
Certain modules, yes. General-use modules should always be whitelisted, whereas some should be only available in certain channels. I think it makes sense to have it changeable at runtime if you explicitly turn it on (!toggle force-on PhaserDocs for example), but it should be ignored in the general !toggle all-on or all-off. |
It would be nice if there was a way to make some modules channel-specific.
For example, I have considered making a Phaser Docs module to quickly navigate the docs, however, it does not make sense to show this module anywhere else. This would help clean up and compartmentalize the module list per group.
The text was updated successfully, but these errors were encountered: