Thank you for choosing LambdaCore!
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 = 1This will enable @newpassword, @registerme, @password, @mailme, @netforward, and others to send mail from the MOO.
@make-guest <guestname>This 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:
To set the default description and gender for a guest:
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.
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:
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.
@programmer HaakonThe `@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.
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:
To make #123 a wizard: