The RPMUD Network is a site dedicated to the independent collection, research, documentation, and critical review and analysis of information regarding Role-Playing MUDs, serving as a source for this information and other services for the use by the games, staff, and players of Role-Playing MUDs; and to encourage, recognize, and support the development and prosperity of the field of Role-Play MUDding in general.

Founded by Wade Gustafson in 2005 as the RPIMUD Network, the site provided free listings for MUDs, rank voting, advertising, forums, trivia and reviews. In 2007, the site transferred ownership and a five-person Operating Committee took over management of the site. On November 12, 2008 the Operating Committee approved a name change and ratified a Charter which defined their role and duties as well as the structure of the management of the site, laying the groundwork for how the RPMUD Network operates today. The site is maintained by a committee of nine members including six permanent staff and three elected by and from the community of RP games.

The RPMUD Network categorizes MUDs into three groups for ease in helping players find just the kind of Role-Play MUD they desire.  Each of these groups also elects representatives to sit on the Operating Committee that runs this site.  The groups are designated as RPE (Role-Play Enforced), RPI (Role-Playing Intensive), and RPO (Role-Playing Oriented).

Role-Playing Enforced (RPE)

Role-Playing Enforced (RPE) MUDs are all Role-playing MUDs which feature a policy of required role-playing at all times.  This distinction separates them from games where role-playing is not consistently enforced (ie, encouraged) or only conditionally enforced (ie, in cases of PK only, etc).  Additionally, for the use of this site, MUSHes, MOOs, and other forms of text-based gaming which do not fit the other two categories are included in this group so long as they feature a policy of required role-playing at all times.

Role-Playing Intensive (RPI)

Role-Playing Intensive (RPI) MUDs are RPEs that adhere to the nineteen characteristics shared by the two original code-bases that comprised and gave birth to the term, those of Armageddon and Harshlands.  These features include, but are not limited to:

1. Strict in-character behavior enforcement:  Players are expected to remain in-character at all times while in the game and speak and act as their character would (exceptions existing only for issues of emergency assistance).  This feature is found in RPOs and RPEs as well.
2. World-driven code:  RPIs are designed around the philosophy that code design follows world design.  Rather than the characteristics and nature of the game’s world conforming to the parameters and features of the code, RPIs’ adapt the code to fit the needs of the world’s characteristics.
3. Mechanics-based world and use-based advancement:  RPIs employ code where possible to simulate the mechanics and chances of success in things such as communication (ie, understanding languages), combat, or production of articles (ie, crafting).
4. Use-based advancement:  RPIs employ use-based advancement of skills and abilities in place of traditional methods of point allocation.  Use of a skill or ability is the only way to improve that skill or ability, either through direct use or via crafts.
5. Descriptive, generalized skill aptitude and abilities/attributes:  A character’s aptitude in the skills they possess is represented through descriptive, generalized terms which prevent precision in assessment and advancement.  Likewise, a character’s physical and mental attributes such as strength and intelligence are represented by descriptive, generalized terms to prevent precise assessment.
6. An enhanced emote system:  RPIs feature a system of emotes and similar commands by which actions not dictated by code functions may be carried out.
7. Permanent character death:  With the exception of non-IC-related incidents, death is permanent and typical MUD resurrection systems are not present.
8. Lack of global out-of-character (OOC) channels for player use:  Use of semi-global channels is limited in range and function and all OOC channels are restricted only for limited staff use.
9. Lack of a detailed “who” list:  The traditional “who” command is limited by removing a list of players or characters online and showing only total numbers online or via complete removal of this function altogether
10. Detailed character creation and staff approval:  Players are expected to submit detailed characters with full descriptions and personality backgrounds subject to approval before entering the game.
11. Lack of levels:  Traditional MUD levels are not employed by RPIs.
12. Lack of traditional mud-classes:  Traditional, confining code-based classes found on most MUDs, typically used to categorize character types, are absent from RPIs.  Some RPIs use “classes” or “professions” which serve merely as tools for skill selection but which do not require adherence or limitation only to those skills and professions.
13. Lack of experience point systems:  RPIs feature a complete lack of “experience point” systems (XP).
14. Description-based identities:  Characters are only identifiable by descriptions and other information that could be gleaned through observation alone.
15. Description-based objects:  Objects feature descriptions which are used to judge their quality or identity (for example, no “Sword of Billy the Merciless”).
16. Described rooms:  RPIs feature rooms with detailed IC descriptions.
17. Detailed world design:  RPIs feature comprehensive world designs encompassing the various aspects of socio-cultural characteristics of the setting.  These include but are not limited to political, historical, economic, and religious systems which provide players with depth to the setting and a clear framework in which their character exists.
18. Single character per player:  RPIs possess a policy limiting players to possession of one character at a time and multi-playing is strictly forbidden.
19. In-character situation-dependant killing:  Killing is restricted to require in-character motivations for the killing of PCs and NPCs.  The goal of RPIs is not to kill to advance or to kill without regard for the setting and situation (ie, laws and justifiable reason to break such laws).

Role-Playing Oriented (RPO)

Role-Playing Oriented (RPO) MUDs are a term created uniquely for this website.  The term was invented in 2006 as a means of recognizing that the original distinction between RPI and RPE was no longer as clear as it had once been.  RPOs, like RPIs, are all Role-Playing Enforced but possess one or more of the seventeen other characteristics listed above.  As yet there is no definite pattern of which of those characteristics an RPO must possess.  Some may possess five, others ten, some even fifteen.  The lack of a standardized set of characteristics, however, makes grouping very difficult.  A RPO with only five of those features may have the five that a RPO with twelve does not.  As such, each represents an independent Role-Playing MUD type with a distinct feature set.  For the sake of avoiding potentially dozens if not hundreds of separate categories, the RPMUD Network uses the designation of RPO in referring to these games.

The RPMUD Network Charter is a document outlining the overall operation and organization of the site, its purpose, and its management.  Written over a period of several weeks in late 2008, the Charter was approved by the ad-hoc Operating Committee on November 12, 2008 and formally established the purpose and name-change of the site as well as the composition and duties of the Operating Committee.

ADMINISTRATING CHARTER OF THE RPMUD NETWORK

ARTICLE I:  PURPOSE 

A.        The purpose of the RPMUD Network shall be to provide a site for the independent collection, research, documentation, and critical review and analysis of information regarding Role-Playing MUDs; to serve as a source for this information and other services for the use by the games, staff, and players of Role-Playing MUDs; and to encourage, recognize, and support the development and prosperity of the field of Role-Play MUDding in general.

B.         The RPMUD Network shall maintain a website, forums, and other services for freely-accessible collection and distribution of independently-collected and researched statistical and critical data for the purpose of encouraging, documenting, recognizing, and supporting of the development and prosperity of Role-Play MUDs.

ARTICLE II:  COMPOSITION AND MEMBERSHIP OF RPMUD NETWORK

A.        The RPMUD Network shall be comprised of an Operating Committee comprised of the following:

            1.         Five (5) or more Standing Committee Members

            2.         Three (3) Elected Members

            3.         Honorary Non-Voting Members

B.         The RPMUD Network shall also be comprised of staff, players, and interested parties from, but not limited to, the following in accordance with Article V, Section A:

1.                  Role-Play Intensive MUDs

2.                  Role-Play Oriented MUDs

3.                  Role-Play Enforced MUDs

4.                  Anyone interested in the above.

C.        Membership in the RPMUD Network shall be open according to the following:

1.                  Affiliate Games may join freely but are subject to confirmation by the Operating Committee in accordance with Article V.

2.         Individuals may join freely in accordance with Article VI.

A.        Standing Members

1.         The Operating Committee shall consist of a minimum of five standing members who are not subject to election.

2.         Standing members shall be appointed by unanimous consent of the Operating Committee membership and shall serve until resignation or removal.

B.         Elected Members

1.                  The Operating Committee shall contain one elected member representing each type of Role-Playing Game as defined by Article V.

2.                  Elected Members shall serve terms of one (1) year except in the event of resignation, removal, or in the case of special election or appointment.  The normal term of office shall run from January 1 through December 31.

3.                  Election

a.         Each open game may nominate one (1) person for their respective group according to a process of their choosing.  Candidates must be selected and passed on to the Operating Committee no later than two (2) weeks prior to the election.  All candidates will be confirmed by the Operating Committee no later than one (1) week prior to the election.

b.         Elections shall be held on the first full weekend of December.

c.         Votes

i.          Each game shall receive one (1) vote in their respective group.

ii.          Each Standing Committee member shall receive one (1) vote for each group.

iii.                  In the event of a tie, a run-off shall be held the following weekend.

iv.                 In the event of a further tie, another run-off shall be held in which only the Standing Members of the Operating Committee shall each cast one (1) ballot each.

v.                   In the event of a further tie, the candidates shall draw lots to decide the winner.

vi.                 The Election process must be completed prior to the end of the existing term of office.

4.         Standing Committee Members are not eligible to hold both Standing and Elected office simultaneously.

5.         In the event that a seat is not filled, the Operating Committee may, at their discretion, fill the seat by appointment for the remainder of the term or until the next election, whichever may come first or leave it vacant.  If left vacant, the empty seat shall not calculate into quorum or any other votes.  The Operating Committee may also hold special elections later in the term to fill any vacancies which may exist.  These elections shall be conducted by the same method outlined in Article III, Section B, Subsection 3, paragraph c.

C.        Honorary Members

1.                  The Operating Committee may designate Honorary Membership status to anyone they so deem.

2.                  Honorary Members do not require re-appointment.

3.                  Honorary Members do not possess any of the powers listed in Article IV.

ARTICLE IV:  DUTIES, POWERS AND REMOVAL OF OPERATING COMMITTEE MEMBERS

A.        Duties, Powers, and Removal of the Standing Committee Members

1.                  Standing Committee Members shall each possess one (1) vote.

2.                  Standing Committee Members duties shall include, but are not limited to, the following:

a.         Operation and maintenance of the RPMUD Network website.

b.         Monitoring of the RPMUD Network forums.

c.         Policy Determination.

d.         Enforcement of RPMUD Network Policies.

e.         Operation of the annual elections.

f.          Representing the RPMUD Network in an official capacity.

g.         Attending the meetings scheduled by the Committee.

3.                  Removal of Standing Committee Members

a.                   Removal of a Standing Committee Member shall require the following:

i.          Initiation of removal proceedings must occur within two (2) weeks if a majority of the total membership of the Operating Committee approves.

ii.          Removal of a Standing Member of the Operating Committee shall require a two-thirds (2/3) vote of the total membership of the Committee.

b.         Removal of a Standing Member of the Operating Committee shall be immediate if the two-thirds (2/3) vote is achieved.  The Committee may then consider appointment of a new Standing Member.

B.         Duties, Powers, and Removal of the Elected Committee Members

1.         Elected Committee Members shall each possess one (1) vote.

2.         Elected Committee Members duties shall include, but are not limited to, the following:

a.         Operation and maintenance of the RPMUD Network website.

b.         Monitoring of the RPMUD Network forums.

c.         Policy Determination.

d.         Enforcement of RPMUD Network Policies.

e.         Operation of the annual elections.

f.          Representing the RPMUD Network in an official capacity.

g.         Attending the meetings scheduled by the Committee.

3.         Removal of Elected Committee Members

a.         Initiating removal of an Elected Committee Member shall require the following:

i.          Initiation of removal proceedings by a majority of the total membership of the Operating Committee.

ii.          Petition for removal approved by a majority of the respective games which the Elected Member represents.

                        b.         Removal Process

i.          If one of the above requirements is met, the Operating Committee shall convene within two (2) weeks to vote on removal of the member in question.

ii.          Removal of an Elected Member of the Operating Committee shall require a two-thirds (2/3) vote of the total membership of the Committee.

iii.                  Removal of an Elected Member of the Operating Committee shall be immediate if the two-thirds (2/3) vote is achieved.

c.         In the event of removal of an Elected Member, the Operating Committee shall hold a special election no more than one (1) month following unless removal occurs within one (1) month of the annual election.  In the event that no eligible candidate runs, the Operating Committee may fill the seat by appointment at their discretion or leave it vacant.  If left vacant, the empty seat shall not calculate into quorum or any other votes.

ARTICLE V:  AFFILIATE MEMBERSHIP

A.        The RPMUD Network shall recognize the following types of games as eligible for affiliation and representation.

            1.         Role-Play Intensive (RPI) MUDs

a.         The designation of Role-Play Intensive (RPI) shall apply to all MUDs which adhere to all of the following characteristics.

i.          Strict in-character behavior enforcement.

ii.          World-driven code.

iii.         Mechanics-based world and use-based advancement.

iv.         Use-based advancement.

v.         Descriptive, generalized skill aptitude and abilities and/or attributes.

vi.         An enhanced emote system.

vii.        Permanent character death.

viii.       Lack of global out-of-character (OOC) channels for player use.

ix.         Lack of a detailed “who” list.

x.         Detailed character creation and staff approval.

xi.         Lack of traditional levels.

xii.        Lack of traditional mud-classes.

xiii.       Lack of experience point systems.

xiv.       Description-based identities.

xv.        Description-based objects.

xvi.       Described rooms.

xvii.      Detailed world design.

xviii.     Single character per player policy.

xix.       In-character situation-dependant killing.

b.         Recognition of this designation must be confirmed by the Operating Committee.

            2.         Role-Play Oriented (RPO) MUDs

a.         The designation of Role-Play Oriented (RPO) shall apply to all MUDs which adhere to a policy of strict in-character behavior enforcement and two or more of the following:

i.          World-driven code.

ii.          Mechanics-based world and use-based advancement.

iii.         Use-based advancement.

iv.         Descriptive, generalized skill aptitude and abilities and/or attributes.

v.         An enhanced emote system.

vi.         Permanent character death.

vii.        Lack of global out-of-character (OOC) channels for player use.

viii.       Lack of a detailed “who” list.

ix.         Detailed character creation and staff approval.

x.         Lack of traditional levels.

xi.         Lack of traditional mud-classes.

xii.        Lack of experience point systems.

xiii.       Description-based identities.

xiv.       Description-based objects.

xv.        Described rooms.

xvi.       Detailed world design.

xvii.      Single character per player policy.

xviii.     In-character situation-dependant killing.

b.         Recognition of RPO designation shall not apply if the requirements of Article V, Section A, Subsection 1 are met.

c.         Recognition of this designation must be confirmed by the Operating Committee.

            3.         Role-Play Enforced (RPE) MUDs

a.         The designation of Role-Play Enforced (RPE) shall apply to all MUDs which adhere to a policy of strict in-character behavior enforcement.

b.         Recognition of RPE designation shall not apply if the requirements of Article V, Section A, Subsection 1 or Article V, Section A, Subsection 2 are met.

c.         Recognition of this designation must be confirmed by the Operating Committee.

4.         Affiliate MUDs may only be assigned one designation and will be reconfirmed annually by the Operating Committee.

B.         Each affiliate member (RPI, RPO, and RPE games) shall each possess the following:

1.         Each affiliate member shall be able to nominate one candidate for election to their respective seat on the Operating Committee by a method of their own choosing.

2.         Each affiliate member shall possess one (1) vote in any matter of referendum and one (1) vote in the annual election.

3.         Each affiliate member shall be able to initiate a petition for removal of an Elected Member of the Operating Committee and shall possess one signature to that effect.

ARTICLE VI:  INDIVIDUAL MEMBERS OF THE RPMUD COMMUNITY  

A.        Individual members of the RPMUD community are defined as anyone expressing an interest in joining the community.

B.         The RPMUD Network shall not restrict membership on the basis of race, gender, sexual orientation, disability, age, ethnicity, nationality, or affiliation.

C.        Individual members of the community may be removed and banned if a two-thirds vote of the Operating Committee approves such a measure based on one of the following reasons:

            1.         Criminal behavior such as hacking or theft.

            2.         Inappropriate behavior such as harassment.

ARTICLE VII:  POLICY PROCEDURE

A.        Policies of the RPMUD Network are determined by the Operating Committee according to the following process:

1.         Initiation of discussion may be made by any member of the Operating Committee.

2.         Discussion of the policy shall be conducted until said discussion is exhausted or a motion to vote is made.

            3.         If a motion to vote is made the following shall occur:

a.         A second to the motion must be obtained.  If the motion is not seconded discussion shall continue.

b.         If a second is obtained an immediate vote to end discussion shall be taken.  If successful the vote on the matter on hand shall be taken.

4.         If an amendment to the policy being discussed is made the following shall occur:

a.         A second to the motion must be obtained.  If the amendment does not receive a second discussion of the original policy shall continue.

b.         If a second is obtained discussion of the amendment shall commence until exhausted or a motion to vote is made.

c.         When a motion to amend the policy being discussed is voted upon a two-thirds vote of the members present shall be required to pass.

d.         Upon completion of the vote to amend the discussion shall revert to the policy as so amended.

5.         When a motion is made to vote a majority vote of the members present shall be required for approval.

B.         Amendment of existing policies of the RPMUD Network shall follow the above process but shall require a two-thirds vote instead of a simple majority.

C.        Policies covered under this process include anything affecting the operation of the committee or the RPMUD Network not covered in this Charter.

D.        The Operating Committee may form and approve its own rules of order where not specified in this charter.

E.         Quorum of the Operating Committee shall be set as a majority of the total membership of the committee.  This number of members present shall be sufficient except where otherwise noted.

F          The Operating Committee shall elect from its membership a chair, a vice-chair, and a secretary within two (2) weeks of the start of the new year.

1.         The chair shall run the meetings of the Committee.

2.         The vice-chair shall run the meetings in the absence of the chair.

3.         The secretary shall maintain minutes of the meetings.

A.        Amendments to the Charter may be introduced to the Operating Committee by either of the following:

            1.         Any member of the Operating Committee.

            2.         Petition by a majority of the Affiliate games.

B.         Amendments to the Charter require a three-quarters majority of the total membership of the Operating Committee.

C.        Amendments to the Charter are effective at the start of the new year unless otherwise noted in the amendment itself.

ARTICLE IX:  RATIFICATION

A.        Ratification of this Charter shall require an unanimous approval of the total membership of the existing operating committee.

B.         Upon successful ratification, this Charter shall go into immediate effect.

The RPMUD Network is managed by an Operating Committee comprised of at least five permanent standing members and three elected members, chosen by annual elections from the three types of affiliate games.

The present Standing Committee members are:

Falco (Jason Mount):  One of the original members of the Operating Committee, Falco joined the site’s administration with the new managing committee in 2007.  A former administrator on Shadows of Isildur, Falco holds three degrees in history and has been playing MUDs since January 1997.  His first role-playing MU* was Harshlands in 1999 and over the past decade he has tried out or played nearly 1000 different MU*s including every RPI ever to open (and quite a few which haven’t).  In January 2004, Falco joined the staff of Shadows of Isildur and served as a Role-Play Administrator there until January 2005 when he left to form his own RPI:  the historical-based, Victorian-themed The Streets of Yesterday (TSOY).  A long-time supporter of the RPI, RP, and MUD communities and the longest-serving member of the Operating Committee, Falco was elected by the committee to serve as their Chair.  He may be contacted by emailing Falco(at)rpmud.net

Garibaldi (Anthony Stauder):  A relative newbie to the RP* Community when he joined the staff of The Streets of Yesterday in 2005, Garibaldi holds a degree in computer science.  He may be contacted by emailing Garibaldi(at)rpmud.net

Jack:  Involved with MU*s since 1997, Jack has been equally interested in RP MUDs as well as MUSH during that time.  A frequent player of several, he has also been a builder on three different MU*s as well as founded two games in the pre-alpha stage:  Camino Real and Urbana.  He may be contacted by emailing Jack(at)rpmud.net

Kerrida:  A longtime player of MUDs, Kerrida is presently designing and coding her own game.  She was elected Secretary of the Operating Committee in March 2009.  Kerrida may be contacted by emailing Kerrida(at)rpmud.net

Mycroft (Darren Dale):  A longtime player of text-based games, Mycroft's experience dates back to 1996 and also includes administrative and coding positions on First Defence Fleet (FDF) and The Streets of Yesterday (TSOY).  He was elected Vice-Chair of the Operating Committee in March 2009.  Mycroft may be contacted by emailing Mycroft(at)rpmud.net

Parhelion:  First introduced to the world of MUDs through a stock diku by the name of Crimson MUD II in 1997, Parhelion has since volunteered or held building and administrative positions across numerous MUDs or MUD organizations, including Public Relations with the LPUniversity Foundation in ‘05-‘06 and Accursed Lands in ‘06-‘08. In 2005, she began work on her own short-lived RPI, dubbed Aurora, a project once again put into the works in late 2008 with the hopes of becoming a future platform for innovation in artificial life research and philantropy. Although a student of modern game design and software, Parhelion has been a long-term supporter of the text-based game community. She originally served on the Operating Community by special appointment but was made a permanent member in November 2010.  Parhelion can be reached by emailing parhelion(at)rpmud.net

Also serving on the Operating Committee are the following Elected Members:

Shadow:  Elected in December 2008, Shadow is an administrator on Shadows of Isildur and sits on the Operating Committee as the RPI representative.  Shadow was reelected to this seat in the 2009 elections.  She may be contacted by emailing Shadow(at)rpmud.net

Chibible (Sparks):  A 21 year old college senior, currently on his last semester of
college at SUNY Plattsburgh, Chibible is aiming for a Bachelor of Science in
Environmental Science. His future career goals are unknown but he has ties at
JC Broderick and Associates as an air sampling technician. He currently
works as an extremely basic coder and themer in Accursed Lands, and is
still learning a fair bit about code. His interests include video games,
swordfighting, and most roleplaying games, especially Dungeons and
Dragons. His main place of residence is Long Island, New York.  He may be contacted by emailing Chibible(at)rpmud.net

Also elected in the 2009 elections was Milawe from Threshold.  Biographical information is pending.