Re: Adding additional custom flags to Sourcemod
Just use the admin overrides file to make commands for custom flags, I use one to make skins available to public players by using the 'p' flag and then just assign the flag to the player (or group) on sourcebans.
Your admin overrides text file would look like this.. Quote:
|
Re: Adding additional custom flags to Sourcemod
Perhaps it's suitable for commands, but some plugins also have actions or events and need to implement their own set of permissions.
Plugins could just use custom flags to control permissions to specific features, but that may conflict with the same flag in other plugins where you want access to one feature in one plugin, but not in another plugin. |
Re: Adding additional custom flags to Sourcemod
Quote:
|
Re: Adding additional custom flags to Sourcemod
So we could just make fake command strings like "myPlugin.myFeature" and override those instead? Though they would still need to be mapped to flags. In some cases it would be enough to just be a member of a group.
|
Re: Adding additional custom flags to Sourcemod
Quote:
As for default flag mapping, it's just a matter of making sane choices (if it's a public plugin, else just go wild as you know how you'll be setting up overrides). Some simple default recommendations (for things that don't have a sane equivalent flag of their own): Public: 0 Any admin: Generic No-one: Root One silly thing some people do that could screw this up: Give other people the Root flag. It's basically designed as a complete override to the admin system, for the server console. |
Re: Adding additional custom flags to Sourcemod
Quote:
|
Re: Adding additional custom flags to Sourcemod
Quote:
Give everyone all permissions and then find out who will abuse what and only remove those permissions from said abusive admins. |
All times are GMT -4. The time now is 11:03. |
Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.