[ADMN, DEV] Permissions - WIP 
18 comments [Admininstration, Developer Tools] Permissions
Do you really think you've a good admin management with customizable rights? I am LOLing at you
With Permissions you don't need to write own admin management like here
or even
Happy Camper's work
HC Admin Script 1.9.3 (226) where you only have 4 different groups (oh, sweet
)
or
Starkkz's Admin Script (146) where you have 10 different groups.
In general:
At the moment, scripters need to code their own admin management, admins have to edit directly the scripts files to give/remove rights.
This is unflexible and hard, that's where Permissions come into play

What's so good about Permissions?
For Admins:
You decide which commands users can use. Everything is done in Permissions, you don't need to touch other scripts.
For Scripters:
No need to waste your time writing own rights management! Permissions does everything for you, a single function call is enough.
How it works:
There are groups, there are users and now there are permission nodes. Scripters tell which permission node is used for a command in their script and then admins simply grant the permission to a specific user or group so they can use the command.
Features: 
Flexibility: unlimited groups and users
Multiple groups per user
Inheritance: don't need to add same permissions to all groups
Example: group [Admin] can additionally have all nodes from groups [newbie], [member] and [moderator]
High performace: no problems with >9000 permission nodes per user
Per-map permissions
By far that's only a handful of features and usages of Permissions. The default config also contains prefixes and suffixes that can be used by chat scripts. Permissions can even be used as config for other scripts
Setup Permissions:
Put the contents of archive into autorun folder
Edit the config in /Permissions/config/permissions.lua as you wish
Information for scripters:
Every time you look at the code 100 cute kittens die a painful death.
> Don't mind the shitty code
Do you really think you've a good admin management with customizable rights? I am LOLing at you

With Permissions you don't need to write own admin management like here
or even




or


In general:
At the moment, scripters need to code their own admin management, admins have to edit directly the scripts files to give/remove rights.
This is unflexible and hard, that's where Permissions come into play


For Admins:
You decide which commands users can use. Everything is done in Permissions, you don't need to touch other scripts.
For Scripters:
No need to waste your time writing own rights management! Permissions does everything for you, a single function call is enough.

There are groups, there are users and now there are permission nodes. Scripters tell which permission node is used for a command in their script and then admins simply grant the permission to a specific user or group so they can use the command.








By far that's only a handful of features and usages of Permissions. The default config also contains prefixes and suffixes that can be used by chat scripts. Permissions can even be used as config for other scripts


Put the contents of archive into autorun folder
Edit the config in /Permissions/config/permissions.lua as you wish

Every time you look at the code 100 cute kittens die a painful death.
> Don't mind the shitty code
edited 1×, last 29.06.14 09:31:48 pm

Comments
18 comments



Log in!
You need to log in to be able to write comments!Log in

Wat? I have better group rank system
I can add a rank and permissions in config by function file hue and more...
EDIT:
Oh, but you still have a fuck*d config file. I have simpler.

I can add a rank and permissions in config by function file hue and more...
EDIT:
Code:
permissions.create.group(name, parent)
Oh, but you still have a fuck*d config file. I have simpler.
edited 2×, last 01.07.14 09:54:17 pm
@
_Yank: If I weren't lazy, it would also be finished by today


@
VADemon: If this were released earlier it would be a success. VADeamon Permissions configs would replace admin scripts



I need more time to improve the description, but current priorities are like this:
groups < per-map < team (upcoming) < user
So groups are kinda the lowest rank among permissions and user is the highest
@
mafia_man: You wrote your own permissions system. Good. If I was about to create a 20 line long script (in this example I am new to Lua etc.), why should I care about making my own system? I'd rather "outsource" this work to an external script.
Prefixes and suffixes: Permissions only acts as a storage there, so any script can access and use the options.

Prefixes and suffixes: Permissions only acts as a storage there, so any script can access and use the options.
Quote:
At the moment, scripters need to code their own admin management, admins have to edit directly the scripts files to give/remove rights.
This is unflexible and hard, that's where Permissions come into play
This is unflexible and hard, that's where Permissions come into play
That is not true, some of them like me wrote their own permissions system, and dynamic commands which you can modify without restarting server like me.
Instead of prefixes and suffixes you should use chat format string. Example:
Code:
1
"©255255255ש255242000VIP©255255255× ©255242000%PLAYERNAME%©255255255: %text%",



