You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Such a feature does not seem supported yet in-game, but we may override the locs of the hub names.
A configurable would be used as such: link = { state = STATE_ISTRIA homeland = croatian city = "Trst" mine = "Željezograd" farm = "Opatija" wood = "Šuma" port = "Pula" }
In this case, if Istria is a homeland state for the Croatian ethnicity, the hub names are thus overwritten.
The first matching rule would be applied. All fields except for state and homeland are optional. If such fields are missing, no output is produced.
The overriding would be output in /localization/[language]/hub_names_l_[language].yml (for each language), with this syntax: HUB_NAME_[State key]_[Field key]:1 "[String]"
As an example, HUB_NAME_STATE_ISTRIA_CITY:1 "Trst".
It'd be best to eventually move to nested locs for this configurable, so that dynamic names are correctly translated.
The text was updated successfully, but these errors were encountered:
Eu4 more often than not provides province names, not city names, along with their respective dynamic names according to owner culture. Also due to map deformation, we can't guarantee the city in eu4 maps to the city in Vic3, making crossmapping from EU4 difficult.
I'll leave this issue open but I don't see a trivial way to rename base hubs using eu4 sources. Also, as noted, any rename would be permanent as there is no dynamic rename system in Vic3 yet.
Such a feature does not seem supported yet in-game, but we may override the locs of the hub names.
A configurable would be used as such:
link = { state = STATE_ISTRIA homeland = croatian city = "Trst" mine = "Željezograd" farm = "Opatija" wood = "Šuma" port = "Pula" }
In this case, if Istria is a homeland state for the Croatian ethnicity, the hub names are thus overwritten.
The first matching rule would be applied. All fields except for state and homeland are optional. If such fields are missing, no output is produced.
The overriding would be output in
/localization/[language]/hub_names_l_[language].yml
(for each language), with this syntax:HUB_NAME_[State key]_[Field key]:1 "[String]"
As an example,
HUB_NAME_STATE_ISTRIA_CITY:1 "Trst"
.It'd be best to eventually move to nested locs for this configurable, so that dynamic names are correctly translated.
The text was updated successfully, but these errors were encountered: