Show Last IP in /openrights

[jake13jake]

I'm thinking, whenever someone uses /open account on RC to look at an IP of someone, a large amount of the time it's so that they can add the IP to the IP range in /openrights account. However, I've really been wanting to simplify adding new staff on Classic since currently it requires opening five windows which is like making a mountain out of a molehill. I'd prefer just having to add a staff member to the server ops and setting their rights.

On Classic, the staff list looks like:
staff=(Manager),Polo,(LAT),latadmin,latmembers,(FA Q),faqadmin,faqmembers,(GP),gpadmin,gpmembers,(GC) ,gcadmin,gcmembers

I find myself wanting to take this list and making a script that sets the player's guild if they're in their division of this list rather than using guilds.txts. Just in general, be able to simplify the process of adding/removing staff members. I mean, the only solution for being able to focus on many tasks is overkill, and overkill is in no way efficient. Otherwise you could end up forgetting to remove a person from the guilds.txt when removing them from staff and they could still go on tag and abuse the scripted rights built into having the tag on.

The other solution for having so many tasks to focus on is simplifying the tasks through innovation. Which is why I'm posting this.

[xXziroXx]

Sort of something like this?

PHP Code:

for (i = 0; i < serverstaff.size(); i ++) {
  blahahaha;
} 


Basicly, an array of all staff listed in the staff= section of the server options?

[Chris]

Oh wow now you're just being lazy.

[xXziroXx]

Nah, its a good idea. Would make so-called *staff NPCs* ten-thousand times more secure aswell by instead of (for instance) enabe it for everyone in the string serverr.staff, you can check if the player is listed in the server options.

[jake13jake]

Originally Posted by Chris

Oh wow now you're just being lazy.

In a sense I am being lazy. In another sense I'm concerned about security.
Having to look through five different windows when adding/removing a new staff can be a problem. Flaws are bound to occur because of the lack of simplicity, which is the security problem, and with being lazy, it would save a lot of time for having to change the flags of scripts.

It would also improve security if you could test a player's IP against their set IP range for RC.

Ex. Use of staff boots, god mode... Not to mention, one of my staff's accounts was recently stolen.

Testing for staff tags can already be done on a scripting level so I'm not concerned about this.

[ApothiX]

The last-IP in the changerights thing is a little too much. If you're that concerned about it, write a client-rc and make the modifications yourself.

There is a way to read the staff= variable serverside. I just can't think of it off the top of my head. However, I believe Stefan frowns upon people putting (blah) separators in their staff= list, though.

[jake13jake]

Originally Posted by ApothiX

The last-IP in the changerights thing is a little too much. If you're that concerned about it, write a client-rc and make the modifications yourself.

There is a way to read the staff= variable serverside. I just can't think of it off the top of my head. However, I believe Stefan frowns upon people putting (blah) separators in their staff= list, though.

I didn't write Classic's serverops, and you can get the staff list using onreceivetext for the serverops. (or so I'm told)