allow channel-specific modules

[seiyria]

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.

[rahatarmanahmed]

Perhaps just make the list show only enabled modules and have a !list all
for all of them?
On Jun 27, 2014 11:29 AM, "Kyle Kemp" [email protected] wrote:

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.

—
Reply to this email directly or view it on GitHub
#49.

[seiyria]

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.

[rahatarmanahmed]

So you want to whitelist modules per channel? Would this be defined in the module or at runtime?

[seiyria]

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.