The nuts and bolts of Real City Naming while using Yet not Another Map Pack requires the use of two files: CityMap.xml and MapText.xml. Each entry in CityMap.xml assigns a unique XML-valid value to a tile or group of tiles. The MapText.xml file then contains entries that convert those values into text.


An example from my map CityMap.xml is:

• Area sets the radius of tiles affected. That is, zero (0) results in the name only applying to that specific tile; one (1) applies that name to that tile and the six surrounding tiles; and two (2) applies the name to the those seven tiles plus the next twelve outside the ring of six.
  
• MapName corresponds to, you guessed it, the map name, which I believe is set in your Config.xml file.
  
• CityLocaleName then is a unique name for that city. I kept the LOC_CITY_NAME type format. A key here is to only use standard alphanumerics -- i.e., no spaces, punctuation, special characters, accented characters, etc.
  
• X and Y correspond to the coordinates of the tile.

MapText.xml contains the corresponding CityLocaleNames and provides complete text for each entry.

• Tag is simply each unique CityLocaleName you used in CityMap.xml
  
• Text is the text you want displayed. You can see here that punctuation, accented characters, etc. are fair game.

To help keep all these straight, I recommend the use of a spreadsheet with columns for, at a minimum: X, Y, CityLocaleName, and Text. It'll make the XML development a breeze!

Then, to activate these updates, the ModInfo needs: