Dynamic Country Names

Define and apply Victoria 3 dynamic country names with YAML rules and triggers.

21|8|Updated Jun 23, 2025
One-click install
npx skills add https://github.com/mattia2110/tech-and-res --skill dynamic-country-names
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Dynamic Country Names
Source: https://github.com/mattia2110/tech-and-res/tree/main/.agents/skills/dynamic_country_names
Command: npx skills add https://github.com/mattia2110/tech-and-res --skill dynamic-country-names

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps modders manage and apply dynamic country naming rules for Victoria 3, reducing manual edits and ensuring consistency across tags, adjectives, and localization.

Core Features & Use Cases

  • Centralizes dynamic country name rules under a single structure.
  • Supports tag- and DEFAULT-based naming patterns, triggers, and prioritization.
  • Example use: define a country name for a tag with a country-specific trigger and a fallback.

Quick Start

Rename countries in your mod by adding dynamic_country_names patterns and a DEFAULT rule for general cases.

Frequently Asked Questions about Dynamic Country Names

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

FAQPage Schema
How do I define dynamic country names in Victoria 3?

Dynamic country names in Victoria 3 are defined by adding dynamic_country_name entries to a YAML file. This structure allows you to centralize rules, apply country-scope triggers, and set prioritization.

How does the DEFAULT rule work for Victoria 3 country names?

The DEFAULT rule provides a fallback for Victoria 3 country names when specific tag conditions are not met. It ensures a general name is applied, while specific tags can override it using prioritized triggers and is_main_tag_only settings.

Can I use triggers to change a country name dynamically in Victoria 3?

Yes, you can use deterministic country-scope triggers to change a country name dynamically in Victoria 3. These triggers evaluate tag conditions to apply specific naming patterns over the fallback DEFAULT.

What is the best way to manage localization for dynamic country names?

The best way to manage localization for dynamic country names is to centralize your tag-based rules within a YAML structure. This reduces manual edits and ensures consistency across tags, adjectives, and localization files.

Why are my dynamic country names not overriding the base tag in Victoria 3?

Dynamic country names might not override the base tag if the priority is set incorrectly or the country-scope trigger fails. Ensure your YAML structure includes the correct priority value and a valid deterministic trigger.

Do I need is_main_tag_only for dynamic country names in Victoria 3?

You need the is_main_tag_only parameter for dynamic country names when you want the naming rule to apply exclusively to the primary tag. This optional YAML field prevents secondary tags from inheriting the dynamic name.