From: nveid Date: Tue, 11 Jan 2011 03:19:05 +0000 (+0000) Subject: CobraMUSH Personalization Related Items: X-Git-Url: https://git.theari.com/?a=commitdiff_plain;h=3076896c5e8e30bf62f777ee2b5c0c9ebfca77f8;p=cobramush.git CobraMUSH Personalization Related Items: Ignore-this: 7cf42106337147f95820de9f2624ad0a 1) Removed distributed PennMUSH INSTALL, UPGRADING & README file in toplevel directory as well as README in game directory. a) Will need to create a CobraMUSH specific ones in the future. 2) In mushcnf.dst, replaced references of PennMUSH with CobraMUSH (even though this file may very well be a lua script by the time 0.80 is done) 3) Edited README in txt directory to reflect this is CobraMUSH as well as mentioned changes.txt in it 4) pennmush.evt in evt txt directory renamed to cobramush.evt 5) Added TODO in toplevel directory 6) email in options.h changed to devteam@cobramush.org --- diff --git a/INSTALL b/INSTALL deleted file mode 100644 index 89c2f32..0000000 --- a/INSTALL +++ /dev/null @@ -1,196 +0,0 @@ -============================================================================ - Installation Guide to PennMUSH 1.7.x -============================================================================ -This file explains how to install PennMUSH. It comes in three parts: - A. Important background - B. Installation from source (recommended) - C. Installation of precompiled binaries (only for Windows platforms) - -If you are upgrading from a previous PennMUSH release, this is -probably not the file you want to start with. Read the UPGRADING -file first. - -DISCLAIMER: Before attempting to run a MUD of any sort, you should have -some reasonable knowledge of UNIX and C. If you do not, it is _strongly_ -suggested that you learn UNIX and C to some reasonable level of competency -before attempting to set up a MUSH. (Note that even people using the -Windows ports are encouraged to know UNIX, because that's the paradigm -that PennMUSH was built with, and most resources will be written with -UNIX is mind.) - -You may also want to take a look at Javelin's Guide for PennMUSH Gods, -at http://pennmush.org/~alansz/guide.html -or by ftp from pennmush.org, /pub/PennMUSH/Guide -============================================================================ - -A. Important background - -Here's a quick picture of the organization of the MUSH directory tree. -The "src" directory contains C source code. The "hdrs" directory -contains header files for the source code. The files used by a running -MUSH are in the "game" directory, which includes subdirectories "data" -(current databases), "txt" (text files and directories for building them), -"log" (log files), and "save" (backup databases). Finally, the "hints" -directory is used during the installation process, the "po" directory -holds translation message files, and the "os2" directory contains files -of using in building for OS/2. - - pennmush--+-> src - +-> hdrs - +-> game ------+-> data - | | - | +-> txt -------+-> nws - | | +-> evt - | | \-> hlp - | | - | +-> log - | \-> save - +-> hints - +-> os2 - +-> po - +-> utils - \-> win32 - - -PennMUSH has been tested on a fairly wide variety of machines and -operating systems including at least: - - NeXT Mach 2.1 - Sun Sparc SunOS 4.1.x - Sun Sparc and i386 Solaris 2.x - DEC Decstation Ultrix 4.x and OSF/1 - DEC Alpha OSF/1 and Linux - SGI Indy Irix 5.x and 6.x - HP 9000 series HP-UX 8.x - IBM RS/6000 AIX 3.2 - IBM S/390 Linux - Novell Unixware SVR4 - Linux - FreeBSD - AT&T SVR4 - Windows 95/NT cygwin and MSVC++ - OS/2 - -There's no real reason why PennMUSH shouldn't compile on any 32-bit -or better BSD, System V, or POSIX operating system. Javelin does his -development on a Linux PC these days. - -If you have serious problems, contact Javelin and he will try to help -you. Email is the best way to get a fast response; in an emergency, you -can bother him on a MUD, but for code problems, email will probably get -you a better response. - -============================================================================ - -B. Installation from source - - The quickstart version of the installation is: - -1. On win32 only, install proper tools or read win32/README.txt. -2. sh Configure -d or some variant -3. create options.h, or make update -4. make install -5. possibly make customize -6. Read game/README and follow those instructions - - Here's the process in detail: - -1. If you're running on win32, there are two options known to work: - a. Compile with MS VC++ or VS.NET. If you want to do this, read - win32/README.txt and then skip down to step #6 below - b. Compile with the Cygwin unix emulation tools (http://www.cygwin.com) - In addition to the base cygwin stuff, you'll want the following packages: - binutils, gcc, make, patch, perl, exim (the latest *source* code - package, not the binary) - (gcc 3.2 is recommended.) - These are also recommended: - gettext, gettext-devel, indent, vim or emacs - It is recommended that you install the tools under C:\CYGWIN and - that you read the Cygwin FAQ if you get messages about HOME not set. - - Put the pennmush .tar.gz file in C:\CYGWIN\USR\SRC. Don't uncompress - it with Winzip or other windows tools! - - VERY IMPORTANT: The rest of the instructions assume that you have - started up a bash shell and are running commands under that shell -- - they won't work right if run directly from a DOS shell. - - cd /usr/src, and unpack the .tar.gz file with: - tar xfz pennmush-whatever.tar.gz - -2. cd pennmush. On Unix systems: - ./Configure -d - - On cygwin systems, try ./Configure -d, but if it fails, try: - . Configure - (That's a single period, a space, and Configure) - When you get to the question about hints files, choose 'cygwin'. - For all other questions, the defaults should work. - -3. EITHER: - -Copy options.h.dist to options.h. Note that these files stay in the -pennmush directory. - -Edit the file. It's liberally commented. - -On Cygwin systems, you should *not* define NT_TCP with cygwin, and you -should use MALLOC_PACKAGE 0. You may use an COMPRESSION_TYPE you prefer. - -Also, cp game/mushcnf.dst to game/mush.cnf and edit. - -On cygwin systems, you probably should not use compressed database, -so modify that bit. - -OR: - -Type 'make update', and answer all the questions about which MUSH -options you want. - -You should not need to change any of the other header files. - -4. On cygwin systems, add to the CCFLAGS in the Makefile: - -I/usr/src/exim-4.20-1/minires - (or whatever the latest exim source directory is) - -5. Do a "make install". This will build all the necessary files, and -set up some symbolic links for the restart script. You will probably -receive a few compilation warnings, which can generally be ignored. - -6. If you plan to run multiple MUSHes, you may want to do a "make -customize" which will run a script to help set up a separate customized -game subdirectory for each MUSH (run it once per MUSH you plan to run). -Files in these subdirectories will already be customized in many ways, -so what follows may be slightly different. :) This is probably broken. - -7. Read game/README and follow those instructions. - -A final thing you may want to think about is compiling announce.c or -portmsg.c. These are port announcers; if your MUSH ever goes down, you can -set one up, and a message will be given to a person attempting to connect -to that port. Read that file for details. It is not an official MUSH -piece of code; rather, it is a freely distributable program available -via anonymous FTP that is included in this code because it happens to -be fairly useful. Javelin suggests using portmsg - it appears to be -more stable. - -============================================================================ - -C. Installation of precompiled binaries (only for Windows platforms) - -A pre-built binary is frequently available for win32 users who don't -want to customize their MUSH server, and don't feel like compiling it -themselves. This binary distribution may not contain the src, hdrs, -hints, or os2 directories and may be missing several key files (like -Configure) from the pennmush directory. It does include the options.h -that it was built with, as an aid to those who decide later that they -want to customize the server; they are useful as a baseline to work from. - -Using the pre-built binary is fairly simple; adjust your configuration -file as in game/README, then go to the game directory and run -PennMUSH.exe (you may need to use PennMUSH /run or PennMUSH /start). -Alternately, if you want the MUSH to automatically start each time you -turn on your machine, you can install it as a system service by running -'PennMUSH /install'. PennMUSH can be removed from service status via -'PennMUSH /remove'. - diff --git a/MANIFEST b/MANIFEST index 03e0342..be07577 100644 --- a/MANIFEST +++ b/MANIFEST @@ -47,7 +47,6 @@ game/txt/hlp/pennvOLD.hlp game/txt/nws/base.nws COPYRITE I18N -INSTALL MANIFEST Makefile.SH Patchlevel diff --git a/README b/README deleted file mode 100644 index b0c4aa4..0000000 --- a/README +++ /dev/null @@ -1,237 +0,0 @@ -============================================================================ - User's Guide to PennMUSH 1.7.x -============================================================================ - -Some of this Guide was written by Amberyl, and is used with permission. -Most of it is by Paul/Javelin. This most recent version has been -updated by Alex/Talek and Javelin. - -Installation information can be found in the files INSTALL or -UPGRADING, depending on whether it's a new install or an upgrade. -The file I18N discusses internationalization. - -I. Introduction and history -II. Getting Help, Reporting Bugs -III. Getting a .pennmush.org hostname and mailing lists -IV. Comments - -You may also want to take a look at Javelin's Guide for PennMUSH Gods, -at http://pennmush.org/~alansz/guide.html -or by ftp from pennmush.org, /pub/PennMUSH/Guide -============================================================================ - -I. Introduction and history - -PennMUSH uses a version-numbering system that includes version -numbers (like 1.7.2) and patchlevels (like p32), usually written -together (1.7.2p32). - -Starting with 1.7.2, version numbers that are even (like 1.7.2) are -stable releases - patchlevels on the latest stable release will only be -issued to fix serious bugs. Version numbers that are odd (like 1.7.3) -are development releases - patchlevels on the latest development release -may include new features as well as bugfixes, and development releases -may not be as stable as stable releases. On the other hand, some new -features may *increase* stability without fixing bugs per se, and it's -quite likely that later patchlevels on the development version will be -more stable than those on the "stable" version. - -PennMUSH is a TinyMUD derivative, and one of the branches along the MUSH -line. "Vanilla" TinyMUSH, which added the "v" registers and functions to -the basic TinyMUD building commands, was written by Larry Foard. The code -was later expanded by Jin, of MicroMUSH. In January of 1991, MicroMUSH -changed its name to MicroMUSE, and the code there continued to develop -under the MUSE name. At that same point in time, Moonchilde took the -last public release of that code and began a series of improvements -and extensions. - -That code was released as PernMUSH, named for the MUSH that Moonchilde -was running. The last released version of that code was version 1.15, -at the end of November 1991. PernMUSH itself had switched over to -TinyMUSH 2.0, which Moonchilde had co-written with Glenn Crocker -(Wizard of TinyCWRU); there was no longer a reason for Moonchilde to -maintain this code. - -In January of 1992, Amberyl began working on the PernMUSH 1.15 code -release, for TinyKrynn. She took over the code, which no one was -supporting, and is continuing to work on extending this code, as well -as improving its compatibility with TinyMUSH 2.0. She changed the name -to PennMUSH (named for her school, the University of Pennsylvania), to -avoid the confusion that resulted from PernMUSH actually running -TinyMUSH 2.0. - -In January of 1995, Amberyl passed on her mantle to Javelin (aka -Paul@Dune, Alan Schwartz), who is now the maintainer of the primary -public distribution in development. He released two patchlevels -numbered "dune-1" and "dune-2" before releasing PennMUSH 1.50 pl11 and -later distributions. The numbering scheme changed again with PennMUSH -1.6.0 (see CHANGES.OLD). - -Gradually during the early part of 1995, Alan formed the PennMUSH -development team with T. Alexander Popiel (Talek) and Ralph Melton. -The development process became more formalized, with official patches, -a dedicated bug reporting email address, and better tracking of -outstanding issues and history. - -In August of 1997, Ralph Melton left the PennMUSH development team, -and Thorvald Natvig joined as a new member. Many thanks go to Ralph -who contributed much time, code, and good cheer to PennMUSH. -Since that time, the development team has gained and lost members. -The current membership is usually listed at the top of the -latest CHANGES. file. - -In November 2002, with the release of PennMUSH 1.7.6, PennMUSH -began using the Artistic License (see the COPYRITE file), -an open source/free software license. This license was -simultaneously adopted by TinyMUSH (2.2.5, 3.x) and TinyMUX to -facilitate code sharing and widen use. - -A MUSH manual should be available at ftp.digex.net, ftp.math.okstate.edu, -primerd.prime.com, or from wherever you got this code from. The manual -should be numbered version 2.007 or higher. - -If you are planning on modifying the source code to PennMUSH, you'll -probably want Javelin's Guide for PennMUSH Gods, which should be -available where you got this code, or, in hypertext, as -http://pennmush.org/~alansz/guide.html. More recent versions -may be available at http://community.pennmush.org. - - Enjoy! - -============================================================================ - -II. Getting Help, Reporting Bugs - -Here are some guidelines about where and how to report bugs or problems -or generally look for help. - -There are three places one could get help with a problem: - -1. pennmush@pennmush.org is the PennMUSH mailing list. - To subscribe, visit http://www.pennmush.org/mailman/listinfo/pennmush - - The PennMUSH mailing list should only be used for problems, - bugs, suggestions, ideas, discussion, etc. that are OF GENERAL INTEREST. - It's often hard to say what's of general interest, but a good - rule of thumb is: - - Anything that occurs before the MUSH process is running is - *not* of general interest - - That is, don't report problems with downloading PennMUSH, compilation, - installation, restarts, or database corruption to the mailing list. - These are often system specific. - - (If you don't want to hear these discussions, but do want to be - informed of new patches, subscribe to pennmush-announce instead, - at http://www.pennmush.org/mailman/listinfo/pennmush-announce) - -2. pennmush-bugs@pennmush.org is the bug reporting address - for the PennMUSH developers (suggestions go to pennmush-developers, - bugs to pennmush-bugs). This will generally give you the fastest - response and is ideal for unusual bugs. A web-based submission - form is at http://www.pennmush.org/jitterbug/pennmush - -When reporting a problem, please always include the following -information: - -1. PennMUSH version number -2. The type of machine you are using (Sun SparcStation, IBM RS/6000, etc.) -3. The operating system and version (SunOS 4.1.2, AIX 3.2.4, etc.), -4. The compiler and compiler version (gcc 2.4.5, SGI cc 2.10, etc. -- the - 'file' command usually tells you the compiler version, if there's no - built-in option like '-v' or '-V' to give it), -5. Whether or not you have made any changes to the code. - -If the problem resulted in a crash and a core dump, a stack trace of -the core dump (see the section above) should also be included. - -If I need additional stuff (like a log of the Configure or make), I'll -ask for it, but if you know that it's relevant, you can send it along, -too. - -============================================================================ - -III. Getting a .pennmush.org hostname and mailing lists - -Thanks to donations from the PennMUSH community, Javelin was able to -register the pennmush.org domain name, and, if you're running a PennMUSH, -you can have yourmush.pennmush.org assigned as a hostname for your MUSH, -so players don't need to telnet to obscuresite.obscuredomain.com! - -NOTE: A hostname is not the same thing as a site. We don't have accounts -for you to run your MUSH from. You must already have your MUSH -running at someplace.edu or whatever -- we just provide a nice hostname -that will resolve into your current site's IP address. - -How do you get a pennmush.org hostname? Go to -http://lists.pennmush.org/pennmush.html, and follow the instructions. -It may take a day or two before the hostname will work. - -Thovald also has volunteered to host mailing lists for MUSHes in -the pennmush.org domain. Details are on the same web page. - -============================================================================ - -IV. Comments - -IV.a. Amberyl's Comments - -These are in the first person. :) - -I've been working with this code for a year and a quarter now. I can't -claim that it's particularly elegant or inspired; all I can say is that -it works (most of the time), and that I've had fun writing it. I'm -also hoping that it's quite readable; the sections I've added or -revised tend to be quite heavily commented. - -A number of people have been contributed a lot, directly and -indirectly, to PennMUSH; many of them are credited in copyright.h. -Read the file and embarrass them the next time you see them. ;) - -PennMUSH 1.50 patchlevel 3 contains the promised parser rewrite. A -great deal of the code is derived or directly taken from the TinyMUSH -2.0 parser; credit goes to JT Traub (Moonchilde) and Glenn Crocker -(Wizard) for writing the thing in the first place. In most cases, the -1.50 parser should now be functionally identical to the parser in -TinyMUSH 2.0.9; see the news file for a brief summary of the changes. -Major differences between the 1.50 and 2.0 parsers are almost certainly -bugs, and should be reported to me. - -I do have a life, though, and academics/job/social stuff take priority. -Thus, don't get too upset if it takes me a while to add your pet hack. -:) I'm generally happy to discuss code and life in general, though, so -if you see me on a MUSH, feel free to say hi. - - Enjoy your MUSH. - - -- Lydia Leong (lwl@digex.net) - "Amberyl" just about everywhere - -IV.b. Paul/Javelin's Comments - -And let me recognize T. Alexander Popiel, Shawn Wagner, Nick Gammon, -Dan Williams, Ervin Hearn III, Ralph Melton, David Cheatham, and Thorvald -Natvig, other past and present members of the PennMUSH development or -porting team. Working with them is a real pleasure. - -I am trying to keep extending the functionality of the server, while -optimizing and rewriting things wherever possible. I'm always -interested in improvements or ideas for the code, as well as anything -you might have done to get it to compile and run on unusual systems. - - - -- Alan Schwartz (dunemush@pennmush.org) - Javelin at most places - - -IV.c. Alex/Talek's Comments - -I would like to thank Ralph, Amberyl, Moonchilde, and all the others -who went either with us or before us. - -PennMUSH is the embodiment of many years of hard work by many people. -May it never stagnate. - - -- Alex (talek@pennmush.org) - diff --git a/TODO b/TODO new file mode 100644 index 0000000..84354e3 --- /dev/null +++ b/TODO @@ -0,0 +1,9 @@ +CobraMUSH Development TODO List +---------------------------------- +* Create Module/Plugin Core code. (Scheduled for 0.80) + - Removed cmdlocal.c, funlocal.c, and other local files in favor of module loading + - Move majority of commands & functions to modules divided into categories. + - Seperate Chat & Mail code into seperate modules +* Embed LUA Engine + - Move all configuration code to be one big LUA script + - Allow lua to be hooked to events, commands, functions, etc.. diff --git a/UPGRADING b/UPGRADING deleted file mode 100644 index 45c402c..0000000 --- a/UPGRADING +++ /dev/null @@ -1,153 +0,0 @@ -============================================================================ - Upgrading to PennMUSH 1.7.x -============================================================================ - -This file explains how to upgrade to a new version of PennMUSH. - -There are three basic upgrade situations: - A. You're running a stock ("vanilla") PennMUSH server of some - version and you want to upgrade to a later version - B. You've hacked your server source code a little bit here and there - (adding a flag, for example). Hacks to the *local.c files don't - count as hacks, as they're easy to handle. - C. You've hacked your server source code a lot. - -The PennMUSH developers actually only support situation A, but -we'll give some useful tips for B and C here, too. - -DISCLAIMER: It is very wise to always back up your current working -MUSH directories before you try an upgrade. You were warned. - -============================================================================ - -A. Vanilla upgrade - -You have basically two choices here: upgrade with patch files, or -build a whole new distribution. - -A.1. Upgrading with patch files - -This is the easiest way to upgrade your source code if you're -keeping up with patches as they come out, or if you're upgrading -patchlevels within a release (e.g., within 1.7.6). - -To upgrade with patch files, get all the patch files for higher -patchlevels than your current version. For example, if you're running -1.7.6p0 and the latest version is 1.7.6p4, you need patches 1-4. - -These files are stored at http://ftp.pennmush.org/Source and usually -named things like 1.7.6-patch02 (the patch from 1.7.6p1 to 1.7.6p2) -or, in some cases, 1.7.4p20-1.7.6p0.patch (the patch from 1.7.4p20 to -1.7.6p0). - -Each patch file contains instructions at the top explaining how to -apply it. FOLLOW THESE! Don't assume they're all the same. - -After you've applied all the patches and followed all the instructions, -you should be good to go. In most cases, you can simply @shutdown/reboot -after the final successful compile. If @shutdown/reboot crashes, -you'll have to restart again. - -A.2. Building a new distribution - -When you're upgrading across release and no patchlevel is provided -to make the upgrade (e.g. from 1.7.4p3 to 1.7.7p0), it's often -easier to simply build a new distribution following the INSTALL -instructions, but with your old configuration stuff. - -Move your older version of PennMUSH in a directory called oldpenn/, -unpack the new one (it will unpack into pennmush/). - -All of the steps below should be taken before running Configure for the -new version: - -A.2.a. options.h and game/*.cnf - -You can copy the options.h file and game/mush.cnf file from your -old version to the new version. The 'make update' command (run after -Configure) will compare your files with the newly distributed ones and -tell you about options that have been added or removed. If you have any -options defined that the new version doesn't recognize, you'll be asked -if you want to retain them (which is safe). - -If your mush.cnf file is called something else, copy it to mush.cnf in -pennmush/game anyway, since that's the file that gets updated. Then make -a link to that file called whatever.cnf if you want to use that. - -If you've modified the restart script, you'll have to decide if -your modified script is still appropriate, or modify the distributed -game/restart script again as you like it. The latter is encouraged. - -You can also copy your old game/access.cnf, game/sitelock.cnf, and -game/txt/*.txt files into the appropriate locations. You may wish -to do the same thing for game/restrict.cnf, but you should compare -it to the new version, as restrictions that may formerly have been -compiled into the server may now be specified in restrict.cnf instead. - -A.2.b. src/*local.c - -You should copy local.c, cmdlocal.c, and funlocal.c from oldpenn/src -to pennmush/src if you want to retain this local code. Of course, -it may not still work, but it's quite likely that it will. If you -don't have any such code, you can skip this step. - -A.2.c. Databases - -This MUSH version should read databases along the main branch of MUSH -evolution -- TinyMUD, vanilla TinyMUSH up to 2.0, MicroMUSH, and all -Pern/PennMUSH versions. If you need to convert a TinyMUSH 2.0 database, -please contact Amberyl, and she'll mail you an extension to 2.0 that -will dump a 1.50-readable flatfile. You're probably out of luck with -databases for TinyMUSH 2.2 and later. - -Be sure that your options.h settings correctly reflect the type -of password encryption that was used on your database. The default -has changed to SHS, so if your db used crypt(3) encryption, be -sure you set the appropriate definition in options.h. - -*** If you are upgrading from 1.7.4 (or earlier) to 1.7.7 (or later), -*** you must first load your old database under PennMUSH 1.7.6 and -*** then dump it, and load this converted database under your -*** target version of PennMUSH. PennMUSH 1.7.7+ can no longer read -*** 1.7.4 databases. - -============================================================================ - -B. PennMUSH with a few hacks - -When you have only a few local hacks outside of the src/*local.c -files, you can often patch up using the patch file method discussed -above. Alternatively, you can build a new version and reapply your -changes. - -One small exception is upgrading from a version that used the old flag -system to one that uses the new flag system (post-1.7.7p5), if you've -added flags or toggles. You probably had an #define in hdrs/flags.h -for your flag's bit value. This now should be moved to hdrs/oldflags.h; -you should leave in the table entry in src/flags.c. If you set up a macro -for testing your flag in hdrs/mushdb.h, you'll need to change it to use -the has_flag_by_name() function - see the many examples in that file. - -If this isn't suitable (you're crossing releases or your hacks are too -many for this to work cleanly), see below. - -============================================================================ - -C. PennMUSH with a lot of hacks - -If you've seriously hacked your server source code, you're on your -own in terms of keeping up with new patchlevels. Some people apply -patchfiles and fix the rejected hunks. - -A better approach is probably that described in the Guide for Gods, -and involves creating a set of patches from the distributed old -version of pennmush (e.g. 1.7.2p32) to your hacked version of pennmush -(e.g. 1.7.2p32 with hacks), and then applying those patches to the new -version of PennMUSH (e.g. 1.7.6p0) to create a hacked version thereof. If -some patch hunks fail, you'll have to apply them manually. - -Probably the best approach is to keep all multiple versions of the -code (old distributed, old hacked, new distributed, new hacked) under -a source code control system like prcs that can merge changes between -versions. See the Guide for Gods. - diff --git a/game/README b/game/README deleted file mode 100644 index 2251d7c..0000000 --- a/game/README +++ /dev/null @@ -1,127 +0,0 @@ - Run-time Installation and Configuration of PennMUSH - -This document assumes that you've successfully compiled and installed -PennMUSH as described in the main PennMUSH README file. - -The next step is to create your configuration file. In the game directory -is a file called "mush.cnf". If you don't have mush.cnf, but you have -mushcnf.dst, you can copy mushcnf.dst to mush.cnf. This file is a list -of all runtime configuration options with their default settting. Change -them as you see fit. IMPORTANT: do not _delete_ any parameters. They -all need to be there. - -WIN32: - Under win32 using the Microsoft compiler, ignore the restart script. - In the configuration file, turn off disk database compression; it is - not supported. Then go to the game directory and run PennMUSH.exe. - Poof, you're done. - -UNIX: - Edit the restart script. Change GAMEDIR to the path to the directory - containing mush.cnf. Read about the optional settings in that file. - The restart script is written for sh, and assumes a fairly standard - Berkeley UNIX setup. If you're on a HP-UX or SysV machine, for example, - you may need to change the restart script a bit (the ps options, - for example). Then run it. - -You should now be ready to start the game. This distribution can -general a minimal database - a God character, starting room, and -master room. The server will generate this database if it doesn't -find another database to load. - -If you're starting with the minimal database, the god character "One" -has no password, so you can log in without one. Of course, you should -immediately set one (via @newpasswd). options.h has the Master Room as -#2 by default; in the minimal database, this room is created for you. - -Now you should be set -- all you have to do now is customize the -.txt files in the game directory. - -The logfiles in the "log" directory generally contain useful -information. You will probably want to read your error logfile (defined -in mush.cnf) every time, since errors and other important messages get -printed to that logfile. - -============================================================================ - - Game Trouble-shooting - -If you ever run into trouble, the your first reaction should ALWAYS be -to back up your database. indb.Z.old is the file that the MUSH saves -indb.Z to when the game, restarted, indb.Z is the file that the MUSH -loaded at startup, and outdb.Z is the file to which the MUSH is -currently dumping the database. - -You can tell if a dump is (theoretically) complete by doing a -"zcat | tail -10". The last line should read -"***END OF DUMP***". If it doesn't, your database has been truncated -for some reason. Check the logfile. Possible causes include a full -process table, a full disk partition, or running out of disk quota. - -Occasionally the dump process may dump core. This is caused by some -sort of corruption in an attribute, normally. You can tell if the dump -process has died by looking in your data directory; you will see -something like "outdb.Z.#5#". Wait a few moments and check on the file -again. If it has grown, then the game is in the process of a normal -dump. If it hasn't, and there's a core file, then something has gone -wrong. You should definitely shout a warning that building is not being -saved. - -To attempt to fix the problem, do a @dbck to take care of any possible -minor weirdness in the database, then try doing a "@dump/paranoid", and -reading the checkpoint logfile (default is log/checkpt.log). This is -slow, but it will write out an uncorrupted database, and tell you what -it fixed. Back up that database and indb.Z, then figure out what you're -going to do next: you can take the game down with a kill -9, or attempt -to manually fix the problem by either @destroying the offending object, -or attempting to reset the attributes on the object that are causing a -problem. If "@dump/paranoid" dies, you are more or less out of luck. - -The game may crash from time to time. It will generate a core file, -usually; if you don't limit the coredumpsize or strip the executable, -you should be able to get some useful information out of it, using a -debugger. Javelin is interested in stack traces. You can do a stack -trace in the following manner: Go into the directory where you keep -your source code, and type - netmud ../game/core -If you don't call your executable "netmud", substitute in whatever -you do call it. - -You are looking for variables set to bizarre values - attempts to -access objects that aren't there, attempts to use pointers which point -to nothing, and the like. - -If you are using the "adb" debugger (don't do this unless you really -have absolutely nothing else available), you will see nothing. It's -loaded and ready, though. Type "$c". This will print out a list of the -functions it called. Type "$q" to quit. You can't really get much more -useful information out of adb. - -If you are using the "dbx" debugger, type "where" to see the stack -trace. You can move through it using "up" and "down", and see exactly -what the sequence of calls was. You can also use "print " to see the value of a variable at the time the game crashed. -The "gdb" debugger is similar to "dbx"; with that, you can abbreviate -"print" as "p". - -Javelin appreciates news of any bugs found, and any patches that have -been written to deal with them. He is also interested in any extensions -that people make to the code, and requests that ones that are of more -than just local interest be sent to him for inclusion in the next -release of this code. - -One important thing to remember is, if the MUSH refuses to start, there -is probably a good reason. Check the MUSH log, and the core file, if -there is one. Make sure to back up your database before attempting to -restart -- remember that every time it restarts, it overwrites -indb.Z.old. If you restart three times and somehow manage to trash your -database each time (for example, a full process table zero'ing out your -files), you won't have a backup to restart from, unless you've backed -up your database before trying! - -You can also find helpful tips in Javelin's Guide for Gods, -which is available on the WWW as - http://pennmush.org/~alansz/guide.html -and by ftp from pennmush.org as - /pub/DuneMUSH/Guide/guide-single.txt - diff --git a/game/mushcnf.dst b/game/mushcnf.dst index 39801bb..8de20f3 100644 --- a/game/mushcnf.dst +++ b/game/mushcnf.dst @@ -1,4 +1,4 @@ -# configuration file for PennMUSH +# configuration file for CobraMUSH # # The directives in this file control the behavior of your MUSH # If you change any of them while your MUSH is running, you can @@ -25,7 +25,7 @@ ip_addr # Should the MUSH attempt to resolve IP numbers to hostnames? # If yes, you'll see hostnames on the wizard WHO. If no, IP numbers. -# No makes sense if you're running PennMUSH at home and don't have +# No makes sense if you're running CobraMUSH at home and don't have # a DNS server you can access. MacOS 7/8/9 should use 'no' # Changing this while using info_slave requires a @shutdown/reboot # to make it take effect. @@ -136,7 +136,7 @@ names_file names.cnf ### ### Attribute (chunk) cache ### -### PennMUSH can swap rarely-referenced attribute text out to a disk +### CobraMUSH can swap rarely-referenced attribute text out to a disk ### file, and cache often-used attribute text in memory. This ### can result in substantial (typically 30-50%) savings ### in process memory use, at the cost of a very small performance hit. @@ -651,7 +651,7 @@ full_invis no # For TinyMUSH compatibility, the answer is 'no'. null_eq_zero no -# In PennMUSH, strings and db#s larger than #0 have traditionally +# In CobraMUSH, strings and db#s larger than #0 have traditionally # been considered true (1) in boolean functions like and(), or(), etc. # In TinyMUSH, strings and db#s evaluate as false (0) # Should we emulate TinyMUSH? @@ -659,14 +659,14 @@ tiny_booleans no # TinyMUSH's trim function is: # trim( [, [,]]) -# PennMUSH's trim function has been: +# CobraMUSH's trim function has been: # trim([,[,]]) # Should we emulate TinyMUSH? [+ for new MUSHes] tiny_trim_fun yes # In Tiny, strings used in math expressions evaluate to 0, # so eq(asdfa,0) = 1, gt(asdf,0) = 0, etc. -# In Penn, using strings where numbers should be is traditionally an +# In Cobra, using strings where numbers should be is traditionally an # error (returning #-1 ARGUMENT MUST BE NUMBER or similar) # Do you want the TinyMUSH behavior? tiny_math no diff --git a/game/txt/README b/game/txt/README index d616288..9744f22 100644 --- a/game/txt/README +++ b/game/txt/README @@ -1,11 +1,11 @@ Your local help/news/events/etc files can now be kept separate -from those distributed with PennMUSH, and can now be managed as +from those distributed with CobraMUSH, and can now be managed as a set of files rather than a single large file. Here's the details: -1. The source files for help.txt, news.txt, and events.txt are - kept in directories called hlp, nws, and evt respectively. +1. The source files for help.txt, news.txt, changes.txt, and events.txt + are kept in directories called hlp, nws, and evt respectively. 2. Files in those directories which end in . are considered to be part of the text. That is, files in hlp/ @@ -22,7 +22,7 @@ So, if you want to add your own news entries, make a file called nws/local.nws and put 'em there. Or maybe organize it into parts: nws/theme.nws, nws/code.nws, etc. -Files distributed with PennMUSH always begin with "penn", so don't +Files distributed with CobraMUSH always begin with "cobra", so don't start your files with that. You can also add files for "rules" and "index" commands if you diff --git a/game/txt/evt/cobramush.evt b/game/txt/evt/cobramush.evt new file mode 100644 index 0000000..3dca389 --- /dev/null +++ b/game/txt/evt/cobramush.evt @@ -0,0 +1,16 @@ +& help + +=========================================================================== + CobraMUSH Events +=========================================================================== + + +No topics written yet. + + + + + + +=========================================================================== + diff --git a/game/txt/evt/pennmush.evt b/game/txt/evt/pennmush.evt deleted file mode 100644 index 3dca389..0000000 --- a/game/txt/evt/pennmush.evt +++ /dev/null @@ -1,16 +0,0 @@ -& help - -=========================================================================== - CobraMUSH Events -=========================================================================== - - -No topics written yet. - - - - - - -=========================================================================== - diff --git a/options.h.dist b/options.h.dist index 4e01b87..1f7f0e2 100644 --- a/options.h.dist +++ b/options.h.dist @@ -12,7 +12,7 @@ * to make sure that you know the full effects of what you are changing. And * if you encounter any errors or compile time problems with any options * other than the default settings, PLEASE inform - * pennmush-bugs@pennmush.org + * devteam@cobramush.org * immediately, so that they can be fixed. The same goes for any other bug * you might find in using this software. All efforts will be made to fix * errors encountered, but unless given a FULL description of the error,