Guides

SMAUG with open-source tools

This guide details the process of deploying SmaugFUSS 1.9—the most stable version of the SMAUG codebase—on a modern Linux environment. It addresses specific compilation challenges caused by modern GCC versions and outlines the initial configuration required to boot the engine successfully.

45-60 minutes7 steps
SMAUG with open-source tools hero illustration
1

Prepare the Build Environment

Modern distributions do not include development headers by default. You must install the build-essential suite and zlib1g-dev, as SMAUG uses zlib for MCCP (Mud Client Compression Protocol) and area compression.

terminal
sudo apt-get update && sudo apt-get install build-essential zlib1g-dev

⚠ Common Pitfalls

  • •Missing zlib1g-dev will cause compilation failures in comm.c or telnet.c regarding missing headers.
2

Download and Extract SmaugFUSS

SmaugFUSS is the preferred version of SMAUG due to its numerous bug fixes and removal of legacy code that prevents compilation on modern systems. Extract the source to a dedicated directory.

terminal
wget http://www.smaugfuss.org/download/smaugfuss1.9.tgz
tar -xvzf smaugfuss1.9.tgz
cd smaugfuss1.9/src
3

Modify Makefile for Modern GCC

Modern GCC versions (10+) default to -fno-common, which causes 'multiple definition' errors in SMAUG's global variable declarations. You must explicitly add -fcommon to the C_FLAGS in the Makefile.

Makefile
C_FLAGS = -g2 -Wall -fcommon $(PROF) $(NOCRYPT) $(SYSTEM) $(EXPORT) -D_GNU_SOURCE

⚠ Common Pitfalls

  • •Failure to add -fcommon will result in linker errors during the final stage of compilation.
4

Compile the Binary

Execute the make command. SmaugFUSS uses a standard Diku-style Makefile. Use the -j flag to speed up compilation if your server has multiple cores.

terminal
make -j$(nproc)

⚠ Common Pitfalls

  • •If you see 'crypt' errors, you may need to add -lcrypt to the L_FLAGS in the Makefile.
5

Initialize Directory Structure and Symlinks

SMAUG expects the binary to reside in the parent directory of 'src', usually called 'dist' or the root folder. Move the compiled 'smaug' binary up one level and ensure the 'area', 'player', and 'system' directories exist.

terminal
mv smaug ..
cd ..
mkdir -p player system area boards clans councils gods Deities
6

Configure Port and Initial Boot

The default port is 4000. Start the MUD in the background and monitor the logs to ensure all area files load without corruption. SMAUG is sensitive to malformed VNUMs in stock area files.

terminal
./smaug 4000 > log/boot.log 2>&1 &

⚠ Common Pitfalls

  • •If the MUD crashes immediately, check log/boot.log. Common causes include missing 'system/sysdata.dat' or 'area/area.lst' files.
7

Create the First Immortal Character

Connect to the MUD via telnet or a MUD client. Create a new character. Since there is no 'wizlock' initially, you must manually elevate your level in the character file while the MUD is offline, or use the 'set' command if you have access to a pre-existing admin account.

player/y/Yourname
# Close MUD, then edit the player file:
nano player/y/Yourname
# Change 'Level' to 65

⚠ Common Pitfalls

  • •Never edit a player file while that character is logged into the MUD, as the engine will overwrite your changes on save/quit.

What you built

Your SMAUG instance is now running and accessible. From here, you should focus on configuring 'sysdata' via the in-game 'cset' and 'set' commands to define your MUD's name and gameplay parameters. Familiarize yourself with the OLC (Online Creation) system to modify areas without needing to restart the binary.