A living fantasy world. A community that builds it.
The game, the world-building tools, the web platform, and the Mudlet client behind DurisMUD.
Explore the game server · Explore DurisWeb · Get the Mudlet client · Read the game docs · Contribute to DurisWeb
DurisMUD is a persistent, text-based dark-fantasy world built around a global war between good and evil. Explore dangerous lands, undertake quests, sail ships, craft equipment, join guilds, and pursue powerful artifacts in a world shaped by player-versus-player conflict.
Community Duris brings the game and its web community together. Our three projects cover the simulation and world data, the web platform around it, and the client players use to step inside.
| Duris | DurisWebApp | duris-client | |
|---|---|---|---|
| Purpose | The DurisMUD game server and world. | DurisWeb, the community website and operator platform. | The Arjinius Client, a custom Mudlet interface for playing New Duris. |
| Inside | Combat and gameplay systems, areas, quests, ships, crafting, guilds, persistence, and area-building tools. | PvP data, forums, wiki and guides, auction interfaces, builder tools, and administration. | A three-column game frame, character and group panels, zone and wilderness maps, organized chat, and opt-in automation. |
| Built with | C++20, Linux, MySQL/MariaDB, GnuTLS, and optional Redis integration. | Vue 3, Vite, TypeScript, Tailwind CSS, Express 5, Knex, MySQL, and Redis. | Lua on Mudlet 4.19.1+, Geyser, GMCP, and a Python 3 build script. |
| Start here | Setup and local play · Architecture | Onboarding · Architecture | Install · Build and contribute |
| Follow development | Commits · Issues · Checks | Commits · Issues · Checks | Commits · Issues · Releases |
Players reach the game through a MUD client such as the Arjinius Client for Mudlet. The community website uses a Vue frontend and an Express backend; that backend connects to the game through dedicated integrations. The diagram shows the documented shared-database arrangement.
flowchart TB
Players["Players"]
Community["Community · Builders · Operators"]
subgraph Game["DURIS · Game and world"]
Client["MUD client<br/>duris-client for Mudlet"]
Server["C++20 game server<br/>Combat · Quests · Guilds · Ships"]
World["World data and area tools"]
Client <-->|Telnet / TLS / WebSocket| Server
World -->|Areas and content| Server
end
subgraph Web["DURISWEBAPP · Community platform"]
UI["Vue 3 frontend<br/>PvP · Forums · Wiki · Builder · Admin"]
API["Express 5 + TypeScript API"]
UI <-->|HTTP / WebSocket| API
end
Players --> Client
Community --> UI
Server <-->|Authenticated bridge| API
World -.->|Validated content ingestion| API
Server <-->|Game state| DB[("MySQL / MariaDB<br/>Game-owned tables + web extensions")]
API <-->|Shared data| DB
Server <-.->|Optional integrations| Redis[("Redis<br/>Cache and scoped pub/sub")]
API <-->|Cache and integrations| Redis
classDef people fill:#F1E9DC,stroke:#9A7543,color:#30281E,stroke-width:2px;
classDef game fill:#282431,stroke:#B9975B,color:#FFF3DC,stroke-width:2px;
classDef web fill:#183832,stroke:#57B99B,color:#ECFFF8,stroke-width:2px;
classDef data fill:#1D2D43,stroke:#799DC9,color:#F0F6FF,stroke-width:2px;
class Players,Community people;
class Client,Server,World game;
class UI,API web;
class DB,Redis data;
The game owns the core game-state schema; DurisWeb owns its web extensions and projections. Redis is optional for the game runtime and is a dependency of DurisWeb. For the detailed boundaries, see the game database guide and web integration architecture.
- Explore the game: follow the Duris quick start to set up a local world, or use the Docker development guide.
- Play with the Mudlet client: install the Arjinius Client from its latest release, then read the build and contribute guide to work on it.
- Build the web experience: begin with DurisWeb onboarding, then the development guide.
- Create and improve world content: explore the areas and tools and the game documentation index.
- Help improve the projects: bring reproducible bug reports, focused fixes, clearer documentation, or ideas to the relevant repository's issues and pull requests. Start with the game development workflow, the DurisWeb contribution guide, or the client build guide.
All three projects evolve independently. The activity badges above track their default-branch commits and the client's latest release; deployment compatibility depends on the exact game and web revisions selected together. Setup requirements, feature gates, and known limitations live in the repositories' maintained documentation.
DurisWeb's current documentation identifies remaining security and database-baseline work, and some legacy mutation paths are disabled by default. Read its project considerations, security record, and deployment guide when planning an installation.
Explore the world. Shape the code. Build the community.
