People who wander the MU and use @take to acquire their own areas are being very helpful.
Some of the staffers have a passion for finding and fixing areas. Once found and fixed, though, they are stuck. Without having someone that wants them, they end up "sitting on them" and being responsible for them forever.
It's been suggested a couple of times that a command be written to give rooms to Atlas. This is important, and I will do it. This doesn't solve the problem above, though, because when Atlas owns a room, the staff maintain it, but NOBODY links to it except by staff approval. Specifically, Atlas owned areas are meant to provide the skeleton but don't make homes available. Only "large" areas or "necessary" links are made from or to Atlas-owned areas.
Another idea is to create a Builder character for the areas which are owned by staffers and set that builder character control flag to the staff, so any staffer can help if someone wants to work with land that is owned by the builder, not JUST the "one and only one" owner.
A different idea is to transfer ownership BACK to Chown_Char, thus allowing playesr to @take and do as they like.
Yet another idea is to set the land to Atlas and make some rooms +community so that players can build without any permission at all.
I'm open for other suggestions as to what commands (besides "+giveTo <whoever>") we need to add to make it easier for staffers to manage areas and for players to do things without being blocked when particular owners are offline.
I'll be coding the solution the weekend after next, so get your suggestions in soon.
Thanks!
Keep the Light, Otter
Comment
My two cents...
Posted by:
Chaosat
2005-05-21
Personally, I'd make the Builder character that the staff can control. Essentially make Atlas the Second who can be linked to, and is beyond what is necessary for the "skeleton" of the muck.
I'm not sure how people would react, but perhaps this Builder could have access to work on any and all areas. Give the Builder building priviledges muck-wide. Some areas might disagree, but it's just a thought.
I read the comments. I'm hesitant to give anyone power over things owned by players, but I don't mind giving power over canon areas to the staffers.
So, anyone who owns a canon area that is NOT already owned by a builder should contact me and I'll grant permission to use "+give" to transfer the canon area to the CanonBuilder.
Then, we can use all the canon areas to send TPs throughout the MU.
Some of the staffers have a passion for finding and fixing areas. Once found and fixed, though, they are stuck. Without having someone that wants them, they end up "sitting on them" and being responsible for them forever.
It's been suggested a couple of times that a command be written to give rooms to Atlas. This is important, and I will do it. This doesn't solve the problem above, though, because when Atlas owns a room, the staff maintain it, but NOBODY links to it except by staff approval. Specifically, Atlas owned areas are meant to provide the skeleton but don't make homes available. Only "large" areas or "necessary" links are made from or to Atlas-owned areas.
Another idea is to create a Builder character for the areas which are owned by staffers and set that builder character control flag to the staff, so any staffer can help if someone wants to work with land that is owned by the builder, not JUST the "one and only one" owner.
A different idea is to transfer ownership BACK to Chown_Char, thus allowing playesr to @take and do as they like.
Yet another idea is to set the land to Atlas and make some rooms +community so that players can build without any permission at all.
I'm open for other suggestions as to what commands (besides "+giveTo <whoever>") we need to add to make it easier for staffers to manage areas and for players to do things without being blocked when particular owners are offline.
I'll be coding the solution the weekend after next, so get your suggestions in soon.
Thanks!
Keep the Light, Otter
Comment
My two cents...
Posted by: Chaos at 2005-05-21Personally, I'd make the Builder character that the staff can control. Essentially make Atlas the Second who can be linked to, and is beyond what is necessary for the "skeleton" of the muck.
I'm not sure how people would react, but perhaps this Builder could have access to work on any and all areas. Give the Builder building priviledges muck-wide. Some areas might disagree, but it's just a thought.
Replies to this comment
Comment
Builder created
Posted by: otter at 2005-05-28I read the comments. I'm hesitant to give anyone power over things owned by players, but I don't mind giving power over canon areas to the staffers.
So, anyone who owns a canon area that is NOT already owned by a builder should contact me and I'll grant permission to use "+give" to transfer the canon area to the CanonBuilder.
Then, we can use all the canon areas to send TPs throughout the MU.
Thanks!