MOO directory

A curated directory of server engines, core databases, and programming resources for MOO (MUD Object Oriented) development, administration, and play.

MOO directory illustration
Placeholder illustration shown while custom artwork is being produced.
category:
pricing_model:

Showing 10 of 10 entries

ToastStunt

open-source

A modern, actively maintained fork of the LambdaMOO server with significant performance improvements and modern features like JSON support and SQLite integration.

Pros

  • + High performance multi-threading
  • + Built-in support for dictionaries and lists
  • + Regular security updates

Cons

  • Deviates from legacy LambdaMOO behavior in edge cases
servermodernc
Visit ↗

LambdaCore

open-source

The foundational database for most MOOs, providing the root object (#0) and basic object hierarchy (Room, Player, Thing).

Pros

  • + Clean slate for world building
  • + Standardized object numbering

Cons

  • Lacks modern utilities and web features by default
databasecorelegacy
Visit ↗

Mudlet

open-source

A modern, cross-platform MUD client with a powerful Lua scripting engine that supports MOO-specific features and ANSI graphics.

Pros

  • + High-speed rendering
  • + Extensive GUI customization via Lua

Cons

  • Requires local scripting for MOO-specific verb editing
clientguilua
Visit ↗

Wikipedia: LambdaMOO

free

Background and history of LambdaMOO, one of the most influential social MOOs.

Pros

  • + Largest existing MOO object database
  • + Significant historical value

Cons

  • Steep learning curve for new users
  • Ancient server code
socialhistoricalactive
Visit ↗

TinyMUX

open-source

Descendant of TinyMUD supporting complex lock systems and attribute-based organization membership tracking for social MUDs.

Pros

  • + Efficient hardcode performance for large playerbases
  • + Compatibility with PennMUSH softcode conventions
  • + Robust locking mechanisms for guild-only areas
  • + Active maintenance and security updates

Cons

  • Compilation required from source
  • Limited built-in web integration compared to modern engines
muxc++performance
Visit ↗

PennMUSH

open-source

Traditional MU* server supporting softcoded guild systems, bulletin boards, and role-based permissions through MUSHcode.

Pros

  • + Mature codebase with decades of guild system examples
  • + Softcode allows in-game modification of org rules
  • + Built-in bboards for faction communication
  • + Extensive compatibility with legacy MUSH tools

Cons

  • Softcode debugging complexity
  • Older networking code requires proxy for modern SSL
mushsoftcodelegacy
Visit ↗

RhostMUSH

open-source

An advanced MUSH engine focused on administrative control, hardened security, and granular permission systems.

Pros

  • + Superior permission and lock management
  • + Built-in support for multiple softcode dialects
  • + Highly configurable server settings

Cons

  • Steep learning curve for administrative setup
  • Documentation can be fragmented across versions
ServerHardenedAdministration
Visit ↗

MUSHcode.com

free

The primary archive for MUSH softcode snippets, featuring global systems for chargen, combat, and economy.

Pros

  • + Searchable database of legacy and modern code
  • + Includes complex systems like +com and +finger
  • + Standardized formatting for easy installation

Cons

  • Some scripts require deprecated engine functions
  • Limited documentation for complex integrations
SoftcodeScriptsLibrary
Visit ↗

AresMUSH

open-source

MUSH server framework with built-in web portal, scene scheduling, and hierarchical organization management for faction-based games.

Pros

  • + Integrated web portal for character rosters
  • + Built-in scene scheduling and room claims
  • + Permission groups for IC organizations
  • + Automated wiki generation from game data

Cons

  • Ruby learning curve for custom extensions
  • Smaller community than traditional MUSH codebases
serverweb-portalruby
Visit ↗

MUD Coders Guild

free

A professional-grade community of developers focused on the technical and social engineering aspects of running text-based games.

Pros

  • + Focus on modern development stacks
  • + Deep dives into player retention tech
  • + Highly collaborative Slack/Discord

Cons

  • Technical barrier to entry
  • Less focus on non-coding admin tasks
codingdev-opsstrategy
Visit ↗