driver-overrides

Document FluffOS driver efun overrides and wrappers in Oxidus.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Document how Oxidus driver efun overrides modify FluffOS behavior and why these changes exist, helping developers avoid wrong assumptions about runtime semantics.

Core Features & Use Cases

  • Documents all overrides in override.c (exec, shutdown, set_privs, userp, query_num, ctime, element_of, debug_message) and their security, usability, and consistency implications.
  • Describes the wrappers this_body and this_caller that provide semantic alternatives to common efuns, along with usage guidelines and pitfalls.
  • Provides rationale and scenarios for when and why to apply or adjust these overrides in small to large mudlib projects.

Quick Start

Read this documentation before making changes to driver overrides to understand the expected behavior and safety constraints.

Frequently Asked Questions about driver-overrides

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

FAQPage Schema
How do FluffOS efun overrides modify runtime behavior in a mudlib?

FluffOS efun overrides intercept default efuns like exec and shutdown to enforce security, usability, and consistency constraints before execution. They modify standard behavior by applying privileged checks and semantic rules within the driver layer.

What are the this_body and this_caller wrappers used for in FluffOS?

The this_body and this_caller wrappers provide semantic alternatives to common efuns by clarifying object context. They help developers avoid ambiguity and runtime pitfalls when tracking the active player body or calling object interactions.

Why does the exec efun need a security override in FluffOS?

The exec efun override applies security constraints to prevent unauthorized body swapping or privilege escalation. By intercepting the default exec call, the driver layer ensures only privileged contexts execute sensitive connection transfers safely.

How do I document driver overrides for mudlib security and consistency?

Documenting driver overrides requires specifying the YAML name and description in frontmatter for discovery, then detailing the intent, constraints, and real-world impact of each modified efun to ensure developers understand safety considerations.

When should I adjust query_num or ctime overrides in a mudlib project?

You should adjust query_num or ctime overrides when runtime semantics require consistency changes across small to large mudlib projects. Changing these overrides impacts numerical and time formatting behavior throughout the driver environment.

Can I safely change set_privs and shutdown overrides without breaking driver security?

Changing set_privs and shutdown overrides requires reading their documentation first to understand safety constraints. These overrides directly manage privilege assignment and system termination, so adjusting them risks breaking driver security boundaries.