Modbuddy made Civ text strings not read

SCubed

Chieftain
Joined
Apr 22, 2011
Messages
1
Hello all, I was following along the modder's guide adding a new civ to the game and have mixed results. A new civ is indeed added, but none of the text strings are decoded. For example instead of the Civilization name I get TXT_KEY_CIV5_SHORT_DESC and similar for the leader, and the cities.


At first i thought there was a typo in the OnModActivated action and there was so I corrected that and rebuilt the mod and then copied it over to the game dir /mods after removing the old one from the game.

Anyone have any suggestions on where to look next? Are there any logs somewhere that would reflect what happenned when a particular key was being referenced?
 
This sort of question goes in the general C&C forum, not the SDK one, but it's a simple answer:

You'll see that bug happen if there's any duplication of text keys. So one of your newly-added text keys is identical to one in the vanilla game, or a DLC you have, or another mod you're running. The most common culprit are city names, since several cities have been linked to different empires throughout history. Content mods also had this with things like the Granary or Hospital, where the devs added new Help keys, or the Aqueduct, where many of us had created a building with that name before the devs added an "official" one.

Before the March 1st patch, duplication like this in text keys wouldn't do any harm and you'd never notice. As of that patch, it now causes the entire file containing the duplicate entry to fail, which is why you're seeing none of your text keys (since mods are loaded after the vanilla game, DLC, and maps). So the easiest way to debug it is to start commenting out text keys until it works.

Bisecting the file is a useful way to do this: Comment out half the file. See if it works. If it does, then the error is in the half you commented, if it doesn't then there's at least one error in the part you DIDN'T comment. Reduce the amount of entries that are commented out and try again until you've narrowed it down to one or two keys causing the conflict.
 
Back
Top Bottom