room-creation

Automate Oxidus Mudlib room creation with function-based APIs and layered inheritance.

8|3|Updated Sep 29, 2021
One-click install
npx skills add https://github.com/gesslar/oxidus-mudlib --skill room-creation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: room-creation
Source: https://github.com/gesslar/oxidus-mudlib/tree/main/.claude/skills/room-creation
Command: npx skills add https://github.com/gesslar/oxidus-mudlib --skill room-creation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Room Creation Skill streamlines building consistent, feature-rich rooms for Oxidus by outlining a clear setup chain, inheritance patterns, and metadata conventions.

Core Features & Use Cases

  • Establish area bases and room layers with a predictable setup order.
  • Configure exits, items, terrain, zones, and monster spawning using a clean API.
  • Apply consistent room metadata for maps, lighting, and GMCP data across the mud.

Quick Start

Define a new room by setting its short and long descriptions, wiring exits, adding items, and configuring metadata with the standard room base.

Frequently Asked Questions about room-creation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create rooms in Oxidus Mudlib with consistent terrain and exits?

Oxidus Mudlib room creation utilizes a function-based API—such as set_long, set_exits, add_item, and add_door—to configure room elements. This enforces a standardized setup order and layered inheritance for defining terrain, exits, and items.

What is the correct setup order for area bases and room layers when building Oxidus rooms?

The correct setup order for Oxidus rooms involves establishing area bases first, then applying individual room layers. This layered inheritance pattern ensures consistent metadata for maps, lighting, and GMCP data, while wiring exits and adding items systematically.

Can I configure doors and monster spawning using the standard Oxidus room API?

Yes, you can configure doors and monster spawning using the Oxidus room API. The function-based API includes add_door and supports monster spawning configurations, allowing you to add these features while maintaining consistent room metadata and layered inheritance.

How does layered inheritance work when defining room metadata in Oxidus?

Layered inheritance in Oxidus works by establishing a shared area base that defines common room metadata, such as lighting and GMCP data. Individual rooms then inherit this base, ensuring consistent definitions while allowing specific overrides for exits, terrain, and items.

Does Oxidus room creation support configuration for map and GMCP metadata?

Yes, Oxidus room creation supports configuring map and GMCP metadata. By applying consistent room metadata conventions across the mud through the layered area base, you ensure that lighting, map, and GMCP data are uniformly applied to all inherited rooms.