Login
User Name:

Password:



Register
Forgot your password?
Vote for Us!
tintin++ ogg sound player script for linux
Author: Robert Smith
Submitted by: Vladaar
6Dragons ogg Soundpack
Author: Vladaar
Submitted by: Vladaar
6Dragons 4.4
Author: Vladaar
Submitted by: Vladaar
LoP 1.46
Author: Remcon
Submitted by: Remcon
LOP 1.45
Author: Remcon
Submitted by: Remcon
Users Online
CommonCrawl, Remcon, Yandex, DotBot

Members: 1
Guests: 9
Stats
Files
Topics
Posts
Members
Newest Member
481
3,735
19,370
618
Micheal64X
Today's Birthdays
There are no member birthdays today.
Related Links
» SmaugMuds.org » Codebases » AFKMud Support & Development » Level 101 and Up command rest...
Forum Rules | Mark all | Recent Posts

Level 101 and Up command restructure
< Newer Topic :: Older Topic > suggestions?

Pages:<< prev 1 next >>
Post is unread #1 Mar 5, 2004, 12:42 pm
Go to the top of the page
Go to the bottom of the page

cynshard

GroupMembers
Posts95
JoinedNov 19, 2003

I'm expanding the current REALMs to cover many different jobs within the game and I've reached several problems. Not all jobs I want to have will fit easily within the current level-based system. What I'm thinking of doing is adding realm[] (or job) as a member of the command structure. Where realm would be all the realms that may use the command. Then I could set all commands to lvl 101. I could then restrict sensitive commands like player discipline and things like reboot to higher levels, so that no matter what your job is, you can't use that command unless you have had it bestowed. Has anyone else ever tried this? Any major flaws that would make this impossible?

Thanks,
Cynshard

P.S. All this was brought on by an idea to rewrite promote to work with jobs instead of just promoting one level at a time.

P.S.S Also, I was thinking of being able to bestow groups of commands based on realm as well.
       
Post is unread #2 Mar 5, 2004, 2:59 pm
Go to the top of the page
Go to the bottom of the page

Samson
Black Hand
GroupAdministrators
Posts3,643
JoinedJan 1, 2002

Well, you could leverage the existing council system to cover this. It's one of the reasons it got left in despite the majority response to the poll indicating it should have been removed.

Councils can have commands assigned to them that only that council can use. So it seems like it would fit what you want, at least partially. What it ultimately sounds like you want is a new set of command flags along the lines of:

Admin, Builder, Coder, Quest, Enforcers, etc.... and so forth. This wouldn't be overly difficult to setup. Commands could be flagged as one group, flagged for multiple groups, or not flagged at all. A perfect example is the CMD_GHOST flag which will eventually be used to allow commands being used by PC's who are ghosts. Any command not flagged as such is rejected.
       
Post is unread #3 Mar 5, 2004, 7:38 pm
Go to the top of the page
Go to the bottom of the page

Greven
Magician
GroupMembers
Posts204
JoinedMar 5, 2005

I have actually done this exact thing, using command flags, matching them with immortal flags. Wasn't hard, a little time consuming to set all the commands, but not difficult.
       
Pages:<< prev 1 next >>