Admin command sets vs Moderation logs vs Builder and even
Selecting a MUD server framework determines your administrative workload, player capacity, and customization ceiling for years. This comparison evaluates four actively maintained architectures representing distinct approaches: Python-based modern web integration (Evennia), JavaScript event-driven systems (Ranviermud), traditional C-based stability (tbaMUD), and the LPMUD lineage (FluffOS). Each targets different technical competencies and project scales.
Evennia
Python-based MUD engine with Django web integration
Best for: Administrators with Python experience requiring web dashboards and modern database ORM
www.evennia.com/ ↗Ranviermud
Node.js event-driven MUD framework with WebSocket support
Best for: JavaScript developers building real-time multiplayer with npm ecosystem integration
github.com/Ranviermud/core ↗tbaMUD
C-based CircleMUD derivative maintaining 1990s Diku traditions
Best for: Administrators seeking stable traditional Telnet MUDs with minimal resource requirements
www.tbamud.com/ ↗FluffOS
Modern LPMUD driver supporting LPC bytecode execution
Best for: Experienced MUD owners requiring massive concurrency and deep Mudlib customization
github.com/fluffos/fluffos ↗| Criterion | Evennia | Ranviermud | tbaMUD | FluffOS | Winner |
|---|---|---|---|---|---|
Installation Complexity Dependencies and build steps required from fresh OS to running server | pip install evennia requires Python 3.8+ and virtualenv | npm install after cloning repo requires Node.js 14+ | ./configure && make requires GCC and standard C libraries | CMake build with C++14 compiler and libevent, jemalloc, or pcre dependencies | Evennia |
Default Database System Persistent storage mechanism for player data, rooms, and objects | SQLite default with Django ORM supporting PostgreSQL and MySQL migrations | JSON flat files via node-persist with MongoDB driver available | Binary .mob/.obj/.wld flat files with ASCII playerfile storage | LPC internal save_object() to binary files with external SQL driver support | Evennia |
Concurrent Player Capacity Realistic player limits without architectural modifications on standard VPS hardware | 50-150 players depending on Python event loop efficiency | 100-300 players via Node.js async event loop | 50-100 players limited by synchronous C select() loop | 200-500+ players depending on Mudlib efficiency and epoll implementation | FluffOS |
Scripting Language for Builders Language available to non-coder staff for creating quests, mobs, and events | Python with full access to Django ORM and Evennia typeclasses | JavaScript/ES6 with access to npm modules and entity scripts | DG Scripts (proprietary C-like language) with trigger-based logic | LPC (C-like syntax with object inheritance) compiled to bytecode | Ranviermud |
Web Client Architecture Built-in browser-based play without Telnet requirement | Django web client with WebSocket or AJAX polling, web admin at /admin/ | React-based web client bundled with WebSocket transport in core | None - requires external Java web clients or standalone clients | None in core - requires separate web-to-Telnet proxy or packages | Evennia |
Documentation Quality Completeness of API references, tutorials, and troubleshooting resources | Extensive ReadTheDocs with tutorials, API autodocs, and active Discord support | README-driven documentation with JSDoc comments, smaller community knowledge base | 20+ years of accumulated forums, CircleMUD heritage docs, tbaMUD specific wiki | Driver docs on GitHub wiki, Mudlib-dependent documentation scattered across LP sites | Evennia |
Active Development Status Frequency of commits, releases, and security patches in past 12 months | Monthly releases with 500+ commits annually, funded via Patreon | Maintenance mode with quarterly dependency updates, seeking maintainers | Stable maintenance with bi-annual releases focusing on bug fixes | Active driver development with weekly commits, multiple Mudlib projects | Evennia |
Core Modification Requirements Language and compilation needed to change fundamental game mechanics | Python-only for most changes, no restart required for code updates | JavaScript changes restart Node process or use hot-reload modules | C source edits require make and server restart | LPC Mudlib changes reloadable, C++ driver changes require rebuild | Evennia |
Hosting Cost Profile Minimum viable server specifications and compatible hosting types | 2GB RAM VPS, compatible with Python hosting platforms | 1GB RAM VPS, runs on Node.js PaaS like Heroku or Railway | 512MB RAM sufficient, runs on minimal Linux shell accounts | 2GB+ RAM recommended for large Mudlibs, requires dedicated server or VPS | tbaMUD |
Security Model Built-in protections against common MUD exploits and player griefing | Django CSRF protection, input sanitization, permission-based lock system | Event-based command validation, no traditional MUD command injection | Traditional MUD permission flags, buffer overflow risks in C string handling | Sandboxed LPC execution, master object controls player permissions | Evennia |
Builder Onboarding Curve Time for non-programmer staff to create playable content | High - requires understanding Python classes and typeclass system | Moderate - YAML area definitions with JavaScript for behaviors | Low - familiar OLC (Online Creation) menu commands for rooms and mobs | Very High - must master LPC inheritance and Mudlib conventions | tbaMUD |
External Library Ecosystem Access to modern libraries for HTTP APIs, databases, or game features | Full PyPI access including Discord bots, web scraping, ML libraries | Full npm registry access for real-time services and modern tooling | None - self-contained C code with no external dependency management | Limited - LPC packages exist but ecosystem is insular and aging | Ranviermud |
Our Verdict
Evennia dominates for administrators prioritizing web integration and modern Python ecosystems but requires accepting higher memory usage and Python proficiency. Ranviermud suits JavaScript developers wanting npm access but accept maintenance uncertainty. tbaMUD remains the choice for traditionalists needing minimal resources and simple builder tools. FluffOS serves established MUDs scaling to hundreds of concurrent players with dedicated technical staff.
Use-Case Recommendations
Scenario: First-time MUD administrator with web development background
→ Evennia
Python familiarity transfers directly, Django admin provides immediate web-based building tools, and documentation prevents common new-admin pitfalls
Scenario: Free-to-play hobby MUD on minimal $5/month VPS budget
→ tbaMUD
Runs on 512MB RAM without swap, compiles on smallest DigitalOcean droplets, and twenty years of optimization produces stable CPU usage
Scenario: Commercial MUD targeting 200+ concurrent subscribers
→ FluffOS
Event-driven epoll implementation handles high concurrency, LPC Mudlib allows runtime modifications without player disconnections, and proven track record at larger MUDs
Scenario: Rapid prototype for narrative game jam with web deployment
→ Ranviermud
npm init installation completes in minutes, WebSocket client works immediately for browser-based playtesters, and JavaScript allows quick iteration
Scenario: Educational institution teaching MUD history and C programming
→ tbaMUD
Source code readability for C students, direct lineage to original DikuMUD, and no external dependencies complicating lab computer setups
Scenario: MUD requiring Discord bot integration and modern web APIs
→ Evennia
Native Python allows discord.py integration, Django REST framework provides API endpoints, and web client can embed directly in modern sites
.