100 MUSH / MUX resources for MUD players

The primary repository for PennMUSH. Use this for the most feature-rich engine with built-in JSON support and extensive function libraries.

Optimized for performance and stability. Best for high-concurrency games that require a lean memory footprint and traditional MUX flavor.

A highly configurable engine that offers advanced security features and compatibility layers for both PennMUSH and TinyMUX softcode.

Essential for modernizing MUSH connections. Use Stunnel to wrap the telnet port in SSL, allowing clients like Mudlet to connect securely.

Configure the mush.cnf to link with MySQL/MariaDB. This allows softcode to query external databases for web-to-game synchronization.

Implement a cron job to trigger '@dump' and move the resulting flatfile to off-site storage to prevent data loss from server failure.

Determine if a feature (like a custom combat parser) should be a C-level 'hcode' module or a softcode system based on performance needs.

Standardize on port 4201 or 6666; ensure iptables or ufw allow both the game port and the HTTP port for web-based help files.

Enable UTF-8 in the engine configuration to allow players to use extended character sets for foreign languages or decorative symbols.

When porting legacy systems, use the compatibility flags in RhostMUSH to support older NetMUSH-style function syntax.

Designate a 'Master Room' (typically #2) to hold objects with 'COMMAND' flags, ensuring global availability of +help or +who.

Use u() for calling code on attributes and z() for executing code on remote objects to keep logic modular and reusable.

Master iter(), map(), and filter() for handling space-delimited lists, which are the primary data structure in softcode.

Use the switch() function within a command attribute to handle multiple arguments and sub-commands efficiently.

Utilize the 10-30 available registers (q0-q9, qa-qz) to store temporary variables during complex calculations to reduce db lookups.

Use @parent to create archetypes (like a generic 'weapon' object) and inherit attributes to child objects for easier mass updates.

Organize data using backtick notation (e.g., STATS`STRENGTH) to create clean, searchable namespaces on character objects.

Apply regmatch() and grep() for advanced string parsing in user input, essential for complex chargen or combat logs.

Apply the WIZARD, TRUST, or INHERIT flags carefully to objects to prevent unauthorized execution of restricted functions.

Understand the difference between functions that return strings and side-effect functions (like create() or set()) that modify the DB.

Build a multi-room character generation sequence using 'AENTER' attributes to guide players through stat allocation and bio entry.

Implement a global +bbs system for out-of-character announcements and in-character news, using object-based storage for posts.

Create a tool for logging roleplay sessions, allowing players to start/stop scenes and automatically save the output to a web archive.

Develop a system for players to set 'RP Preferences' (e.g., +consent/combat) to ensure safe and collaborative storytelling.

Use the @desc attribute with embedded functions to change room descriptions based on time of day or current weather variables.

Configure the built-in 'comsys' to separate narrative channels from technical support or social chatter channels.

Build a 'Wallet' object parented to characters that tracks balance and allows for +pay and +buy commands via softcode.

Use a single 'Parent Room' for all grid locations to provide uniform 'look' commands and global exits to a central hub.

Customize the +finger command to display IC stats, faction membership, and last-seen timestamps via a global command object.

Implement a +map command that uses the loc() function to determine player coordinates and display an ASCII representation of the area.