NC Restrictions

[Gambet]

I believe Stefan should implement a restriction system to NC, in which if a player does not have specific rights, any changes that are made to NC (classes/weapons,etc) that they add/update would be kept in a "Waiting for approval" section of NC. Basically, any additions/updates must be approved by a higher staff before they are put into effect. Once an npc/update is approved, it automatically adds to NC or over-rides a current script. I believe this would be useful for managers and administration to keep track of new NAT's and any other position that would require NC.


So, this would mean that a system would have to be created in which administration would have to appoint certain rights to players. These rights can include:

-Reading rights //Allows you to view code without restriction
-Re-Writable rights //Allows you to view/update code without restriction
-Deleting rights //Allows you to remove npcs without restriction
-Adding rights //Allows you to add npcs without restriction

and then there could be a seperate box right for those that will be placed under the restriction above.

I believe this would help servers administer what updates are made to the servers scripts, what items are deleted, and so forth. Servers always have problems with corrupt staff ruining scripts or with NATs messing around with scripts. This would definitely increase server security, script wise.

[Skyld]

In terms of more flexible rights, perhaps a better idea is to keep the rights framework similar to how it already is.

For example, the current system works on the "r", "w" and "-" switches. Perhaps a new switch could be added to prevent the deletion of NPCs, say:

PHP Code:

rwd NPCS/SomeDatabase 


... would prevent you from deleting the NPC, but:

PHP Code:

rw NPCS/SomeDatabase 


... would allow you to delete the NPC.

It seems pointless adding rights to allow the adding of NPCs, though.

[Ibonic]

Originally Posted by Skyld

PHP Code:

rwd NPCS/SomeDatabase 


... would prevent you from deleting the NPC, but:

PHP Code:

rw NPCS/SomeDatabase 


... would allow you to delete the NPC.

Personally I'd rather see that the other way around, as in rwd allowing deletion. It's more consistent and seems like common sense to me (no w = no write, no d = no delete) ...
I know this would require many people who use just rw now to change their rights, but that could be a good thing - managers would be forced to consider who actually needs deletion rights. And I know files can still be overwritten, but this could possibly at least slow down those common intentional mass deletions on playerworlds which I and others frequently need to look into.

[KuJi]

While your at it: Folder Rights should not allow you to edit your own folder rights..I mean..I limit my staff w/ some folders and give him hiring rights, then he opens his rights..and gives him rw */* etc..

And now he has access to EVERY folder and can easily delete things and see private folders where I keep some backups.

[Warcaptain]

Yes, folder rights are somewhat flawed.. only designated staff should be able to modify their own folder rights.

Also.. it would be pointless to add a delete option because someone who really wanted to remove a script could just erase the whole thing or replace all of the code with a single line of code (if you tried to make it so not able to delete meant not able to make the file size 0 too) so this right is pointless..

[KuJi]

Warcaptain: But their should be that deletion for the levels.

And:

For Change Folder Rights:
You should require Folder Configurations to change your own folder rights..or so.. Because I do not give that right to none but myself..and my co-manager and I trust my Co-Manager enough to know he would never 'screw' me over..and he hasn't in 4 years or so since I've known him.