Orders

Name: Orders
Availability: InStock
Author: mattia2110

Create and validate Victoria 3 commander order files against vanilla references.

21|8|Updated Jun 23, 2025

Search Tags:#guidelines #modding #orders #victoria-3 #commander-orders #vanilla-references

Ready to run

npx skills add https://github.com/mattia2110/tech-and-res --skill orders

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Orders
Source: https://github.com/mattia2110/tech-and-res/tree/main/.agents/skills/orders
Command: npx skills add https://github.com/mattia2110/tech-and-res --skill orders

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides the creation, editing, and review of Victoria 3 commander order files, ensuring consistency with vanilla references and correct modifiers.

Core Features & Use Cases

Inspect vanilla orders to understand intended behavior before creating a new one.
Decide whether a task results in a new order, a trait-specific variant, or a vanilla override.
Ensure UI visibility gates (visible/possible), correct modifiers, and asset references; verify icon, animation, sound, and localization paths.
Keep related orders within the same behavior family for consistency.

Quick Start

Create or update an order in common/commander_orders/*.txt by following vanilla patterns.

Frequently Asked Questions about Orders

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

FAQPage Schema

How do I create custom Victoria 3 commander orders that match vanilla behavior?▼

To create Victoria 3 commander orders, define files in common/commander_orders by following vanilla patterns for military_type, behavior, and modifiers. This ensures custom orders align with vanilla references and maintain consistent behavior and UI visibility gates.

What fields need to be validated when modding Victoria 3 commander orders?▼

Validating Victoria 3 commander orders requires checking fields like texture, military_type, behavior, visible, possible, modifier, entity_animation, and ai_weight. Correct validation ensures assets and icon paths are properly referenced without breaking game stability.

When should I override a vanilla commander order instead of creating a new one?▼

Overriding a vanilla commander order is appropriate when modifying existing behavior, while creating a new order suits distinct mechanics. Analyze vanilla files to decide whether a task results in a new order, a trait-specific variant, or a vanilla override.

Why are my custom Victoria 3 commander orders not showing up in the UI?▼

Custom Victoria 3 commander orders may not appear due to incorrect visible or possible gates, or missing asset references. Verify that UI visibility conditions, icon paths, and localization entries match vanilla patterns to resolve display issues.

How do I inspect vanilla Victoria 3 commander orders to understand their intended behavior?▼

Inspect vanilla Victoria 3 commander orders by examining files in common/commander_orders to understand their structure. Reviewing these vanilla references clarifies how behavior, modifiers, and ai_weight function before creating custom or variant orders.

Does this approach work for adding trait-specific commander order variants in Victoria 3?▼

Yes, this approach supports adding trait-specific commander order variants in Victoria 3. By keeping related orders within the same behavior family, you ensure trait-specific variants maintain consistent behavior, modifiers, and localization alongside vanilla references.