dg-script-reference

Document DG Script trigger syntax and implementation patterns for TbaMUD environments.

7|1|Updated Mar 15, 2017
One-click install
npx skills add https://github.com/Henquewl/Hunter-X-Hunter-Greed-Island-MUD --skill dg-script-reference
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dg-script-reference
Source: https://github.com/Henquewl/Hunter-X-Hunter-Greed-Island-MUD/tree/main/.claude/skills/dg-script-reference
Command: npx skills add https://github.com/Henquewl/Hunter-X-Hunter-Greed-Island-MUD --skill dg-script-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves common development hurdles in TbaMUD DG Scripting, such as timing discrepancies, syntax pitfalls like the elseif parsing error, and the complexities of managing temporary player effects.

Core Features & Use Cases

  • Trigger Logic Optimization: Provides clear guidance on trigger type codes and the specific behavior of consume triggers (halt vs return 0).
  • Timed Effect Management: Offers a standardized pattern for attaching temporary effects to players using remote variables and timer triggers.
  • Use Case: When implementing a custom item effect that modifies player stats, use this reference to ensure the effect is correctly attached, timed, and reverted without causing permanent stat inflation or logic errors.

Quick Start

Use the dg-script-reference skill to debug your current trigger logic and verify the correct syntax for your conditional branches.

Frequently Asked Questions about dg-script-reference

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

FAQPage Schema
How do I create timed temporary player effects in TbaMUD without causing permanent stat inflation?

To create timed temporary player effects in TbaMUD, use remote variables to attach the effect to the player and utilize timer triggers to ensure the effect reverts correctly without causing permanent stat inflation or logic errors.

Why does my elseif parsing fail in DG Script triggers?

The elseif parsing error in DG Script triggers is a known syntax pitfall. You can resolve this by verifying your conditional branch syntax against established reference patterns to ensure proper logic execution.

What is the difference between halt and return 0 in a DG Script consume trigger?

In a DG Script consume trigger, halt and return 0 dictate specific trigger behaviors. Understanding these trigger type codes is essential for optimizing trigger logic and correctly managing the sequence of script execution.

How do I manage remote variables for mob, object, and room triggers in TbaMUD?

Managing remote variables for mob, object, and room triggers in TbaMUD involves utilizing the remote variable attachment pattern. This clarifies variable handling and ensures robust script development across different trigger types.

What are the syntax constraints and writable fields for DG Scripting in TbaMUD environments?

DG Scripting in TbaMUD environments involves specific syntax constraints and writable fields. Documenting these fields ensures robust script development by clarifying variable handling and timing discrepancies across trigger types.