100 MOO resources for MUD players

The current standard for high-performance MOO servers. It provides 64-bit support, improved networking, and built-in SQLite integration.

The classic server source code. While dated, it serves as the baseline for understanding the MOO VM and bytecode execution.

An intermediate fork that introduced many of the features now found in ToastStunt, useful for legacy compatibility with older databases.

Containerized deployment configurations for running MOO servers on modern cloud infrastructure like AWS or DigitalOcean.

A patch for ToastStunt that allows native parsing and generation of JSON, enabling API integrations with external web services.

Implementation details for using the ToastStunt SQLite built-in functions to handle large datasets outside the standard object hierarchy.

Lightweight objects that do not consume object numbers. Essential for high-density data structures like inventory items or map tiles.

Instructions for implementing secure connections via OpenSSL within the server layer to protect user credentials.

Documentation on using binary strings to handle non-textual data, necessary for custom protocol implementations.

Configuration of the server's task limits to prevent infinite loops from crashing the driver during verb execution.

The foundational database containing the absolute minimum objects (#0 through #90) required to boot a functional MOO environment.

A more feature-rich core that includes advanced building tools, a robust mail system, and improved security defaults.

Specifically designed for virtual classrooms, featuring web-interface hooks and collaborative editing tools.

The definitive guide to the MOO language syntax, built-in functions, and the standard object hierarchy.

The root of the MOO hierarchy; understanding its 'do_login_command' and 'do_command' verbs is critical for server security.

The parent object for all spatial locations. Learn to extend its 'announce' and 'look_self' verbs for custom environments.

The template for all user accounts. Customizing the 'tell' verb is necessary for implementing custom UI or logging.

A design pattern for adding commands to players without polluting the inheritance tree, using the 'features' property.

Techniques for exporting specific object trees and verbs into text files for version control or migration between servers.

Implementation of the $quota_utils object to restrict the number of objects and bytes a user can create.

A protocol for structured communication between the MOO and clients like Mudlet, allowing for GUI elements and file transfers.

Pre-configured Lua scripts for Mudlet that handle MOO-specific ANSI sequences and local editing prompts.

Configuring the MOO to send verb code to a local text editor (VS Code/Vim) via the client rather than using the in-game editor.

Vim configuration files providing syntax highlighting for the .moo file format and verb code blocks.

Critical syntax for managing non-blocking operations and background tasks in the MOO's single-threaded environment.

The architectural distinction between executable code (verbs) and data storage (properties) and when to use each.

Understanding the 'caller', 'player', and 'this' variables to prevent unauthorized verb execution and data leaks.

Core objects for handling outbound connections to HTTP servers or other MOOs using 'open_network_connection'.

Techniques for wrapping standard functions like 'move()' or 'create()' with custom logic at the database level.

Monitoring 'ticks_left()' and 'seconds_left()' to optimize complex algorithms and avoid 'Task ran out of ticks' errors.