This project is read-only.

Getting Started

  1. Register yourself with CodePlex, if you haven't already done so.
  2. Please introduce yourself briefly with a new thread in the Discussions tab (our forums), with the "Welcome" topic check-marked. Some good things to mention would be how you would like to participate (if not coding), how much experience you have there.
  3. Finding a task... Usually newcomers ask us for a first task, so feel free to talk to any type of systems you might want to dive into first, or start by grabbing the source and perusing it until inspiration strikes; we have plenty of TODOs marked directly in the code, as well as an Issues tab here that we will be maintaining again. (The issues have had their own Jira instance over the last several years, but will be migrating back here soon!)
  4. Get the code and test the server. See Getting Started.
  5. First Contribution. The main repository might be locked down against random changes at first; generally we require just one contribution by patch before giving you full repository write access. It does not have to be a huge chunk of work. You can now upload SVN patches in the Source Code tab. Then, let us know in the forums about your first patch being ready.


If you have a decent handle on the bug, feel free to see if it is tracked arleady in the issue tracker (in the CodePlex Issues tab), or to add it yourself. Alternatively, you can open a new discussion thread. Please report bugs; I'd rather have unresearched bugs sloppily reported to the forums than no bug report at all! Bug fixes make good candidates for that First Contribution patch.

Ideas and Requests

Design suggestions and feature requests are best posted in the Discussions with the "Design" topic selected. We value fresh discussion and opinions even on old threads, so don't be afraid of posting to a "stale" thread.

Non-Coding Contributions

Even if you are not interested in coding, there are a variety of other ways we can use your help. For example:
  • Testing and bug/issue management.
  • Fostering community.
  • Telling your coding friends about us / attracting coders.
  • Documentation.
  • Eventually, area/world building.
  • Eventually, organizing UX (User eXperience testing) sessions.
  • Design discussions.
Note that participating in design does not necessarily mean "we will build your ideal MUD for you"; Our goal here is to build a MUD framework with a variety of base features that we generally agree will be useful or in demand for most MUD implementations.

Last edited Feb 21, 2015 at 8:16 PM by Karak, version 7