Derek Dreamweaver has been helping with naming
Tawane has been helping with world building
 

Here are some behind the scenes variables that I wanted to hang on to
for the NERO MOO
 
---------------------------------------------------------------------------
to modify welcome message:

@edit $login.welcome_message
enter

                   ..
                 .//
                ///.
 /\-.__________// |\-----'--------------------------------------------------\
(  >)/////////(< +) =~-~-=--------------------------------------------------->
 \/_p~~~~~~~~~~\\ |/-----,--------------------------------------------------/
                \\\'
                 `\\
                   `'

Welcome to Reverie, the Nero Ashbury MOO. This is a virtual world created so
Nero players and characters can interact online in a comfortable
and familiar atmosphere.

To walk our world as a guest, type: connect guest
When you're ready to leave, type:   @quit
If you need help right now, type:   help
.
save
quit

-----------------------------------------------------------------
This is what it originally said:
"I don't understand that. Valid commands at this point are
WELcome, Who, COnnect, CReate, Quit, UPtime, Version, REQuest, or Help
 
--------------------------------------------------------------------
@edit $login.help_message
enter

From the login prompt, you can do the following:
Log in as a guest:                    connect guest
Log in as your existing character:    connect [character] [password]
End this session:                     quit
See who is currently online:          who
See how long the world has been up:   uptime
See the software version running:     version
See the welcome message again:        welcome

To request a permanent character on NERO MOO,
send email to moomaster@swiftmail.com with your character name and a
little info about yourself.

.
save
quit
 

-----------------------------------------------------------------
character creation via @create has been disabled
I still have to disable @rename so players can't be anonymous

everone who wants to get on must @request a username
To disable automatic character creation, I set $login.create_enabled to 0

-----------------------------------------------------------------
No teleportation in NERO Moo!   (except programmers and Wizards)
I did:  @set #3.free_entry to 0
that sets generic room to be no teleportation. Also, all existing rooms are no
teleportation.  (remember that the block only stops incoming teleports)
 

-------------------------------------------------------------------
 

sign on the wall near the fire in the tavern
@edit #186.description
enter
Welcome to the Dragon's Flagon. In case this is your first visit, here
are some pointers for you:

xxxxxxxxxxx

save
quit

-----------------------------------------------------------------
A dimly lit stone hallway leads to several rooms here. to the south is the conference room where many a noble and merchant meet to discuss business and to the north is the Inn where tiresome adventurers rest their weary heads dreaming of gold and adventure.
 

"A long oak table filled with dagger markings and bloodstains sits here with a
dozen chairs along side it. Many a debate has been witnessed here."
 

@dig up,u,upstairs,steps|down,d,downstairs,tavern
 

-----------------------------------------------------------------
Here are the original news articles that came with LambdaCore

Tuesday, February 11, 1997
WELCOME TO LAMBDACORE
Getting Started with your LambdaCore MOO
========================================

Thank you for choosing LambdaCore!

Initial Setup Notes
-------------------

The "welcome" screen, seen when a player connects.
  -- this is stored in $login.welcome_message

Do you want on-line character creation?
  -- this is stored in $login.create_enabled
     for more detailed information, edit $login:player_creation_enabled

Do you want to limit the number of players on the MOO at once?
  -- look at $login.max_connections
     the `connection_limit' message on $login is the message printed
     when this limit is reached.

Do you want a different default player class?
  -- set $player_class to a different value
     *do not* change $player

You should also set the following:
  $network.postmaster
    -- your email address, or the email address of the person who will
       handle your email
  $network.site
    -- the machine your MOO is running on (e.g. "lambda.moo.mud.org")
  $network.port
    -- the port your MOO is running on (e.g. 8888)
  $network.MOO_Name
    -- the name of your MOO (e.g. "LambdaMOO")
  $site_db.domain
  -- this is set to the `domain' of your address
     (eg `foo.com' for `moo.foo.com')

If you compiled the server with open_network_connection() enabled (allowing
 the MOO to open up connections with other computers on the network), then you
 should set
  $network.active = 1
     This will enable @newpassword, @registerme, @password, @mailme,
 @netforward, and others to send mail from the MOO.

-------------------------------------------------------------------

Setting Yourself Up
-------------------

Set a password for yourself.
  -- @password <new-password>

Set a description for yourself.
  -- @describe me as <anything>

Set a gender for yourself.
  -- @gender <gender>

There are, also, a large number of messages you can set on yourself.  Setting
 them will enhance the virtual reality.
-------------------------------------------------------------------

About Guests
------------

To make a new Guest character:
  -- @make-guest <guestname>
     will make a new guest with the name you specify with `_Guest' appended
     and some other standard but useful aliases

This is the easiest way to make Guest characters.  The most important things
 to remember about Guests, if you want to make them yourself, are:
  -- make them owned by nonwizards, and not owned by themselves
  -- make sure they've got .password == 0, and that .password is nonclear
  -- at least one Guest must always be named `Guest'; this can be an alias

To set the default description and gender for a guest:
  -- set .default_description to the description the guest should start with
  -- set .default_gender to the gender the guest should start with
  -- remember to set .description and .gender too, for the guest's first use

-------------------------------------------------------------------

Adding to the Newspaper
-----------------------

The newspaper is a special mailing list.  To add a post to the newspaper, send
 mail to it (as *News or $news), and then note the number of your post (let's
 call it <x> and:
  -- @addnews <x> to *News
... in general, `@addnews $ to *News' will work as well.
Quota
-----

By default, LambdaCore runs with object-based quota.  This is the quota system
 documented in the LambdaMOO Programmer's Manual, directly supported by the
 server.  If you're satisfied with object-based quota, which serves some
 people's needs better than others', you needn't change anything.  However, an
 in-DB quota system, limiting users by total database space as opposed to
 total objects, has been designed, and is included here.

To enable byte-based quota:
  -- set $quota_utils to $byte_quota_utils
  -- start the measurement task; see `help routine_tasks' for more information
 (Note: this help topic contains information about more than just the quota
 task; it should be read regardless of how quota is set).

It's best that you make this switch before users start, because converting
 existing object-based users to byte-based users is an awkward (and inherently
 arbitrary and political) move.  You'd need to decide how much space your
 builders deserve, and it's all a mess.

-------------------------------------------------------------------

Making Programmers
------------------

The command to turn someone into a programmer is `@programmer'  Its syntax is
 `@programmer <user>'.  For example:
  -- @programmer Haakon
The `@programmer' verb will prompt you if the user isn't set up with a
 description and a gender.

No code to automatically grant programmer bits is included with LambdaCore.

Making Wizards
--------------

THINK CAREFULLY.

Be very careful before giving someone a wizard bit.  That person can do gross
 damage to your database, and fixable but serious damage to the machine it
 runs on.  That person can quite possibly open outbound network connections
 from your machine, and thus commit acts for which your host system will be
 blamed.  That person can ruin your MOO's as-yet-untarnished reputation.

Wizards have technical power, the ability to change anything within the
 database, to create anything within the database.  Be careful with the idea
 of a `Social Wizard' -- a nontechnical person holding a wizard bit is fairly
 likely to, at some point, accidentally do something destructive.  It's a good
 idea not to socialize as your wizard character, for the same reason, to make
 it less likely to be accidentally destructive.

That said, in general you don't turn an existing character into a wizard, you
 make a -new- character to be the wizard.  This is because the existing
 character probably owns code and objects which could be destructive if
 suddenly made wizardly; it's a good security measure to make a fresh player.
 So, to make a fresh player:
  -- @make-player (see `help @make-player' for more information)
     this will make you a new player. for this example, #123

To make #123 a wizard:
  -- @programmer #123
     (a nonprogrammer wizard is a truly strange beast)
  -- ;#123.wizard = 1;
  -- @chparent #123 to $wiz
 it less likely to be accidentally destructive.

That said, in general you don't turn an existing character into a wizard, you
 make a -new- character to be the wizard.  This is because the existing
 character probably owns code and objects which could be destructive if
 suddenly made wizardly; it's a good security measure to make a fresh player.
 So, to make a fresh player:
  -- @make-player (see `help @make-player' for more information)
     this will make you a new player. for this example, #123

To make #123 a wizard:
  -- @programmer #123
     (a nonprogrammer wizard is a truly strange beast)
  -- ;#123.wizard = 1;
  -- @chparent #123 to $wiz
  -- ;#123.public_identity = <the player's nonwizard character's object number>

-------------------------------------------------------------------

Good luck with your new LambdaCore database!

Visit us at LambdaMOO: lambda.moo.mud.org 8888

Join the international mailing list for MOO coders: send an email message to
 moo-cows-request@xerox.com with the word `subscribe' as the body of your
 message.

Do good things.

The LambdaMOO Wizards
[authored February 7, 1997]

(end)
 
 
 
 
 
 
 
 
 
 

-----------------------------------------------------------------
-----------------------------------------------------------------
-----------------------------------------------------------------
-----------------------------------------------------------------
-----------------------------------------------------------------