100 MUD Scripting resources for MUD players

Utilize the Geyser object-oriented library to create resizable gauges, labels, and mini-consoles that automatically adjust to client window scaling.

Implement event handlers for 'sysDataSendRequest' to parse incoming JSON-like data for health, mana, and room coordinates without using regex on the main buffer.

Use the #VARIABLE and #LOCAL commands to prevent namespace collisions in complex scripts, ensuring state is preserved across session reloads.

Encapsulate Lua scripts within XML plugin files to allow for modular distribution and independent script reloads without restarting the client.

Use tempTimer for delayed execution in combat scripts, ensuring you pass unique IDs to avoid overlapping execution threads.

Use the built-in db: library to store item databases, mob vulnerabilities, and player kill logs for persistent data across sessions.

Automate long-distance travel by recording room exits into a list and using the #PATH WALK command to retrace steps accurately.

Organize large script collections into separate .lua files and load them via 'require' to maintain a clean Mudlet script tree.

Configure client triggers to listen for IAC SB MSDP sequences to update UI elements with server-side variables.

Decouple scripts by using custom events instead of direct function calls, allowing multiple modules to react to the same trigger.

Define base 'std/monster' or 'std/room' objects and use the 'inherit' keyword to minimize code duplication in area building.

Implement dynamic command availability by merging CmdSets based on player state, such as 'CombatSet' or 'InMenuSet'.

Use mappings ([ key : value ]) instead of parallel arrays for efficient lookups of item properties and mob resistances.

Leverage 'ext_sock_connect' and 'ext_sock_write' to allow your MUD to communicate with external Discord bots or web APIs.

Limit the use of heart_beat() to active combatants; use 'set_heart_beat(0)' when an entity is idle to reduce CPU overhead.

Design objects to survive reboots by utilizing DGD's atomic persistence, ensuring player inventory state is never lost.

Implement non-blocking delays for quest triggers or environment changes using call_out(function, delay, args).

Utilize Script objects for global systems like weather, economy, or time, separate from individual character or room instances.

Use the 'shadow()' function to temporarily override methods on a player object, useful for status effects like 'Silence' or 'Confusion'.

Prioritize built-in Efuns over simulated SFuns for intensive operations like string replacement or array sorting.

Use non-capturing groups (?:...) and anchor triggers with ^ and $ to reduce the regex engine's backtracking overhead.

Implement state-based triggers that wait for a specific closing line before processing a block of text (e.g., room descriptions).

Use deleteLine() in Mudlet or #GAG in TinTin++ to remove combat spam while still parsing the hidden text for data.

Design scripts that transition between states (Idle, Buffing, Attacking, Healing) to prevent command flooding and logic errors.

Create aliases that accept arguments ($1, $2) to build flexible command shortcuts that work across different target types.

Write triggers that specifically look for ANSI color codes to differentiate between player speech and system messages.

Implement a Dijkstra algorithm in Lua to calculate the shortest path between two room IDs based on a stored JSON map.

Assign numerical priorities to triggers to ensure critical safety scripts (like auto-flee) execute before cosmetic UI updates.

Build a queue that respects the MUD's Global Cooldown (GCD), sending the next command only after receiving a 'Ready' prompt.

Use coroutines in Lua to pause a script's execution until a specific trigger sets a 'ready' flag, avoiding messy nested callbacks.