100 SMAUG resources for MUD players

The primary maintained fork of SMAUG 1.8. This version includes critical fixes for modern GCC compilers and 64-bit architecture compatibility.

Modern Linux distributions require explicitly linking the crypt library. Ensure your Makefile includes -lcrypt in the L_FLAGS variable to avoid undefined reference errors during the build.

To handle legacy C syntax in SMAUG, add -Wno-format-overflow and -Wno-unused-result to the Makefile C_FLAGS to reduce build noise and prevent build failure on strict environments.

Ensure the 'startup' and 'diststartup' bash scripts are set to chmod 755. These scripts handle the auto-reboot loop and log rotation essential for production stability.

SMAUG requires specific subdirectories in /dist/ (e.g., clans, councils, deities, boards, players) or it will fail to boot. Use 'mkdir -p' for all directories listed in the README.

On first boot, use the 'set' command on the console or an admin character to configure the system.dat file, which stores global MUD variables like the max level and experience rates.

Change the default port in the startup script rather than hardcoding it in the source. This allows for easier testing environments on the same machine.

The area.lst file in the /area/ directory controls the load order. Ensure a newline exists at the end of the file or the final area in the list will fail to load.

Run the binary through Valgrind to identify leaks in custom code, specifically targeting the 'fread_string' function which is a common source of heap issues in SMAUG.

SMAUG supports hotbooting (copyover). Ensure the EXE path in the code matches your actual binary location to allow code updates without disconnecting players.

Use 'makeclan [name]' to create a new clan. This generates a .clan file in the /clans/ directory; manual editing of these files is required for setting specific hall vnums.

Councils are for administrative groups. Use 'makecouncil' to create bodies that can vote on player-submitted changes or manage specific game aspects.

Configure deities using 'makedp'. Each deity requires specific 'favor' requirements (e.g., killing certain mobs) to grant unique spells or skills to followers.

Modify the 'clan_data' struct in mud.h to add banking variables if you want to track clan wealth beyond the stock 'gold' field.

The 'do_induct' and 'do_outcast' functions in clan.c handle membership. Customize these to add level requirements or race/class restrictions for specific clans.

Set the 'board' and 'recall' vnums in the .clan file to ensure members return to their specific headquarters upon death or using the recall command.

SMAUG includes a 'nation' system for racial groupings. Use 'makenation' to create racial alliances that affect how NPCs react to different player races.

The 'order' field in clan files determines if a clan is lawful or chaotic, affecting their ability to ally with other clans and their NPC guards' behavior.

By default, clans do not have salaries. This requires a modification to the 'gain_exp' or 'update_handler' to distribute gold from the clan treasury to members.

The 'war' command toggles clan PK status. Ensure 'perm_pk' is set in the system variables if you intend for a full-time player-kill environment.

The primary tool for NPC creation. Use 'medit [vnum]' to modify stats, flags, and programs. Always save using 'foldarea' after edits.

Used for item creation. Pay close attention to 'value' fields, which vary based on item type (e.g., Value0 for a weapon is the condition, Value3 is the damage type).

Used for environment construction. Use 'redit flags' to set room properties like 'dark', 'no_recall', or 'private'.

SMAUG uses a trigger-based scripting system. Use 'mpedit [vnum]' to add scripts that fire on events like 'greet_prog', 'death_prog', or 'speech_prog'.

Use the 'vassign' command to allocate a block of vnums to a builder. This prevents different areas from overlapping and causing data corruption.

Critical command to save changes from memory to the .are files. Using 'foldarea [filename]' saves a specific area; 'foldarea all' saves everything.

SMAUG's reset system controls how mobs and items respawn. Use 'reset [room_vnum]' to view current resets and 'reset add' to place new entities.

SMAUG allows for 'instazones' where resets happen when the first player enters an empty area. Configure this in the area header via OLC.

Essential diagnostic tools to find where specific items or NPCs are located across the entire world map.

When booting, watch the logs for 'Fix_exits' errors. This indicates broken links between rooms that must be corrected via redit.