100 Immortals resources for MUD players

The entry-level staff role focused on answering newbie questions and monitoring public channels without access to destructive commands.

Trial role with restricted VNUM ranges; tasks include room description writing and basic mob placement under the supervision of a Senior Builder.

Granted independent access to OLC (Online Creation) for assigned zones, including the ability to write basic mob and room triggers.

Specialized role with permissions to load temporary objects, echo messages to rooms, and manage dynamic world events.

Responsible for enforcing the Code of Conduct via 'mute', 'jail', or 'kick' commands; requires logging all disciplinary actions.

Oversees a specific department (e.g., Balance, Lore, or Building) and acts as the final arbiter for player appeals in that domain.

Focuses on the engine (C/C++/Python/LPC) rather than world content; manages hot-reloads and bug fixes in the live environment.

The highest tier with full root access to the server, codebase, and database; manages staff appointments and server costs.

Analytical role dedicated to reviewing equipment stats, mob difficulty curves, and class parity using automated log analysis.

Ensures all new area submissions, item names, and quest scripts adhere to the established world-building and narrative guidelines.

Configuring the MUD engine to log all immortal commands to a secure file or SQL table for audit by higher-ranking staff.

A standardized document mapping specific infractions (e.g., multi-playing, botting) to specific durations of mutes, freezes, or bans.

Rules governing when staff should be 'wizinvis' (invisible to players) to observe gameplay without causing 'staff-presence' behavior shifts.

Formal rules preventing staff from interacting with their own player-alt characters or favoring their previous player-clan members.

Strict criteria for when an Immortal can restore lost gear or XP, typically limited to verified server crashes or reproducible bugs.

A shared repository (Wiki or private forum) documenting policy changes and staff decisions to maintain consistency across time zones.

Guidelines on using 'imm-talk' for internal coordination vs. 'gossip/ooc' for public interaction to avoid leaking sensitive info.

Mandatory period where new Immortals must be 'snooped' or shadowed by a Senior staff member during their first 10 moderation actions.

Standard practice of capturing screen logs or database snapshots before issuing permanent bans for harassment or cheating.

Technical or social restriction preventing high-level staff from maintaining active player characters to ensure impartiality.

A centralized spreadsheet or database table assigning unique ID ranges to builders to prevent room/object overwrites.

A checklist for new areas: checking for 'dark' rooms without exits, mob pathfinding loops, and item weight/cost balance.

Using 'mprogs' or 'dg_scripts' debug modes to trace logical errors in mob interactions before the area goes live.

Technical requirements for room 'extra descriptions', consistent tense (usually present), and avoidance of 'you see' phrasing.

A mathematical formula (AC/HP/Hitroll) that builders must follow based on the intended level of the zone.

Integrating .are or .json zone files into a Git repository to allow for easy rollbacks and collaborative building.

Configuration of how often mobs respawn and items repopulate, ensuring zones don't feel empty or overly cluttered.

Strict definitions for flags like 'glow', 'hum', 'anti-evil', or 'nodrop' to prevent unintended item combinations.

A mandatory step where a second builder must 'walk through' a new area to find typos and logical inconsistencies.

Internal comments within scripts explaining what custom variables or global flags are being manipulated for future staff.

Rules for using world-wide messaging to ensure narrative flavor doesn't disrupt standard gameplay or spam players.

The 'switch' command usage for roleplaying as a boss mob during a quest to provide a dynamic, non-scripted challenge.

Using 'timer' or 'quest' flags on items to ensure they vanish after an event or cannot be traded to players who didn't participate.

Adjusting quest rewards on-the-fly based on the number of participants and their average level to prevent economy inflation.

Protocol for staff to follow immediately after a crash: checking logs, clearing corrupted pfiles, and announcing status.

A shared document where Quest Masters record changes to the world state (e.g., 'The King is currently dead') to inform future events.

Guidelines on when an Immortal should 'force' a player action or move a player for the sake of a narrative event.

Technical strategies for spreading quest mobs across multiple rooms to prevent 'room lag' when 50+ players congregate.

Using player-level flags (qbits) to track progress in long-running story arcs and prevent reward double-dipping.

Reviewing logs after a major event to identify which mechanics worked and which caused player frustration or technical lag.