*** Builder advice *****
Ross Williamson
commands for my MUD. What I would like to start some discussion on
is "good" builder commands. ie all of you who have played on builder muds
before and "built" something what where some of the commands that
you liked the best. What commands would you like to see?
At the moment I have all the basic commands that you need, but I'm
just curious to know what you other builders think.
TIA
+-----------------------------------------+--------------------+
| Name : Ross Williamson |Auckland University |
| E-Mail : ro...@ccu1.aukuni.ac.nz | New Zealand |
| Of course these opinions are my own and thank !! for that |
+--------------------------------------------------------------+
"Holy Zarquon singing fish." Zaphod
- From the Hitchhikers Guide To The Galaxy.
Santiago Zorzopulos
> I'm currently in the process of writing a number of builder
>commands for my MUD. What I would like to start some discussion on
>is "good" builder commands. ie all of you who have played on builder muds
>before and "built" something what where some of the commands that
>you liked the best. What commands would you like to see?
> At the moment I have all the basic commands that you need, but I'm
>just curious to know what you other builders think.
Here's the creation command list have on Armageddon DikuMUD:
W O R L D B U I L D I N G
-------------------------------------------------------------------------------
RNAME (22) - "rname <room name>"
RLINK (22) - "rlink <dir> <room number>"
RLINKRM (22) - "rlinkrm <dir>"
REXIT (22) - "rexit <dir> <room number>"
REXITRM (22) - "rexitrm <dir>"
RFLAGS (22) - "rflags <flag>"
RSECTOR (22) - "rsector <sector>"
RCREATE (22) - "rcreate <room number>"
RDESC (22) - "rdesc"
REDESC (22) - "redesc <keywords>"
RDDESC (22) - "rddesc <dir> <direction desc>"
RDKEY (22) - "rdkey <dir> <key>"
RDOOR (22) - "rdoor <dir> <keywords>"
WSAVE (22) - "wsave"
ZSAVE (22) - "zsave <zone>"
ZCLEAR (22) - "zclear <zone>"
ZRESET (22) - "zreset <zone>"
ZNAME (22) - "zname <zone name>"
ZSET (22) - "zset <zone> time|mode <value>"
O B J E C T C R E A T I O N
-------------------------------------------------------------------------------
ONAME (22) - "oname <obj> <object name>"
OSDESC (22) - "osdesc <obj> <object short desc>"
OLDESC (22) - "oldesc <obj> <object long desc>"
ODESC (22) - "odesc <obj>"
OEDESC (22) - "oedesc <obj> <keywords>"
OEDESCRM (22) - "oedescrm <obj> <keywords>"
OCREATE (22) - "ocreate <object number>"
OSET (22) - "oset <obj> <field> <value>"
OTYPE (22) - "otype <obj> <type>"
OAFFECT (22) - "oaffect# <obj> <value> <mod>"
OVAL (22) - "oval# <obj> <value>"
OSAVE (22) - "osave <obj>"
OCOPY (22) - "ocopy <obj> <obj>"
OEFLAGS (22) - "oeflags <obj> <extra flag>"
OWFLAGS (22) - "owflags <obj> <wear flag>"
N P C C R E A T I O N
--------------------------------------------------------------------------------
MNAME (22) - "mname <mob> <mobile name>"
MSDESC (22) - "msdesc <mob> <mobile short desc>"
MLDESC (22) - "mldesc <mob> <mobile long desc>"
MDESC (22) - "mdesc <mob>"
MCREATE (22) - "mcreate <mobile number>"
MSET (22) - "mset <mob> <field> <value>"
MDUP (22) - "mdup <mob>"
MSAVE (22) - "msave <mob>"
MAFFECT (22) - maffect <mob> <affect>"
-------------------------------------------------------------------------------
Hope this gives you some ideas.
-Jhalavar
Raja S Kushalnagar
>ro...@ccu1.aukuni.ac.nz (Ross Williamson) writes:
>
>
>> I'm currently in the process of writing a number of builder
>>commands for my MUD. What I would like to start some discussion on
>>is "good" builder commands.
>
>
>RLINK (22) - "rlink <dir> <room number>"
>OVAL (22) - "oval# <obj> <value>"
>MSAVE (22) - "msave <mob>"
>MAFFECT (22) - maffect <mob> <affect>"
A long list of other similar commands deleted.
>
>Hope this gives you some ideas.
>
>-Jhalavar
IMHO, I think this is the wrong way to go about it. It is better to have
one command control the actions of a related set of actions, rather than
have separate commands for each of those related actions. It is much more
realistic to parse recursively, until you have nothing left, than to have
a lot of commands and trying to remember them all.
e.g., on my mud, Sequent II, I have but one single powerful command for
manipulating anything in the game.
setbit <char | other options> <name> <appropriate 2nd option for 1st option>
<name> <further options if need be> <name> etc.
If you are unsure what options are available, merely type upto that stage
and press return; the game will then show you the options and prompt you
further. And the code to do this is not at all complex. It's just a matter
of recursively parsing and matching until you have nothing left.
This is analogous to a GUI menu which enables you to see what options are
available, no matter what context you are currently in, rather than, say
Messydos's excessive reliance on function keys, where even the keyboard
templates are not sufficient to ease the learning curve.
Oh well.
- Duke - Duke - Duke, Duke of Sequent.