At 05:11 PM 7/20/98 -0400, you wrote:
>At 03:27 PM 7/20/98 -0500, you wrote:
>>>I am looking for help on how to make it so builders can have 3 zones
>>>instead of just 1 to edit. Thanks
>>
>>The only way I know of is a p-wipe. Change the integer holding the players
>>olc zone in structs.h to something along the lines of:
>>
>>int olc_zones[MAX_ZONES_PER_PLAYER - 1];
>>
>
>It can be done less elegantly without a pwipe, by using 2 of the spare
>entries for olc_zone2 and olc_zone3, then checking those in addition to
>olc_zone when looking to see if someone has access to a zone. The code
>gets uglier, but no pwipe is necessary. (Actually, if you find 3 spares of
the
>same type in a row, you could replace them with an array of 3 values, and
>-probably- be ok.)
Or do a whole new system.
Make a file, called perms.zon in the zon directory, which you will have
db.c parse on startup. Add to the zone structure a linked-list containing
ID numbers of players allowed to edit the zone.
Make a zperm command that adds to/removes from the perms.zon file and the
structure.
Not a simple procedure, but it's how I _PLAN_ to do it. I think that's how
Obuild does it, which I like better than the way Oasis does it. (I may be
wrong, but Obuild's zone allow/deny setup is more elegant than Oasis, and
is pfile independent).
-B.
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST