Mudlet checklist for MUDs

Ensure all variables and functions are stored within a single unique table (e.g., MyProjectName = MyProjectName or {}) to prevent overwriting other scripts.

Verify all triggers, aliases, scripts, and timers are nested under one parent folder named after the package.

Scan all scripts for 'for' and 'while' loops to ensure iterators are explicitly declared as 'local' to avoid global scope pollution.

Use registerAnonymousEventHandler for script-side event binding rather than relying solely on the UI event box to ensure portability.

Check that large codebases are split into logical script objects within the Mudlet editor rather than one giant file.

Use '^' and '$' anchors in Perl Regex triggers where possible to prevent unnecessary mid-line scanning.

Convert static text triggers from 'perl regex' to 'substring' or 'begin of line' to reduce CPU overhead.

Implement disableTrigger() and enableTrigger() for combat-specific patterns so they only run when relevant.

Ensure triggers do not rely on specific ANSI colors unless necessary, as user themes or MUD settings may change them.

Use the 'multiline' trigger type with a line delta of 0 or 1 for complex patterns to ensure they only fire on specific sequence blocks.

Verify the script checks for the existence of the 'gmcp' table before attempting to access nested data like 'gmcp.Char.Vitals'.

Ensure UI updates only trigger when GMCP values actually change, rather than on every incoming GMCP packet.

Provide basic prompt-parsing triggers for users playing on MUDs that do not support GMCP or MSDP.

Wrap custom yajl.to_value calls in pcall() to prevent script crashes if the server sends malformed JSON.

Verify gmcp.Room.Info data correctly updates the Mudlet mapper ID via centerview() or setPlayerLocation().

Confirm all UI elements (labels, gauges, consoles) use the Geyser or Vyzor libraries for automatic resolution scaling.

Check that all UI elements are attached to a Geyser.Container to allow for easy bulk hiding/showing.

Test UI readability at different font sizes (e.g., 10pt vs 16pt) to ensure text does not clip out of labels.

Ensure the script calls setBorderRight() or setBorderBottom() so UI elements do not overlap the main game text.

Test UI visibility against both the default Mudlet dark theme and a high-contrast light theme.

Store IDs returned by tempTimer() in a table and kill them before starting new ones to prevent timer accumulation.

Avoid creating large temporary tables inside high-frequency triggers (like the prompt).

Use createStopwatch() and getStopwatchTime() to measure execution time of heavy functions during testing.

Use getMudletHomeDir() for all file operations to ensure paths work across Windows, Linux, and macOS.

Confirm all images used in labels are included in the .mpackage and referenced via relative paths.

Install the package on a completely fresh Mudlet profile to identify missing dependencies or variables.

Include a MyPackage.version string to allow for easy troubleshooting and update checks.

Create a 'help' alias (e.g., 'pkg help') that displays a list of commands and current configuration status.

Ensure no aliases use extremely common short names (e.g., 's', 'k', 'c') without a toggle or specific prefix.

Provide a function or script that cleans up UI elements and global tables when the package is uninstalled.