CREATOR TIPS * For details on the Quick Creation System: http://dead-souls.net/example.html * If you get stuck in the editor type a single dot on a blank line, then enter, then Q, then enter, like this: . Q * PRIVACY: You can enable and disable a privacy field around your workroom with the command: privacy This will prevent unwanted visitors from entering, except for arches. * Admins: there is a new command: admintool It is a menu-driven system that will make your life easier and simplify tasks like locking the mud, changing the mud's name, creating new currency, the works. * Edit .plan in your homedir to let others know what you're working on. You can see other people's plans when you finger them. * You can test how functions work without having to code a command or object. The "eval" command will let you evaluate functions. For example: ------------------------ eval return this_player()->GetName() eval return find_player("cratylus") eval return present("sword",find_player("testylus"))->GetClass() ------------------------ * The "boards" command will tell you which chat boards have posts you have not read. * Navigate and manipulate your files and directories with the standard unix commands: ls, cd, cp, mv, more, ed, grep. Be careful: just like in unix, if you delete a mud file, it is gone for good. * To toggle chat channels on and off, just type the channel name. If you're listening to intergossip, for example, you can turn it off by just typing: intergossip * Use test characters. If you test stuff on yourself and screw up your character file, you will be sad. * To create good code, you should look at what people have already done. Look in /domains/town and /domains/default and you'll find some examples. Copy some to your home directory and use them as templates for your own creations. * Remember that once you finish editing a file, you have to use the "update" command to load it into memory. If you change a file you've already updated, you have to update it again for the changes to take effect. * If you get errors when you try to update a file, use the "elog" command to get clues as to what is wrong. Most of the time it is something simple, like using "=" where you meant to use "==" or forgetting a semicolon. The LPC programming language does not forgive typoes any more than any other programming language. * Before changing a file, make a backup copy, for example: cp file.c file.bak This way, if your changes really cause a problem, you can easily restore things to the way they used to be. * The admins and elders are here to help and answer questions. But remember: if your request is basically "fix my workroom!" or "fix my code!", your request will probably wind up at the bottom of the priority list. We want you to learn to solve coding problems, and fixing your code for you isn't the best way to make that happen. However, we're happy to look over your code and make suggestions. * Permissions and privileges: For security reasons, all creators do not have read/write access to everything. You can read and write any file in your home directory. You only have write permissions within your home directory and the /tmp directory. You can read everything outside the /realms and /secure directories. You can't read anything in other creators' home dirs. Your read access to some items in the /secure directory is limited. If you're full admin, of course, you have full access to everything.