data/help/sourcemud.help doc/zmp-x-sourcemud.txt scripts/sourcemud.sx @@ -1,6 +1,6 @@ Active Developers ----------------- - Sean Middleditch <elanthis@awemud.net> + Sean Middleditch <elanthis@sourcemud.org> Inactive Developers ------------------- AUTHORS @@ -1,6 +1,6 @@ -AweMUD :: Modern MUD server software -Copyright (c) 2000-2006 AwesomePlay Productions, Inc. and -contributors. All rights reserved. +Source MUD:: Modern MUD server software +Copyright (c) 2000-2006, 2008 Sean Middleditch and contributors. +All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: COPYING @@ -1,5 +1,5 @@ account.name = "Administrator" -account.email = "awemud@localhost" +account.email = "sourcemud@localhost" account.passphrase = "$1$tNUNjzkD$F.tONxYNdR8hpYwuekqr7/" account.character = "Admin" account.created = "2000-01-01 00:00:00" data/admin.acct @@ -1,6 +1,6 @@ -# AweMUD Next Generation - Default NPC blueprints +# Source MUD - Default NPC blueprints # Copyright (C) 2003-2005 AwesomePlay Productions Inc. -# Sean Middleditch <elanthis@awemud.net> +# Sean Middleditch <elanthis@sourcemud.org> blueprint.npc { blueprint.id = "wolf" data/blueprints/animals.npcs @@ -1,6 +1,6 @@ -# AweMUD Next Generation - Armor object blueprints +# Source MUD - Armor object blueprints # Copyright (C) 2003-2005 AwesomePlay Productions Inc. -# Sean Middleditch <elanthis@awemud.net> +# Sean Middleditch <elanthis@sourcemud.org> # Additions by Gary Mix copyright 2004 # See COPYING for details data/blueprints/armor.objs @@ -1,6 +1,6 @@ -# AweMUD Next Generation - gem object blueprints +# Source MUD - gem object blueprints # Copyright (C) 2003-2005 AwesomePlay Productions Inc. -# Sean Middleditch <elanthis@awemud.net> +# Sean Middleditch <elanthis@sourcemud.org> blueprint.object { blueprint.id = "gem_ruby" data/blueprints/gems.objs @@ -1,6 +1,6 @@ -# AweMUD Next Generation - Misc object blueprints +# Source MUD - Misc object blueprints # Copyright (C) 2003-2005 AwesomePlay Productions Inc. -# Sean Middleditch <elanthis@awemud.net> +# Sean Middleditch <elanthis@sourcemud.org> blueprint.object { blueprint.id = "co_leather_backpack" data/blueprints/misc.objs @@ -1,6 +1,6 @@ -# AweMUD Next Generation - Default NPC blueprints +# Source MUD - Default NPC blueprints # Copyright (C) 2003-2005 AwesomePlay Productions Inc. -# Sean Middleditch <elanthis@awemud.net> +# Sean Middleditch <elanthis@sourcemud.org> # --- BASE --- blueprint.npc { data/blueprints/undead.npcs @@ -1,6 +1,6 @@ -# AweMUD Next Generation - weapon object blueprints +# Source MUD - weapon object blueprints # Copyright (C) 2003-2005 AwesomePlay Productions Inc. -# Sean Middleditch <elanthis@awemud.net> +# Sean Middleditch <elanthis@sourcemud.org> blueprint.object { blueprint.id = "ma_iron" data/blueprints/weapons.objs @@ -1,6 +1,6 @@ -# AweMUD Next Generation - Default calendar definition +# Source MUD - Default calendar definition # Copyright (C) 2003-2005 AwesomePlay Productions Inc. -# Sean Middleditch <elanthis@awemud.net> +# Sean Middleditch <elanthis@sourcemud.org> # Various day/night texts daytime day "The Sun is casting its light about the world." data/calendar @@ -1,6 +1,6 @@ -# AweMUD Next Generation - Command help data +# Source MUD - Command help data # Copyright (C) 2003-2005 AwesomePlay Productions Inc. -# Sean Middleditch <elanthis@awemud.net> +# Sean Middleditch <elanthis@sourcemud.org> %begin quit Returns you to the main menu. @@ -79,7 +79,7 @@ %end %begin server - Give general information about the AweMUD server. + Give general information about the Source MUD server. %end %begin open data/help/commands.help @@ -1,3 +1,3 @@ -awemud.help +sourcemud.help commands.help olc.help data/help/manifest.txt @@ -1,11 +1,11 @@ -# AweMUD Next Generation - Help data +# Source MUD - Help data # Copyright (C) 2003-2005 AwesomePlay Productions Inc. -# Sean Middleditch <elanthis@awemud.net> +# Sean Middleditch <elanthis@sourcemud.org> %begin building - AweMUD currently has very limited building support. Much of the information in AweMUD can only be modified by editing the data files. + Source MUD currently has very limited building support. Much of the information in Source MUD can only be modified by editing the data files. - There are no plans to support on-line editing of things such as races, classes, help files, blueprints, or server settings. These will have to be changed by modifying their respective files. Races and classes will not be able to be changed without an AweMUD reboot. The help data is read on the fly, so a change to the help file will take affect immediately. Templates are occasionally re-read as well (there are plans to support a forces flush of in-memory blueprints). + There are no plans to support on-line editing of things such as races, classes, help files, blueprints, or server settings. These will have to be changed by modifying their respective files. Races and classes will not be able to be changed without an Source MUD reboot. The help data is read on the fly, so a change to the help file will take affect immediately. Templates are occasionally re-read as well (there are plans to support a forces flush of in-memory blueprints). The {bold 'create'} command allows you to make a new object or npc from a blueprint, or to create a new room or zone, or to create a new exit. In order to modify an existing entity, you must use the {bold 'modify'} command. In order to view the attributes of an entity, use the {bold 'display'} command. To remove existing entities, use the {bold 'destroy'} command. A special command, {bold 'description'}, is used to edit the long description of an entity. @@ -67,7 +67,7 @@ When you run the command, you are put in a special description input mode. You keep entering the lines of the description, until you have the whole thing entered. You then must put a single @ (at sign) on a line all by itself; this signifies the end of your input. - Remember that AweMUD doesn't allow lines that are very long (usually around 100 to 200 characters), so you must break up your description. AweMUD will automatically reform the lines into a single paragraph with proper spacing. (Two spaces after a ., !, or ?, and one space after anything else.) + Remember that Source MUD doesn't allow lines that are very long (usually around 100 to 200 characters), so you must break up your description. Source MUD will automatically reform the lines into a single paragraph with proper spacing. (Two spaces after a ., !, or ?, and one space after anything else.) %end %begin olc_edit_commands data/help/olc.help @@ -1,5 +1,5 @@ </div> - <div id="footer">AweMUD {version}<br /><a href="http://www.awemud.net">http://www.awemud.net</a></div> + <div id="footer">Source MUD {version}<br /><a href="http://www.sourcemud.org">http://www.sourcemud.org</a></div> </body> </html> data/html/footer.tpl @@ -1,7 +1,7 @@ <?xml version="1.0"?> <html> <head> - <title>AweMUD Portal</title> + <title>Source MUD Portal</title> <style type="text/css"> td \{ text-align: left; @@ -51,7 +51,7 @@ </style> </head> <body> - <div id="title">AweMUD Portal</div> + <div id="title">Source MUD Portal</div> <div id="menu"> {if $account} data/html/header.tpl @@ -1,4 +1,4 @@ -<p>Welcome to the AweMUD portal!</p> +<p>Welcome to the Source MUD portal!</p> {if $account} <p>Welcome, {$account.name}!</p> data/html/index.tpl @@ -1,6 +1,6 @@ -# AweMUD Next Generation - Editable messages +# Source MUD - Editable messages # Copyright (C) 2003-2005 AwesomePlay Productions Inc. -# Sean Middleditch <elanthis@awemud.net> +# Sean Middleditch <elanthis@sourcemud.org> text.connect = %begin data/messages @@ -1,6 +1,6 @@ -# AweMUD Next Generation - Player race definitions +# Source MUD - Player race definitions # Copyright (C) 2003-2005 AwesomePlay Productions Inc." -# Sean Middleditch <elanthis@awemud.net> +# Sean Middleditch <elanthis@sourcemud.org> # Human race races.race { data/races @@ -1,4 +1,4 @@ -#### AweMUD Skill List +#### Source MUD Skill List # Intrinsic skills: # These skills are core attributes of all characters. Intrinsic skills are data/skills @@ -1,6 +1,6 @@ -# AweMUD Next Generation - Social commands list +# Source MUD - Social commands list # Copyright (C) 2003-2005 AwesomePlay Productions Inc. -# Sean Middleditch <elanthis@awemud.net> +# Sean Middleditch <elanthis@sourcemud.org> # FORMAT: # <verb> <adverb> <flags> <self> <room> <target> data/socials @@ -1,6 +1,6 @@ -# AweMUD Next Generation - Default weather definition +# Source MUD - Default weather definition # Copyright (C) 2003-2005 AwesomePlay Productions Inc. -# Sean Middleditch <elanthis@awemud.net> +# Sean Middleditch <elanthis@sourcemud.org> weather.state { state.id = "clear" data/weather @@ -3,12 +3,12 @@ <title>Control Socket Interface</title> <section> <title>Introduction</title> - <para>The new control interface feature of AweMUD allows a program to open a connection to the MUD using a UNIX domain socket, and issuing commands to the running AweMUD server. These commands can be anything imaginable that is added to the code. The basic intent, however, is to offer administration capabilities without needing to connect as a player. The interface can also allow scripts and applications to programmatically control AweMUD. This requires an easily parsable protocol.</para> + <para>The new control interface feature of Source MUD allows a program to open a connection to the MUD using a UNIX domain socket, and issuing commands to the running Source MUD server. These commands can be anything imaginable that is added to the code. The basic intent, however, is to offer administration capabilities without needing to connect as a player. The interface can also allow scripts and applications to programmatically control Source MUD. This requires an easily parsable protocol.</para> <para>The protocl is line based. The protocol is client driven. The server only outputs information in response to a client command, or upon initial connection. Clients send commands to the server as a single line, and the server responds with one or more lines of text.</para> <para>The server may then send one or more lines of response. Responses are either error messages or success messages. Success messages may be preceded by data messages.</para> <para>Upon first connecting, the server will return either a single success message, or an error message. In the case of an error response, the client is immediately disconnected.</para> - <para>The tool awemud-ctrl (src/awemud-ctrl in the build directory) allows communications with the server for utilizing the CIP (Control Interface Protocol). In order to enable the CIP mechanism, the server/control setting in the awemud.conf file must be un-commented-out. If you use a different socket path than the default, you may pass the socket path to the awemud-ctrl utility as a command-line argument.</para> - <para>The socket will by default only be usable by the user who started the AweMUD server. Note that if you configure AweMUD to switch user/group IDs after startup, the CIP socket will *not* use the specified IDs, but the original ID (root being the only option in this case for most OSes).</para> + <para>The tool sourcemud-ctrl (src/sourcemud-ctrl in the build directory) allows communications with the server for utilizing the CIP (Control Interface Protocol). In order to enable the CIP mechanism, the server/control setting in the sourcemud.conf file must be un-commented-out. If you use a different socket path than the default, you may pass the socket path to the sourcemud-ctrl utility as a command-line argument.</para> + <para>The socket will by default only be usable by the user who started the Source MUD server. Note that if you configure Source MUD to switch user/group IDs after startup, the CIP socket will *not* use the specified IDs, but the original ID (root being the only option in this case for most OSes).</para> </section> <section> <title>Commands</title> @@ -27,7 +27,7 @@ command !@#\"\\ arg2</screen> <title>Responses</title> <para>A success or error message comes in the form of a plus (+) followed by an error code. Error codes are single words formed of all uppercase characters. Examples are OK, BADCOMMAND, NOTFOUND and BADPARAM.</para> <para>If the error code is OK, the message is a success message. For any other error code, the message is a failure (error) message.</para> - <para>An optional human-friendly string may followed the error code. The message and the code are separated by a single space. These messages are not intended to be machine parsed, but may be presented to users of utilities or applications that use the protocol. (The messages are also useful to users utilizing the awemud-ctrl utility directly.)</para> + <para>An optional human-friendly string may followed the error code. The message and the code are separated by a single space. These messages are not intended to be machine parsed, but may be presented to users of utilities or applications that use the protocol. (The messages are also useful to users utilizing the sourcemud-ctrl utility directly.)</para> <example> <title>Response codes</title> <screen>+NOACCESS You do not have permission to access this resource. @@ -203,7 +203,7 @@ login admin wrongpass <para>Sets the maximum number of characters an account is allowed to have active at any given time. The first paramater is the account name, and the second parameter is the active character limit. Use a limit of zero - (0) to set the limit to the default, as specified in the awemud.conf + (0) to set the limit to the default, as specified in the sourcemud.conf configuration file. Returns a NOTFOUND error if the account doesn't exist.</para> @@ -219,7 +219,7 @@ login admin wrongpass <para>Sets the maximum number of characters an account is allowed to have. The first paramater is the account name, and the second parameter is the character limit. Use a limit of zero (0) to set the limit to the - default, as specified in the awemud.conf configuration file. Returns a + default, as specified in the sourcemud.conf configuration file. Returns a NOTFOUND error if the account doesn't exist.</para> <example><screen>setmaxchars admin 5 @@ -237,7 +237,7 @@ login admin wrongpass <example><screen>showaccount admin -ID=admin -NAME=Administrator --EMAIL=awemud@localhost +-EMAIL=sourcemud@localhost -MAXCHARS=3 -MAXACTIVE=1 -DISABLED=NO doc/ch-control.xml @@ -1,17 +1,17 @@ <!DOCTYPE chatper PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> <chapter id="ch_installation"> <title>Installation</title> - <para>AweMUD uses the standard GNU method of building and installating applications, <command>./configure && make && make install</command>.</para> - <screen>tar -zxf awemud-0.25.tar.gz -cd awemud-0.25.tar.gz + <para>Source MUD uses the standard GNU method of building and installating applications, <command>./configure && make && make install</command>.</para> + <screen>tar -zxf sourcemud-0.25.tar.gz +cd sourcemud-0.25.tar.gz ./configure && make && make install</screen> <section> <title>Dependencies</title> - <para>AweMUD depends on a single external library, <ulink url="http://www.hpl.hp.com/personal/Hans_Boehm/gc/">Boehm-Demers-Weiser Garbage Collector</ulink>. This library must be installed in order to build AweMUD. The BDW libgc uses the standard build and install commands. However, AweMUD requires that libgc be built with C++, which can be done by passing the --enable-cplusplus switch to the ./configure script.</para> + <para>Source MUD depends on a single external library, <ulink url="http://www.hpl.hp.com/personal/Hans_Boehm/gc/">Boehm-Demers-Weiser Garbage Collector</ulink>. This library must be installed in order to build Source MUD. The BDW libgc uses the standard build and install commands. However, Source MUD requires that libgc be built with C++, which can be done by passing the --enable-cplusplus switch to the ./configure script.</para> <screen>tar -zxf gc6.6.tar.gz cd gc6.6 ./configure --enable-cpluplus && make && make install</screen> - <para>If you plan on hacking on the AweMUD source code, you will also need all of the following utilities. You will not need these utilities if you only want to build and install AweMUD.</para> + <para>If you plan on hacking on the Source MUD source code, you will also need all of the following utilities. You will not need these utilities if you only want to build and install Source MUD.</para> <itemizedlist> <listitem><ulink url="http://www.gnu.org/software/autoconf/">GNU Autoconf 2.53</ulink></listitem> <listitem><ulink url="http://www.gnu.org/software/automake/">GNU Automake 1.8</ulink></listitem> @@ -19,7 +19,7 @@ cd gc6.6 <listitem><ulink url="http://www.gnu.org/software/flex/">GNU Flex</ulink></listitem> <listitem><ulink url="http://www.xmlsoft.org">xsltproc</ulink></listitem> </itemizedlist> - <para>If you want to build the AweMUD Manual (this document), you will also need <ulink url="http://cyberelk.net/tim/xmlto/">xmlto</ulink>.</para> + <para>If you want to build the Source MUD Manual (this document), you will also need <ulink url="http://cyberelk.net/tim/xmlto/">xmlto</ulink>.</para> <para>All of the above software is generally available for Linux, BSD, and Cygwin.</para> </section> </chapter> doc/ch-installation.xml @@ -2,7 +2,7 @@ <chapter id="ch_introduction"> <title>Introduction</title> <warning>THIS DOCUMENT IS STILL IN DEVELOPMENT!</warning> - <para>AweMUD is a MUD (Multi-User Dungeon) game server. Players connect to the server using telnet, or a MUD client application, to play in a fantasy world with other players.</para> - <para>AweMUD is a new codebase; it is not derived from any older codebases like many other popular MUDs. One consequence of this is that many terms and systems found in most other MUDs are different in AweMUD.</para> + <para>Source MUD is a MUD (Multi-User Dungeon) game server. Players connect to the server using telnet, or a MUD client application, to play in a fantasy world with other players.</para> + <para>Source MUD is a new codebase; it is not derived from any older codebases like many other popular MUDs. One consequence of this is that many terms and systems found in most other MUDs are different in Source MUD.</para> </chapter>  doc/ch-introduction.xml @@ -3,13 +3,13 @@ <title>On-Line Creation</title> <section> <title>Blueprints</title> - <para>Npcs and objects within AweMUD are based on a blueprint system. A blueprint is a description of an npc or object.</para> + <para>Npcs and objects within Source MUD are based on a blueprint system. A blueprint is a description of an npc or object.</para> <para>The blueprint system makes it easy to create new versions of npcs and objects. For example, to create a new longsword in the game, a builder needs only to create a new object with the longsword blueprint. In order to change a property on every longsword in the game, the builder must only update the longsword blueprint.</para> <para>Blueprint are hierarchial. That is, one blueprint may include another. This allows builders to create targetted versions of a particular blueprint. For example, a builder might make an orc blueprint describing a basic orc monster. The builder might then might derivate blueprints for an orc warrior and an orc scout. By changing the orc blueprint, all orc warriors and orc scouts will be updated with the new properties. By changing the orc scout blueprint, only orc scouts will be updated.</para> </section> <section> <title>Zones</title> - <para>AweMUD breaks the game world into zones. A zone contains a collection of rooms.</para> + <para>Source MUD breaks the game world into zones. A zone contains a collection of rooms.</para> </section> <section> <title>OLC Commands</title> doc/ch-olc.xml @@ -1,14 +1,14 @@ <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> <chapter id="ch_scripting"> <title>Scripting</title> - <para>AweMUD makes use of the Scriptix language to extend and modify the behaviour of the core engine. This guide gives a short over-view of using Scriptix with AweMUD. We do not attempt to teach the Scriptix language in this document (that is the job of yet-to-be-written Scritpix Programming Manual).</para> + <para>Source MUD makes use of the Scriptix language to extend and modify the behaviour of the core engine. This guide gives a short over-view of using Scriptix with Source MUD. We do not attempt to teach the Scriptix language in this document (that is the job of yet-to-be-written Scritpix Programming Manual).</para> <section> <title>Using Scriptix</title> - <para>When AweMUD boots up, it loads all the scripts listed in <filename>scripts/load</filename>. Each of these scripts is compiled into bytecode for use by AweMUD. You cannot, at this time, specify the order scripts are loaded, ignore scripts in the Scriptix folder, or load scripts after AweMUD has booted.</para> + <para>When Source MUD boots up, it loads all the scripts listed in <filename>scripts/load</filename>. Each of these scripts is compiled into bytecode for use by Source MUD. You cannot, at this time, specify the order scripts are loaded, ignore scripts in the Scriptix folder, or load scripts after Source MUD has booted.</para> </section> <section id="sect_commands"> <title>Commands</title> - <para>One of the many abilities Scriptix has in AweMUD is to register new commands. A command is what a player types in when playing to game to perform actions or query the server for information.</para> + <para>One of the many abilities Scriptix has in Source MUD is to register new commands. A command is what a player types in when playing to game to perform actions or query the server for information.</para> <section> <title>Command Functions</title> <para>Functions used in Scriptix for commands will receive two parameters: the <link linkend="Creature">creature</link> who entered the command and an array of the command's parsed arguments, as strings.</para> @@ -45,7 +45,7 @@ </section> <section> <title>Registering Commands</title> - <para>In order to AweMUD to know about your command function, you must register the command with the command interpreter. This is done using the <link linkend="registerCommand">registerCommand()</link> function. This function is a little complex; it takes a number of arguments.</para> + <para>In order to Source MUD to know about your command function, you must register the command with the command interpreter. This is done using the <link linkend="registerCommand">registerCommand()</link> function. This function is a little complex; it takes a number of arguments.</para> <para>The first three are solely for documentation and book keeping purposes. Each command must have an official name. This is almost always the same as the first word of the command. I.e., the <command>dance</command> example about would be named <userinput>"dance"</userinput>. The second parameter is a short about string. The about string should briefly describe what the command does. The third argument is a list of usage lines. Usage lines are in the format <userinput>"foo <argument:>\n"</userinput>. The newline is mandatory. You may put in multiple usage lines if your command has multiple formats.</para> <para>The next argument is the most complex. The fourth argument is the format string for the command. The format string tells the command parser how to interpret the command, and how to extract the interesting arguments for the argv[] array passed to the command function. Formatting is described in more detail below. You may pass in either a single string, or an array of strings, for the format argument.</para> <para>The final two bits are simple enough. The fifth parameter is the actual function to call for the command. The final parameter is the necessary permission level required to use the command. The constants <constant>PRIV_PLAYER</constant> and friends can be used here. If you want to allow any creature to use a command, use the permission level of 0 (zero).</para> doc/ch-scripting.xml @@ -1,12 +1,12 @@ -AweMUD Event System -AweMUD Next Generation +Source MUD Event System +Source MUD Copyright (C) 2006 AwesomePlay Productions, Inc. -Sean Middleditch <elanthis@awemud.net> +Sean Middleditch <elanthis@sourcemud.org> ------------------------------------------------- 1. Introduction ============ - AweMUD uses an event message system to control behavior of game entities. + Source MUD uses an event message system to control behavior of game entities. 2. Event Types =========== doc/events.txt @@ -1,13 +1,13 @@ Description and text parsing documentation. -AweMUD Next Generation +Source MUD Copyright (C) 2005 AwesomePlay Productions, Inc. -Sean Middleditch <elanthis@awemud.net> +Sean Middleditch <elanthis@sourcemud.org> ------------------------------------------------- 1. Introduction ============ - AweMUD features a text parsing system that is used for room descriptions + Source MUD features a text parsing system that is used for room descriptions and many other areas of the engine where complex output is required. The text parsing system is designed to allow several important features: doc/parse.txt @@ -1,8 +1,8 @@ /======================================================\ || Game mechanics and rules || - || AweMUD MUD Server Software || + || Source MUD MUD Server Software || || Copyright (C) 2006 AwesomePlay Productions, Inc. || - || Sean Middleditch <elanthis@awemud.net> || + || Sean Middleditch <elanthis@sourcemud.org> || \======================================================/ I Introduction @@ -18,7 +18,7 @@ I Introduction I ----------------------------------------------------------------------------- -This is the game mechanic ruleset used by AweMUD. +This is the game mechanic ruleset used by Source MUD. One important aspect to keep in mind is that the ruleset internally uses numbers of a larger scale than what the players will see. In general, all doc/ruleset.txt @@ -1,6 +1,6 @@ -# AweMUD Next Generation - Animal AI +# Source MUD Next Generation - Animal AI # Copyright (C) 2003 AwesomePlay Productions Inc. -# Sean Middleditch <elanthis@awemud.net> +# Sean Middleditch <elanthis@sourcemud.org> ai.id = "animal" scripts/ai/animal.ai @@ -1,6 +1,6 @@ -# AweMUD Next Generation - Animal AI +# Source MUD Next Generation - Animal AI # Copyright (C) 2003 AwesomePlay Productions Inc. -# Sean Middleditch <elanthis@awemud.net> +# Sean Middleditch <elanthis@sourcemud.org> ai.id = "monster" scripts/ai/monster.ai @@ -1,9 +1,9 @@ /* - * AweMUD NG - Next Generation AwesomePlay MUD - * death.sx - Death hangling for AweMUD + * Source MUD - Next Generation AwesomePlay MUD + * death.sx - Death hangling for Source MUD * Copyright (C) 2000-2003 AwesomePlay Productions, Inc. * See the file COPYING for license details - * http://www.awemud.net + * http://www.sourcemud.org */ var death_time_minutes = 5; scripts/death.sx @@ -1,4 +1,4 @@ -awemud.sx +sourcemud.sx string.sx corerules.sx npc.sx scripts/manifest.txt @@ -1,4 +1,4 @@ -// Stores for AweMUD +// Stores for Source MUD // Copyright (C) 2003 AwesomePlay Productions, Inc. function show_menu (player) scripts/store.sx @@ -1,9 +1,9 @@ /* - * AweMUD NG - Next Generation AwesomePlay MUD + * Source MUD - Next Generation AwesomePlay MUD * whereis.sx - Whereis administration command * Copyright (C) 2000-2003 AwesomePlay Productions, Inc. * See the file COPYING for license details - * http://www.awemud.net + * http://www.sourcemud.org */ // whereis command scripts/whereis.sx @@ -1,5 +1,5 @@ ## -- sourcemud.conf -- -## Configuration file for AweMUD +## Configuration file for Source MUD ## @VERSION@ ## Log file. sourcemud.conf.in @@ -6,10 +6,10 @@ exec_prefix="@exec_prefix@" bindir="@bindir@" tarname='@PACKAGE_TARNAME@' -if ! test -x "$bindir/awemud-bin" || ! test -f "$sysconfdir/$tarname/awemud.conf" ; then +if ! test -x "$bindir/sourcemud-bin" || ! test -f "$sysconfdir/$tarname/sourcemud.conf" ; then echo "You must first 'make install' to use this utility." - echo "To run AweMUD from the source directory, use './awemud-bin'" + echo "To run Source MUD from the source directory, use './sourcemud-bin'" exit 1 fi -"$bindir/awemud-bin" -C "$sysconfdir/awemud.conf" +"$bindir/sourcemud-bin" -C "$sysconfdir/sourcemud.conf" sourcemud.in @@ -2,10 +2,10 @@ # SETTINGS -ADMIN_EMAIL=$(sed -n '/admin:/{s/^.*admin: $.*$$/\1/;p}' awemud.conf) +ADMIN_EMAIL=$(sed -n '/admin:/{s/^.*admin: $.*$$/\1/;p}' sourcemud.conf) PAUSE=$(expr 60 '*' 5) -BIN=$(test -x './awemud' && echo './awemud' || test -x './src/awemud' && echo './src/awemud') -LOG='awemud.log' +BIN=$(test -x './sourcemud' && echo './sourcemud' || test -x './src/sourcemud' && echo './src/sourcemud') +LOG='sourcemud.log' MAIL=$(test -x /usr/sbin/sendmail && echo /usr/sbin/sendmail || which sendmail) # CODE @@ -30,7 +30,7 @@ while true ; do CORE=$(ls core core.* 2>/dev/null) if test -f "$CORE" ; then # mail message - echo 'AweMUD Crash at' `date` > mail.txt + echo 'Source MUD Crash at' `date` > mail.txt echo >> mail.txt # log file @@ -45,7 +45,7 @@ while true ; do rm -f gdb.cmds.txt # do mail - "$MAIL" -s 'AweMUD Crash' "$ADMIN_EMAIL" < mail.txt + "$MAIL" -s 'Source MUD Crash' "$ADMIN_EMAIL" < mail.txt fi # pause before restart startup data/help/awemud.help doc/zmp-x-awemud.txt scripts/awemud.sx 2f0f7e3a4f8f9948307d91594b0dea4c41063e90 Sean Middleditch sean@awesomeplay.com http://github.com/elanthis/sourcemud/commit/c72257402d31a1e50d4b76500c6fbb79adece76f c72257402d31a1e50d4b76500c6fbb79adece76f

2008-11-07T00:55:02-08:00

complete renaming of awemud to source mud 6dbc33770305aa4be3754c3b5da58ebfa6588b38 Sean Middleditch sean@awesomeplay.com