In this case I find the admin system in SourceMod somewhat limited. It would probably be better with named permissions in a hierarchy. A permission entry could look something like this:
Code:
"Permissions"
{
"MyPermissionGroup"
{
"myPlugin.theFeature.anAction" "deny"
}
}
Then plugins would be able to define custom permissions in this global namespace. Basically a similar system as
Bukkit Permissions in Minecraft where you get full control of any feature in any plugin.
__________________