y3-obj-edit

Edit Warcraft III Y3 Editor object JSON properties and persist changes.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/WindXRan/y3td --skill y3-obj-edit-windxran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: y3-obj-edit
Source: https://github.com/WindXRan/y3td/tree/main/maps/EntryMap/.y3maker/skills/y3-obj-edit
Command: npx skills add https://github.com/WindXRan/y3td --skill y3-obj-edit-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the trial-and-error of editing Warcraft Y3 Editor object (物编) JSON properties by giving a reliable, correct workflow for changing unit/ability/modifier/projectile attributes.

Core Features & Use Cases

  • Targeted property editing: Update existing object data for units, abilities, modifiers (Buff/Debuff), and projectiles via the editor_table JSON files.
  • Correct hotfix → wait → save sequencing: Prevents losing changes by enforcing the editor reload and persistence order.
  • Field-level guidance: Provides key property mappings (e.g., hp_max, ability_damage, modifier_type, effect_foes) and common tuple formatting rules for Y3 data structures.

Quick Start

Ask to modify the cooldown, cost, and sight_type of abilityall/100001001 in maps/EntryMap, then apply the required hotfix-object-editor and save steps to persist changes.

Frequently Asked Questions about y3-obj-edit

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

FAQPage Schema
How do I edit Y3 Editor object JSON properties for units and abilities?

To edit Y3 Editor object properties, locate the correct editor_table path by type and ID, modify the relevant JSON fields like hp_max or ability_damage, then execute hotfix_object_editor followed by save_editor to persist changes.

Why do my Warcraft III Y3 Editor changes not save after modifying object data?

Y3 Editor changes fail to save when the correct persistence sequence is skipped. You must execute hotfix_object_editor, wait for the editor to reload the updated JSON data, and then run save_editor to commit the changes.

What is the correct order to apply hotfix_object_editor and save_editor in Y3?

The correct Y3 hotfix-save flow requires executing hotfix_object_editor first, waiting for the editor to reload the modified object JSON, and then running save_editor to ensure the changes persist in the editor data.

Can I modify Buff and Debuff parameters in Y3 Editor JSON files?

Yes, you can modify Buff and Debuff parameters by editing the modifier object JSON fields like modifier_type and effect_foes in the editor_table, ensuring you follow the hotfix and save sequence to keep the schema valid.

How to update projectile visuals and stats in Y3 Editor?

Update projectile visuals and stats by locating the projectile editor_table JSON path by ID, modifying the relevant tuple formatted fields, and executing the hotfix_object_editor then save_editor flow to persist the object data.

What Y3 tuple formats do I need to know when editing game data JSON?

Y3 object data uses specific tuple formats for structured values. When editing JSON fields for stats or visuals in the editor_table, you must maintain these tuple formatting rules to keep the object schema valid during the hotfix process.