SMAUG directory

A curated directory of codebases, development tools, and technical documentation specifically for the SMAUG (Simulated Medieval Adventure multi-User Game) ecosystem, focusing on SmaugFUSS and modern Linux compatibility.

SMAUG directory hero illustration
Category:
Pricing Model:

Showing 10 of 10 entries

Nick Gammon's SMAUG Forum

free

A deep technical archive of SMAUG-specific coding discussions, focusing on SmaugFUSS and MUSHclient integration.

Pros

  • + High-quality technical solutions for complex C bugs
  • + Detailed explanations of the SMAUG Online Creation (OLC) system
  • + Searchable archive of decade-long development history

Cons

  • Lower frequency of new posts in recent years
  • Heavy focus on MUSHclient as the primary interface
SupportCodingTroubleshooting
Visit ↗

Smaug Codebase

open-source

A heavily modified Merc derivative with advanced features like overland maps, complex triggers, and an in-game building system.

Pros

  • + Includes sophisticated Online Creation (OLC) tools
  • + Advanced mob and room trigger system
  • + Support for complex item properties

Cons

  • High complexity makes customization difficult for beginners
  • Massive code footprint
SmaugOLCMerc
Visit ↗

Wikipedia: DikuMUD

free

Overview of DikuMUD history, code lineage, and licensing context for derivative codebases.

Pros

  • + Critical legal information for server admins
  • + Clarifies 'no-profit' clauses
  • + Official source

Cons

  • Highly restrictive compared to MIT/GPL
  • Can limit monetization options
LegalLicenseCompliance
Visit ↗

CircleMUD 3.1

open-source

A highly documented and stable derivative of DikuMUD, emphasizing clean code and ease of use for new administrators.

Pros

  • + Extensive built-in documentation
  • + Standardized coding style
  • + Large historical library of public patches

Cons

  • Development has largely ceased
  • Requires significant updates for modern C compilers
CircleMUDCEngine
Visit ↗

tbaMUD

open-source

The current standard for CircleMUD development, providing a clean, bug-fixed version of CircleMUD 3.1 with integrated OLC and DG Scripts.

Pros

  • + Active community support
  • + Modern compiler compatibility
  • + Extensive built-in documentation

Cons

  • Diverges from original Circle 3.0 directory structures
COLCActive
Visit ↗

MudBytes

free

Codebase repository and snippet sharing platform with forums for administrative discussions. Resource for understanding legacy systems during staff transitions.

Pros

  • + Codebase repository for comparisons
  • + Snippet sharing for solutions
  • + Forums for admin advice

Cons

  • Interface aging
  • Smaller active user base than historical peaks
codebasesnippetsforums
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 ↗

GDB (GNU Debugger)

open-source

The primary tool for debugging CircleMUD core dumps and identifying the exact line causing a crash in C source code.

Pros

  • + Industry standard for C debugging
  • + Allows backtracing of stack frames

Cons

  • Requires compilation with the -g flag
  • Command-line only
DebuggingCAdvanced
Visit ↗

Valgrind

open-source

An instrumentation framework for building dynamic analysis tools. Used to detect memory leaks in Merc's recycling systems.

Pros

  • + Identifies 'definitely lost' memory blocks
  • + Finds uninitialized variable usage

Cons

  • Significant performance overhead during testing
memoryprofilingc
Visit ↗

Docker Hub (i386 Images)

freemium

Repository for 32-bit container images, essential for running legacy MUD codebases (ROM, Circle, Merc) on modern 64-bit hosts.

Pros

  • + Isolates legacy library dependencies from the host OS
  • + Easily replicate the exact build environment across servers
  • + Simplifies migration between different hosting providers

Cons

  • Requires learning Docker containerization
  • Slight overhead compared to bare-metal execution
LegacyDockerCompatibility
Visit ↗