N/A

Interesting, you had some undead fixes which were designed to add graves instead of population?

Hmm fair enough.

Another comment: I noticed that the irregular map settings display a tooltip that says "String Not Found", so maybe a simple description could be added, similar to those for the non-irregular maps?

N/A

Neat trick! It occurs to me that if you made these available for sovereign creation (for zero cost) you could apply them to custom sovereigns in the in-game creator (for those less inclined to dive into the XML.)

As a minor side-effect, this would seem to have the side effect of giving a free trait at level 2?  Or is level 2 hard-coded to bypass trait selection?

Hrm...I don't see any way to enforce making sure players only choose a single item, but for preventing dual-classing, could you give the path traits an invalid PreReq\RestrictedAbilityBonusOption?  Or does the path selection screen respect that?  OTOH, I guess it might be problematic if they try it and get to a blank path selection screen too...

This might be too convoluted, but perhaps you could do something like spawn a quest, and have the quest reward depend on the answer to a question that determined which path to give out?  I have no idea how/if the AI handles quest branching, though, so you might end up back at random again...

</end random ramblings before coffee>

N/A

N/A

I disagree on there being no functional differences from an xml point of view but I do agree that snaking is snaking from the end-user point of view, which is probably all that matters for most users. That being said, If you are looking to simplify it even further, you can just remove the Category from "Category:Forest" and it will still work. IF my understanding of the matter is right:

• The first time you mention a PreferredTerrain w/o prefix it goes for TerrainType
• The second time you mention the same PreferredTerrain w/o prefix it goes for Category (e.g. This is the Pier in your xml)
• The third time you mention the same PreferredTerrain w/o prefix it goes for SuperCategory

Removing Category: from Category:Forest does work.

To some extent, yes (Forests, Rivers):

e.g.

<ImprovementType InternalName="NO_Snaking_R">
<DisplayName>NO_Snaking_R</DisplayName>
<Description>NO_Snaking_R</Description>
<RequiresCity>1</RequiresCity>
<PreferredTerrain>River</PreferredTerrain>
<LaborToBuild>1</LaborToBuild>
<ArtDef>Art_LoggingCamp</ArtDef>
</ImprovementType>

<ImprovementType InternalName="YES_Snaking_R">
<DisplayName>YES_Snaking_R</DisplayName>
<Description>YES_Snaking_R</Description>
<RequiresCity>1</RequiresCity>
<PreferredTerrain>River</PreferredTerrain>
<PreferredTerrain>River</PreferredTerrain>
<LaborToBuild>1</LaborToBuild>
<ArtDef>Art_LoggingCamp</ArtDef>
</ImprovementType>

<ImprovementType InternalName="NO_Snaking_F">
<DisplayName>NO_Snaking_F</DisplayName>
<Description>NO_Snaking_F</Description>
<RequiresCity>1</RequiresCity>
<PreferredTerrain>Forest</PreferredTerrain>
<LaborToBuild>1</LaborToBuild>
<ArtDef>Art_LoggingCamp</ArtDef>
</ImprovementType>

<ImprovementType InternalName="YES_Snaking_F">
<DisplayName>YES_Snaking_F</DisplayName>
<Description>YES_Snaking_F</Description>
<RequiresCity>1</RequiresCity>
<PreferredTerrain>Forest</PreferredTerrain>
<PreferredTerrain>Forest</PreferredTerrain>
<LaborToBuild>1</LaborToBuild>
<ArtDef>Art_LoggingCamp</ArtDef>
</ImprovementType>

N/A