PennMUSH Community

Changeset 1027

Show
Ignore:
Timestamp:
07/08/07 19:58:25 (1 year ago)
Author:
shawnw
Message:

1.8.2p6

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved

  • 1.8.2/trunk/CHANGES.182

    r925 r1027  
    55chronological order (most recent first) 
    66 
    7 [TAP] is T. Alexander Popiel, a PennMUSH developer (aka Talek) 
    87[SW] is Shawn Wagner, a PennMUSH developer (aka Raevnos) 
    98[EEH] is Ervin Hearn III, a PennMUSH developer (aka Noltar) 
    …… 
    1514========================================================================== 
    1615 
     16Version 1.8.2 patchlevel 6                       July 9, 2007 
     17 
     18Development team changes: 
     19  * After many years of valuable work, Talek has retired from 
     20    development.   
     21 
     22Minor changes: 
     23  * Removed the gmalloc malloc option. [SW] 
     24  * KEEPALIVE flag makes the server send a telnet NOP after 
     25    a short period of inactivity; helps prevent timeouts from 
     26    NAT/router devices with a short timeout. [MUX] 
     27 
     28Fixes: 
     29  * Fixed assorted small memory leaks. [SW] 
     30  * Fixed handling of telnet NOPs sent by clients. [SW] 
     31  * The OpenSSL random number pool wasn't getting adequately 
     32    initialized on systems without /dev/urandom [SW] 
     33  * Infinite loop in math code. Reported by Ashen-Sugar. [GM] 
     34  * mkvershlp.pl skips over emacs backup files. 
     35 
    1736Version 1.8.2 patchlevel 5                      June 13, 2007 
    1837 
    1938Minor changes: 
    20   * Removed the gmalloc malloc option. [SW] 
    2139  * Assorted gcc warning fixes. [SW] 
    2240 
    2341Fixes: 
    2442  * Cleaned up some unsafe signal handler functions. [SW] 
     43 
     44Help files: 
     45  * Mention examine lock in help lattr(). Talvo. 
    2546 
    2647Version 1.8.2 patchlevel 4                      May 16, 2007 

  • 1.8.2/trunk/CHANGES.OLD

    r557 r1027  
    44 
    55[TN] is Thorvald Natvig, a PennMUSH developer (aka Trivian) 
    6 [TAP] is T. Alexander Popiel, a PennMUSH developer (aka Talek) 
     6[TAP] is T. Alexander Popiel, a former PennMUSH developer (aka Talek) 
    77[SW] is Shawn Wagner, a PennMUSH developer (aka Raevnos) 
    8 [LdW] is Luuk de Waard, a PennMUSH developer (aka Halatir) 
     8[LdW] is Luuk de Waard, a former PennMUSH developer (aka Halatir) 
    99[RLM] is Ralph Melton, a former PennMUSH developer 
    10 [NJG] is Nick Gammon, the Win32 porter 
    11 [DW] is Dan Williams, the MacOS porter 
     10[NJG] is Nick Gammon, the former Win32 porter 
     11[DW] is Dan Williams, the former MacOS porter 
    1212[2.2] refers to code which originated with the TinyMUSH 2.2 developers 
    1313[3] refers to code by (or inspired by) TinyMUSH 3.0 

  • 1.8.2/trunk/INSTALL

    r523 r1027  
    88 
    99If you are upgrading from a previous PennMUSH release, this is 
    10 probably not the file you want to start with. Read the UPGRADING 
    11 file first. 
     10probably not the file you want to start with. Read the UPGRADING file 
     11first. 
    1212 
    13 DISCLAIMER: Before attempting to run a MUD of any sort, you should have 
    14 some reasonable knowledge of UNIX and C.  If you do not, it is _strongly_ 
    15 suggested that you learn UNIX and C to some reasonable level of competency 
    16 before attempting to set up a MUSH.  (Note that even people using the 
    17 Windows ports are encouraged to know UNIX, because that's the paradigm 
    18 that PennMUSH was built with, and most resources will be written with 
    19 UNIX is mind.) 
     13DISCLAIMER: Before attempting to run a MUD of any sort, you should 
     14have some reasonable knowledge of UNIX and C.  If you do not, it is 
     15_strongly_ suggested that you learn UNIX and C to some reasonable 
     16level of competency before attempting to set up a MUSH.  (Note that 
     17even people using the Windows ports are encouraged to know UNIX, 
     18because that's the paradigm that PennMUSH was built with, and most 
     19resources will be written with UNIX is mind.) 
    2020 
    21 You may also want to take a look at Javelin's Guide for PennMUSH Gods, 
    22 at http://pennmush.org/~alansz/guide.html 
    23 or by ftp from pennmush.org, /pub/PennMUSH/Guide 
     21You may also want to take a look at the Managing PennMUSH book at 
     22http://community.pennmush.org and at Javelin's Guide for PennMUSH 
     23Gods, at http://javelin.pennmush.org/~alansz/guide.html or by ftp from 
     24pennmush.org, /pub/PennMUSH/Guide 
    2425============================================================================ 
    2526  
    …… 
    2829Here's a quick picture of the organization of the MUSH directory tree. 
    2930The "src" directory contains C source code.  The "hdrs" directory 
    30 contains header files for the source code.  The files used by a running 
    31 MUSH are in the "game" directory, which includes subdirectories "data" 
    32 (current databases), "txt" (text files and directories for building them), 
    33 "log" (log files), and "save" (backup databases).  Finally, the "hints" 
    34 directory is used during the installation process, the "po" directory 
    35 holds translation message files, and the "os2" directory contains files 
    36 of using in building for OS/2. 
     31contains header files for the source code.  The files used by a 
     32running MUSH are in the "game" directory, which includes 
     33subdirectories "data" (current databases), "txt" (text files and 
     34directories for building them), "log" (log files), and "save" (backup 
     35databases).  Finally, the "hints" directory is used during the 
     36installation process, the "po" directory holds translation message 
     37files, and the "os2" directory contains files of using in building for 
     38OS/2. 
    3739 
    3840 pennmush--+-> src 
    …… 
    7274    OS/2 
    7375 
    74 There's no real reason why PennMUSH shouldn't compile on any 32-bit 
    75 or better BSD, System V, or POSIX operating system.  Javelin does his 
     76There's no real reason why PennMUSH shouldn't compile on any 32-bit or 
     77better BSD, System V, or POSIX operating system.  Javelin does his 
    7678development on a Linux PC these days. 
    7779 
    7880If you have serious problems, contact Javelin and he will try to help 
    79 you. Email is the best way to get a fast response; in an emergency, you 
    80 can bother him on a MUD, but for code problems, email will probably get 
    81 you a better response. 
     81you. Email is the best way to get a fast response; in an emergency, 
     82you can bother him on a MUD, but for code problems, email will 
     83probably get you a better response. 
    8284 
    8385============================================================================ 
    …… 
    8789     The quickstart version of the installation is: 
    8890 
    89 1. On win32 only, install proper tools or read win32/README*. 
    90 2. sh Configure -d or some variant 
     911a. On win32 only, install proper tools or read win32/README*. 
     921b. On Unix systems, you need: A C compiler, perl, the minimum development 
     93    packages required to compile programs (Linux distributions that don't 
     94    come with gcc in the base install often need a package named glibc-dev) 
     952. Run sh Configure -d or some variant 
    91963. create options.h, or make update 
    92974. make install 
    …… 
    124129 
    1251305. If you plan to run multiple MUSHes, you may want to do a "make 
    126 customize" which will run a script to help set up a separate customized 
    127 game subdirectory for each MUSH (run it once per MUSH you plan to run). 
    128 Files in these subdirectories will already be customized in many ways, 
    129 so what follows may be slightly different. :) This is probably broken. 
     131customize" which will run a script to help set up a separate 
     132customized game subdirectory for each MUSH (run it once per MUSH you 
     133plan to run).  Files in these subdirectories will already be 
     134customized in many ways, so what follows may be slightly different. :) 
     135This is probably broken. 
    130136 
    1311376. Read game/README and follow those instructions.  
    132138 
    133139A final thing you may want to think about is compiling announce.c or 
    134 portmsg.c. These are port announcers; if your MUSH ever goes down, you can 
    135 set one up, and a message will be given to a person attempting to connect 
    136 to that port.  Read that file for details. It is not an official MUSH 
    137 piece of code; rather, it is a freely distributable program available 
    138 via anonymous FTP that is included in this code because it happens to 
    139 be fairly useful.  Javelin suggests using portmsg - it appears to be 
    140 more stable. 
     140portmsg.c. These are port announcers; if your MUSH ever goes down, you 
     141can set one up, and a message will be given to a person attempting to 
     142connect to that port.  Read that file for details. It is not an 
     143official MUSH piece of code; rather, it is a freely distributable 
     144program available via anonymous FTP that is included in this code 
     145because it happens to be fairly useful.  Javelin suggests using 
     146portmsg - it appears to be more stable. 
    141147 
    142148============================================================================ 
    …… 
    150156Configure) from the pennmush directory.  It does include the options.h 
    151157that it was built with, as an aid to those who decide later that they 
    152 want to customize the server; they are useful as a baseline to work from. 
     158want to customize the server; they are useful as a baseline to work 
     159from. 
    153160 
    154161Using the pre-built binary is fairly simple; adjust your configuration 
    …… 
    156163PennMUSH.exe (you may need to use PennMUSH /run or PennMUSH /start). 
    157164Alternately, if you want the MUSH to automatically start each time you 
    158 turn on your machine, you can install it as a system service by running 
    159 'PennMUSH /install'.  PennMUSH can be removed from service status via 
    160 'PennMUSH /remove'. 
     165turn on your machine, you can install it as a system service by 
     166running 'PennMUSH /install'.  PennMUSH can be removed from service 
     167status via 'PennMUSH /remove'. 
    161168 

  • 1.8.2/trunk/MANIFEST

    r559 r1027  
    178178src/funufun.c 
    179179src/game.c 
    180 src/gmalloc.c 
    181180src/help.c 
    182181src/htab.c 

  • 1.8.2/trunk/Patchlevel

    r925 r1027  
    11Do not edit this file. It is maintained by the official PennMUSH patches. 
    2 This is PennMUSH 1.8.2p5 
     2This is PennMUSH 1.8.2p6 

  • 1.8.2/trunk/UPGRADING

    r511 r1027  
    3131A.1. Upgrading with patch files 
    3232 
    33 This is the easiest way to upgrade your source code if you're  
    34 keeping up with patches as they come out, or if you're upgrading 
    35 patchlevels within a release (e.g., within 1.8.0). 
     33This is the easiest way to upgrade your source code if you're keeping 
     34up with patches as they come out, or if you're upgrading patchlevels 
     35within a release (e.g., within 1.8.0). 
    3636 
    3737To upgrade with patch files, get all the patch files for higher 
    …… 
    4242named things like 1.8.0-patch02 (the patch from 1.8.0p1 to 1.8.0p2) 
    4343or, in some cases, 1.7.6p16-1.8.0p0.patch (the patch from 1.7.6p16 to 
    44 1.8.0p0).  
     441.8.0p0). 
    4545 
    4646Each patch file contains instructions at the top explaining how to 
    4747apply it. FOLLOW THESE! Don't assume they're all the same. 
    4848 
    49 After you've applied all the patches and followed all the instructions, 
    50 you should be good to go. In most cases, you can simply @shutdown/reboot 
    51 after the final successful compile. If @shutdown/reboot crashes, 
    52 you'll have to restart again. 
     49After you've applied all the patches and followed all the 
     50instructions, you should be good to go. In most cases, you can simply 
     51@shutdown/reboot after the final successful compile. If 
     52@shutdown/reboot crashes, you'll have to restart again. 
    5353 
    5454A.2. Building a new distribution 
    5555 
    56 When you're upgrading across release and no patchlevel is provided 
    57 to make the upgrade (e.g. from 1.7.4p3 to 1.8.0p0), it's often 
    58 easier to simply build a new distribution following the INSTALL 
    59 instructions, but with your old configuration stuff. 
     56When you're upgrading across release and no patchlevel is provided to 
     57make the upgrade (e.g. from 1.7.4p3 to 1.8.0p0), it's often easier to 
     58simply build a new distribution following the INSTALL instructions, 
     59but with your old configuration stuff. 
    6060 
    6161Move your older version of PennMUSH in a directory called oldpenn/, 
    62 unpack the new one (it will unpack into pennmush/).  
    63  
    64 All of the steps below should be taken before running Configure for the 
    65 new version: 
     62unpack the new one (it will unpack into pennmush/). 
     63 
     64All of the steps below should be taken before running Configure for 
     65the new version: 
    6666 
    6767A.2.a. options.h and game/*.cnf 
    6868 
    69 You can copy the options.h file and game/mush.cnf file from your 
    70 old version to the new version. The 'make update' command (run after 
     69You can copy the options.h file and game/mush.cnf file from your old 
     70version to the new version. The 'make update' command (run after 
    7171Configure) will compare your files with the newly distributed ones and 
    72 tell you about options that have been added or removed. If you have any 
    73 options defined that the new version doesn't recognize, you'll be asked 
    74 if you want to retain them (which is safe). 
     72tell you about options that have been added or removed. If you have 
     73any options defined that the new version doesn't recognize, you'll be 
     74asked if you want to retain them (which is safe). 
    7575 
    7676If your mush.cnf file is called something else, copy it to mush.cnf in 
    77 pennmush/game anyway, since that's the file that gets updated. Then make 
    78 a link to that file called whatever.cnf if you want to use that. 
    79  
    80 If you've modified the restart script, you'll have to decide if 
    81 your modified script is still appropriate, or modify the distributed 
    82 game/restart script again as you like it. The latter is encouraged. 
     77pennmush/game anyway, since that's the file that gets updated. Then 
     78make a link to that file called whatever.cnf if you want to use that. 
     79 
     80If you've modified the restart script, you'll have to decide if your 
     81modified script is still appropriate, or modify a copy of the 
     82distributed game/restart script as you like it. it is highly 
     83recommended that you copy restart to a second file, called something 
     84like restart.local, and modify and use it instead of the stock restart 
     85script to reduce conflicts when patching. 
    8386 
    8487You can also copy your old game/access.cnf, game/sitelock.cnf, and 
    85 game/txt/*.txt files into the appropriate locations. You may wish 
    86 to do the same thing for game/restrict.cnf, but you should compare 
    87 it to the new version, as restrictions that may formerly have been 
    88 compiled into the server may now be specified in restrict.cnf instead. 
     88game/txt/*.txt files into the appropriate locations. You may wish to 
     89do the same thing for game/restrict.cnf, but you should compare it to 
     90the new version, as restrictions that may formerly have been compiled 
     91into the server may now be specified in restrict.cnf instead. 
    8992 
    9093A.2.b. src/*local.c 
    9194 
    9295You should copy local.c, cmdlocal.c, and funlocal.c from oldpenn/src 
    93 to pennmush/src if you want to retain this local code. Of course, 
    94 it may not still work, but it's quite likely that it will. If you 
    95 don't have any such code, you can skip this step. 
     96to pennmush/src if you want to retain this local code. Of course, it 
     97may not still work, but it's quite likely that it will. If you don't 
     98have any such code, you can skip this step. 
    9699 
    97100A.2.c. Databases 
    …… 
    99102This MUSH version should read databases along the main branch of MUSH 
    100103evolution -- TinyMUD, vanilla TinyMUSH up to 2.0, MicroMUSH, and all 
    101 Pern/PennMUSH versions. If you need to convert a TinyMUSH 2.0 database, 
    102 please contact Amberyl, and she'll mail you an extension to 2.0 that 
    103 will dump a 1.50-readable flatfile. You're probably out of luck with 
    104 databases for TinyMUSH 2.2 and later. 
     104Pern/PennMUSH versions. If you need to convert a TinyMUSH 2.0 
     105database, please contact Amberyl, and she'll mail you an extension to 
     1062.0 that will dump a 1.50-readable flatfile. You're probably out of 
     107luck with databases for TinyMUSH 2.2 and later. 
    105108 
    106109Be sure that your options.h settings correctly reflect the type 
    …… 
    127130system to one that uses the new flag system (post-1.7.7p5), if you've 
    128131added flags or toggles.  You probably had an #define in hdrs/flags.h 
    129 for your flag's bit value.  This now should be moved to hdrs/oldflags.h; 
    130 you should leave in the table entry in src/flags.c. If you set up a macro 
    131 for testing your flag in hdrs/mushdb.h, you'll need to change it to use 
    132 the has_flag_by_name() function - see the many examples in that file. 
     132for your flag's bit value.  This now should be moved to 
     133hdrs/oldflags.h; you should leave in the table entry in 
     134src/flags.c. If you set up a macro for testing your flag in 
     135hdrs/mushdb.h, you'll need to change it to use the has_flag_by_name() 
     136function - see the many examples in that file. 
    133137 
    134138If this isn't suitable (you're crossing releases or your hacks are too 
    …… 
    139143C. PennMUSH with a lot of hacks 
    140144 
    141 If you've seriously hacked your server source code, you're on your 
    142 own in terms of keeping up with new patchlevels. Some people apply 
     145If you've seriously hacked your server source code, you're on your own 
     146in terms of keeping up with new patchlevels. Some people apply 
    143147patchfiles and fix the rejected hunks. 
    144148 
    …… 
    147151version of pennmush (e.g. 1.7.4p16) to your hacked version of pennmush 
    148152(e.g. 1.7.4p16 with hacks), and then applying those patches to the new 
    149 version of PennMUSH (e.g. 1.8.0p0) to create a hacked version thereof. If 
    150 some patch hunks fail, you'll have to apply them manually. 
     153version of PennMUSH (e.g. 1.8.0p0) to create a hacked version 
     154thereof. If some patch hunks fail, you'll have to apply them manually. 
    151155 
    152156Probably the best approach is to keep all multiple versions of the 

  • 1.8.2/trunk/game/mushcnf.dst

    r527 r1027  
    214214# the internet, and don't deal well with persistant connections like 
    215215# mushes use. This option will make the server automatically send a 
    216 # 'Are you still there?' query every few minutes to keep the 
     216# TCP-level 'Are you still there?' query every few minutes to keep the 
    217217# connection active. 
    218 # NOTE: This doesn't work on all OSes, but does on the most popular 
    219 # ones for mush hosting such as linux. 
     218# NOTE: This doesn't work on all OSes, but does some of the most popular 
     219# ones for mush hosting such as linux. Other options include the KEEPALIVE 
     220# flag and the IDLE command. 
    220221keepalive_timeout 5m 
    221222 

  • 1.8.2/trunk/game/txt/hlp/penncmd.hlp

    r853 r1027  
    15671567 For example: 
    15681568  @function/delete ansi 
    1569   &ansi_fun #1234=%0 
     1569  &ansi_fun #1234=%1 
    15701570  @function ansi=#1234, ansi_fun, 2, 2, noguest 
    15711571 

  • 1.8.2/trunk/game/txt/hlp/penncode.hlp

    r525 r1027  
    33PennMUSH is developed by a team of developers whose names are 
    44listed in 'help changes'.  Suggestions, comments, and bug reports are 
    5 welcome: 
    6  
    7 Report bugs at:               pennmush-bugs@pennmush.org 
    8 Comments/suggestions to:      pennmush-developers@pennmush.org 
     5welcome. 
     6 
     7The main PennMUSH web page is at http://www.pennmush.org 
     8 
     9Report bugs and make suggestions at:  http://dev.pennmush.org 
     10 
     11The PennMUSH community page is at http://community.pennmush.org 
    912 
    1013For information about downloading PennMUSH, see 'help download'. 
    1114For information about changes in versions of the code, see 'help changes'. 
    12  
    1315& download 
    1416The latest version of this MUSH code is available at 
    …… 
    2325least version 2.007.  Also on that site is Javelin's Guide for PennMUSH 
    2426Gods, in /pub/PennMUSH/Guide. A better way to read it is on the Web at 
    25 http://www.pennmush.org/~alansz/guide.html 
     27http://javelin.pennmush.org/~alansz/guide.html 
    2628 
    2729& i18n 
    …… 
    4648variable in the PennMUSH restart script. 
    4749 
     50Unicode is not currently supported. 
     51 
    4852& copyright 
    4953& copyrite 

  • 1.8.2/trunk/game/txt/hlp/pennflag.hlp

    r853 r1027  
    5151  d - Destroy_Ok        e - Enter_Ok            g - Gagged 
    5252  h - Halt              i - Orphan              j - Jury_Ok              
    53   l - Light             m - Myopic, Mistrust    n - No_Command           
    54   o - On-Vacation       p - Puppet, Paranoid    r - Royalty              
    55   s - Suspect           t - Transparent         u - Uninspected          
    56   v - Verbose           w - No_Warn             x - Terse, Cloudy        
    57   ? - Unregistered      ^ - Listen_Parent       ~ - Noaccents 
    58   " - NoSpoof 
     53  k - Keepalive         l - Light               m - Myopic, Mistrust 
     54  n - No_Command        o - On-Vacation         p - Puppet, Paranoid 
     55  r - Royalty           s - Suspect             t - Transparent 
     56  u - Uninspected       v - Verbose             w - No_Warn 
     57  x - Terse, Cloudy     ? - Unregistered        ^ - Listen_Parent 
     58  ~ - Noaccents         " - NoSpoof 
    5959----------------------------------------------------------------------- 
    6060Some flags may not be enabled on some MUSHes. @flag/list will show 
    6161which are available. 
    62  
    6362& ABODE 
    6463 Flag:  ABODE  (rooms) 
    …… 
    402401  When a room is set JUMP_OK, then that room can be teleported into 
    403402  by anyone. See @teleport. 
     403& KEEPALIVE 
     404  Flag: KEEPALIVE (players) 
     405 
     406  When this flag is set on a player with a telnet-capable connection, 
     407  a telnet NOP (no-operation) is sent after there's been no activity 
     408  on the connection for a minute, to generate socket activity without 
     409  generating any output. In a way, it's the opposite of the IDLE 
     410  command. IDLE is sent by clients to keep a connection open, while 
     411  KEEPALIVE tells the server to send a message. Both are intended for 
     412  use by people going through home router/NAT appliances with short 
     413  inactivity timeouts. 
     414 
     415See also: IDLE, terminfo() 
    404416& LIGHT 
    405417  Flag:  LIGHT (all types) 

  • 1.8.2/trunk/game/txt/hlp/penntop.hlp

    r651 r1027  
    383383See also: BOOLEAN FUNCTIONS, not(), t() 
    384384& CLIENTS 
     385& CLIENTS 
    385386  Clients are special software programs that you can use to connect to  
    386387  MUSHes. They are usually much nicer to use than raw telnet and give you 
    …… 
    388389  more), backscroll, history of previous commands, macros, and so on.  
    389390 
    390   Here is a list of common clients and the anonymous ftp sites at which 
    391   you can get them. To find out how to anonymous ftp, ask your system  
    392   administrator. Please note that the below sites are subject to change. 
    393   The below are listed solely for your information and possible benefit.  
    394   The developers of PennMUSH have nothing to do with the clients.  
    395  
    396   OPERATING                   FTP or WWW SITE/ 
    397   SYSTEM          CLIENT      DIRECTORY 
     391  Here is a list of common clients and the web sites where they can be 
     392  found.  Please note that the below sites are subject to change.  The 
     393  below are listed solely for your information and possible benefit. 
     394  The developers of PennMUSH have nothing to do with the clients. 
     395 
     396  OPERATING 
     397  SYSTEM          CLIENT      WEB SITE 
    398398  ----------------------------------------------------------------------- 
    399   UNIX            Tinyfugue   tf.tcp.com 
    400                               /pub/tinyfugue 
    401   WINDOWS 32-bit  MUSHClient  http://www.mushclient.com 
     399  UNIX            Tinyfugue   http://tinyfuge.sourceforge.net 
     400  WINDOWS         MUSHClient  http://www.mushclient.com 
    402401                  SimpleMU    http://simplemu.onlineroleplay.com 
    403402                  MuckClient  http://www.xcalibur.co.uk/MuckClient/ 
    404   MACINTOSH       MUDDweller  http://www.shareware.com (search for Muddweller) 
    405  
     403  MAC OS X        Savitar     http://www.heynow.com/Savitar/ 
     404                  Atlantis    http://www.riverdark.net/atlantis/ 
     405                  Unix clients will also run on OS X. 
    406406& CONTROL 
    407407  Controlling an object basically means that you have the power to change 
    …… 
    447447& CREDITS 
    448448  Maintainer: Raevnos [SW] 
    449   Developers: Javelin, Talek [TAP], Ervin Hearn III [EEH],  
    450               Greg Millam [GM] 
     449  Developers: Javelin, Ervin Hearn III [EEH], Greg Millam [GM] 
    451450  Past Porters: Nick Gammon [NJG] (win32), Dan Williams [DW] (MacOS),  
    452451           Sylvia (OS/2) 
    453   Former developers: Rhyanna [RLM], Trivian [TN], Halatir [LdW] 
    454   
    455   The original TinyMUSH 1.0 code was written by Lawrence Foard, and was 
    456   based upon James Aspnes' TinyMUD server. Since then, the code has been 
    457   modified by the programmers of MicroMUSE (then MicroMUSH), and Joseph 
    458   Traub (Moonchilde of PernMUSH).  From January 1992 to January 1995, 
    459   Lydia Leong (Amberyl of PernMUSH / Polgara of Belgariad) maintained 
    460   the code currently known as PennMUSH 1.50.  From January 1995 until  
    461   July 2006, Alan Schwartz (Paul of DuneMUSH / Javelin elsewhere) maintained 
    462   this code, along with a development team. From July 2006 on, Raevnos has 
    463   been the maintainer. 
    464  
    465   Big thanks to the developers of TinyMUSH 2.0, 2.2 [2.2], 3.0 [3], Mux2, 
    466   and Rhost [Rhost] servers, as well as to the players of Belgariad MUSH, 
    467   DuneMUSH, and M*U*S*H, and everyone else using this server! 
     452  Former developers: Rhyanna [RLM], Trivian [TN], Halatir [LdW], Talek [TAP] 
     453  
     454  The original TinyMUSH 1.0 code was written by Lawrence Foard, and 
     455  was based upon James Aspnes' TinyMUD server. Since then, the code 
     456  has been modified by the programmers of MicroMUSE (then MicroMUSH), 
     457  and Joseph Traub (Moonchilde of PernMUSH).  From January 1992 to 
     458  January 1995, Lydia Leong (Amberyl of PernMUSH / Polgara of 
     459  Belgariad) maintained the code currently known as PennMUSH 1.50. 
     460  From January 1995 until July 2006, Alan Schwartz (Paul of DuneMUSH / 
     461  Javelin elsewhere) maintained this code, along with a development 
     462  team. From July 2006 on, Raevnos has been the maintainer. 
     463 
     464  Big thanks to the developers of TinyMUSH 2.0, 2.2 [2.2], 3.0 [3], 
     465  MUX2, and Rhost [Rhost] servers, as well as to the players of 
     466  Belgariad MUSH, DuneMUSH, and M*U*S*H, and everyone else using this 
     467  server! 
    468468 
    469469See also: help code, help license 

  • 1.8.2/trunk/game/txt/hlp/pennv182.hlp

    r925 r1027  
    1 & 1.8.2p5 
     1& 1.8.2p6 
    22& changes 
    33This is a list of changes in this patchlevel which are probably of 
    …… 
    1212be read in 'help patchlevels'. 
    1313 
     14Version 1.8.2 patchlevel 6                       July 9, 2007 
     15 
     16Development team changes: 
     17  * After many years of valuable work, Talek has retired from 
     18    development.   
     19 
     20Minor changes: 
     21  * Removed the gmalloc malloc option. [SW] 
     22  * KEEPALIVE flag makes the server send a telnet NOP after 
     23    a short period of inactivity; helps prevent timeouts from 
     24    NAT/router devices with a short timeout. [MUX] 
     25 
     26Fixes: 
     27  * Fixed assorted small memory leaks. [SW] 
     28  * Fixed handling of telnet NOPs sent by clients. [SW] 
     29  * The OpenSSL random number pool wasn't getting adequately 
     30    initialized on systems without /dev/urandom [SW] 
     31  * Infinite loop in math code. Reported by Ashen-Sugar. [GM] 
     32  * mkvershlp.pl skips over emacs backup files. 
     33 
     34& 1.8.2p5 
    1435Version 1.8.2 patchlevel 5                      June 13, 2007 
    1536 
    1637Minor changes: 
    17   * Removed the gmalloc malloc option. [SW] 
    1838  * Assorted gcc warning fixes. [SW] 
    1939 
    2040Fixes: 
    2141  * Cleaned up some unsafe signal handler functions. [SW] 
     42 
     43Help files: 
     44  * Mention examine lock in help lattr(). Talvo. 
    2245 
    2346& 1.8.2p4 

  • 1.8.2/trunk/game/txt/hlp/pennvOLD.hlp

    r925 r1027  
    44184418type 'help <version>p<patchlevel>'. For example, 'help 1.7.2p3' 
    44194419 
    4420 1.8.2: 0, 1, 2, 3, 4, 5 
     44201.8.2: 0, 1, 2, 3, 4, 5, 6 
    442144211.8.1: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 
    442244221.8.0: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13 

  • 1.8.2/trunk/hdrs/access.h

    r521 r1027  
    77 */ 
    88struct access { 
    9   char host[BUFFER_LEN];   /**< The host pattern */ 
    10   char comment[BUFFER_LEN];    /**< A comment about the rule */ 
    11   dbref who;           /**< Who created this rule if sitelock used */ 
    12   int can;         /**< Bitflags of what the host can do */ 
    13   int cant;            /**< Bitflags of what the host can't do */ 
    14   struct access *next;     /**< Pointer to next rule in the list */ 
     9  char host[BUFFER_LEN];        /**< The host pattern */ 
     10  char comment[BUFFER_LEN];     /**< A comment about the rule */ 
     11  dbref who;                    /**< Who created this rule if sitelock used */ 
     12  int can;                      /**< Bitflags of what the host can do */ 
     13  int cant;                     /**< Bitflags of what the host can't do */ 
     14  struct access *next;          /**< Pointer to next rule in the list */ 
    1515}; 
    1616 
    1717 
    1818/* These flags are can/can't - a site may or may not be allowed to do them */ 
    19 #define ACS_CONNECT     0x1    /* Connect to non-guests */ 
    20 #define ACS_CREATE      0x2    /* Create new players */ 
    21 #define ACS_GUEST       0x4    /* Connect to guests */ 
    22 #define ACS_REGISTER    0x8    /* Site can use the 'register' command */ 
     19#define ACS_CONNECT     0x1     /* Connect to non-guests */ 
     20#define ACS_CREATE      0x2     /* Create new players */ 
     21#define ACS_GUEST       0x4     /* Connect to guests */ 
     22#define ACS_REGISTER    0x8     /* Site can use the 'register' command */ 
    2323/* These flags are set in the 'can' bit, but they mark special processing */ 
    24 #define ACS_SITELOCK    0x10   /* Marker for where to insert @sitelock */ 
    25 #define ACS_SUSPECT     0x20   /* All players from this site get SUSPECT */ 
    26 #define ACS_DENY_SILENT 0x40   /* Don't log failed attempts */ 
    27 #define ACS_REGEXP      0x80   /* Treat the host pattern as a regexp */ 
     24#define ACS_SITELOCK    0x10    /* Marker for where to insert @sitelock */ 
     25#define ACS_SUSPECT     0x20    /* All players from this site get SUSPECT */ 
     26#define ACS_DENY_SILENT 0x40    /* Don't log failed attempts */ 
     27#define ACS_REGEXP      0x80    /* Treat the host pattern as a regexp */ 
    2828 
    29 #define ACS_GOD         0x100  /* God can connect from this site */ 
    30 #define ACS_WIZARD      0x200  /* Wizards can connect from this site */ 
    31 #define ACS_ADMIN       0x400  /* Admins can connect from this site */ 
     29#define ACS_GOD         0x100   /* God can connect from this site */ 
     30#define ACS_WIZARD      0x200   /* Wizards can connect from this site */ 
     31#define ACS_ADMIN       0x400   /* Admins can connect from this site */ 
    3232 
    3333/* This is the usual default access */ 
    …… 
    5050struct access *site_check_access(const char *hname, dbref who, int *rulenum); 
    5151int format_access(struct access *ap, int rulenum, 
    52          dbref who 
    53          __attribute__ ((__unused__)), char *buff, char **bp); 
     52                  dbref who 
     53                  __attribute__ ((__unused__)), char *buff, char **bp); 
    5454int add_access_sitelock(dbref player, const char *host, dbref who, int can, 
    55            int cant); 
     55                        int cant); 
    5656int remove_access_sitelock(const char *pattern); 
    5757void do_list_access(dbref player); 
    …… 
    5959  (const char *opts, dbref *who, int *can, int *cant, dbref player); 
    6060 
    61 #endif             /* __ACCESS_H */ 
     61#endif                  &nb