playerrights\isstaff
 

i think there should be something like.....


players[index].rights={matrices for 1/0(true false) of all rights available)}

and

isstaff

ie:
if (isstaff){dostuff cuz they are staff wow;}

detects if their ac cis in the staff=

Shouldn't this be in future improvements?

Anyway, the idea of the rights array is good. Would provide better security for staff tools et cetera.

it is in future improvements

Only because one of the moderators moved it. It used to be in the Graal Main Forum I think.

and just what would be the benifit of these improvements?

Better dection of if the player is a staff or not. You could be able to check if a player just has NC to let him in a certain room. Or let people with the NC have debug acces to a NPC.

Like:

NPC Code:

---

if(playerisstaff[3]==true){

  //stuff here

}

---

Being the 4th place in the variable is the NC option.

edit: ofcourse this would be read only :)

:(

Could you imagine a corrupt Level Maker or Scripter making a simple npc that would let him\her gain level 4 rc?

which is exactly why he wants it =.=

I'm pretty sure he already has level 4 RC on 2k1 and I know he does on Bomy Development considering he runs it :)

2k2debug and 2k2 -_-

heh, I doubt Loriel would do that though :)

Not necessarily. I requested this a long, long time ago to make safe(r) Staff NPCWs. You could (on an NPCServ) do off-RC jailing NPCs with this - if you are a authorized (and only if you are authorized), run this code which sends this account to this cell.

Could already do off-RC jailing and other ultrasafe staff NPCs with a well-secured admin NPC, perhaps with encryption, a changing password, and probably account lock.

you obviously dont know loriel :p

1) Encryption fails quickly
2) Changing passwords likewise
3) Account locks are much harder

All that seems unnessacary(sp?) if this "Future Improvement" was made.


I know him pretty well :\

1) #E/passwordmatches encryption is heretofore unbroken.

2) If the password changed automatically to a random string every Saturday night (or when prompted by certain persons) and was PMed to the correct people at their next logon, password changing would be pretty infallible, though the idea is that this would be used along with account locking to protect against account theft.

3) Fetch a string array from a DBNPC, or even better, hardcode it into the script. Used with regular password changes and vigilant GPs, this would be virtually infallible.

...but still way more work than the comprable playerrights flag.

Thats what I have been trying to say :\

On Classic we are reading the rights by checking the guild tag. An advantage is that you can only use the tools while being on duty. (Which is usefull since we have to use player accounts for staff jobs now. I wish we had the good old staff accounts back...)

What serer doesn't?

Well, if you wanted to give people rights that doesn't require RC, such as warpto, warp players, edit attributes (can be simulated), etc, etc, you could just use a clientr.string and then have a NPCW with a fancy GUI. Well, a fancy GUI isn't necessary, but hey, it would be nicer. The NPCW could only display the available rights for them, or have the rights they can't use be greyed out or something of the sort.

You don't need to jail anyone. It should be timed bans like I suggested last year. Thats it for punishment.