On Actions

Implement Victoria 3 on_actions with reusable templates for triggers and events.

21|8|Updated Jun 23, 2025
One-click install
npx skills add https://github.com/mattia2110/tech-and-res --skill on-actions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: On Actions
Source: https://github.com/mattia2110/tech-and-res/tree/main/.agents/skills/_on_actions
Command: npx skills add https://github.com/mattia2110/tech-and-res --skill on-actions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a guide and template structure for implementing on_actions in Victoria 3, helping modders organize triggers, events, and cascading actions in a clear, reusable format.

Core Features & Use Cases

  • Structured templates for on_actions with triggers, weights, events, and fallbacks.
  • Clear coverage of on_action composition across common scopes (Country, Character, State) and script-triggered actions.
  • Modding best-practices to facilitate clean, maintainable additions to game logic.

Quick Start

Create a new on_action using the template and define its trigger, events, and optional on_actions.

Frequently Asked Questions about On Actions

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

FAQPage Schema
How do I define and manage on_actions in Victoria 3 modding?

You implement Victoria 3 on_actions by applying reusable templates that outline triggers, weight multipliers, events, and fallbacks. This structures cascading actions across country, character, and state scopes.

What are on_actions in Victoria 3 and when do I need them?

On_actions in Victoria 3 are scripting blocks that trigger events and cascading actions when specific game criteria are met. You need them to hook custom logic into country, character, or state scopes dynamically.

Can I use on_actions across different Victoria 3 scopes like country and state?

Yes, on_actions support common Victoria 3 scopes including Country, Character, and State. The templates provide structures to apply triggers and events correctly within these specific root scopes.

What is the best way to structure triggers and events for Victoria 3 mods?

The best way to structure triggers and events is using a reusable template format with defined triggers, weight multipliers, and fallbacks. This enforces modding best practices and maintains clean game logic.

How do I validate on_action scripts in Victoria 3?

Validate on_action scripts by following the provided workflow and best practices in the template structure. This ensures triggers, events, and YAML frontmatter metadata meet Victoria 3 modding requirements.