-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dynamic country names #158
Comments
With Bahamanis, we already have a Deccan tag in EU4, so what happens if we have both an independent Deccan and a non-Islamic Bahamanis? |
No idea yet how to deal with such
|
A possible suggestion would be to also give dynamic names depending on the government system selected for the country (which could be just passed on from victoria 3 to hoi4 using the subsequent converter). I don't know what the policy on randomness is for these converters, but I would advocate for it, as it would contribute towards a more varied game world. Depending on a country's government type, there could be a list of templated names for the country and one of those could be selected randomly. Some grammar rules could be established as well to filter the odd-sounding choices, but alas I realize this might be too much of a luxury feature. |
Vic3 engine currently can handle dynamic name swaps depending on ruling party/goverment_type. However this issue is more general, and would rename countries from A (in EU4) to B (in vic3) under specific circumstances (government, culture, religion, etc). This issue needs both comprehensive rulesets as well as localization database. I'm leaving this issue open in case anyone has an idea what to do with this - and how. |
Dynamic names can be triggered by just about any trigger in Vic3. Primary culture and state religion are trivial, as are government form, and state ownership. Existence of other countries can also be checked (or flags set by such countries existing). |
See how to make use of this feature. List of EU4 countries that could make use of it:
The text was updated successfully, but these errors were encountered: