N/A

Dang, need to be quicker with the buzzer....

N/A

It seems that changing

<A_Traits>5.0000</A_Traits>

from 4 does the trick.

Edit:

<A_Traits>6.0000</A_Traits>

does not work at all. Looks like 5 is the upper limit.

Meow.

Edit 2:

Looks like it's hardcoded to 5.

N/A

You should be able to do that via a facion trait if you want, something like this in a faction trait ability should work I think...

<GameModifier>

  <ModType>Player</ModType>
  <Attribute>AbilityBonus</Attribute>
  <StrVal>A_Traits</StrVal>
  <Provides>Faction has one more traits that other factions.</Provides>
  <Value>1</Value>
</GameModifier>

One seems to work perfectly, right now I think the discussion is mostly centered around the upper limit.

Ok, will give it a shot and report back what I find.

Regarding adding the trait slot(s) as a race/faction ability: if it matters to you, having extra selectable trait slots will probably not be a very beneficial ability for the faction when controlled by AI.  Just look at how frequently the AI chooses the "base" unit designs without even using all three default slots.  

At the very least you'd need to pre-design units to make use of all the slots at various tech levels, and I don't remember anyone ever having tested whether or not the AI will choose designs with > 4 traits.  

For larger values of additional trait slots, it could potentially also cause problems on higher difficulty levels where the AI gets "bonus" traits for its units applied on top of the ones in the unit design.  Worth testing, anyway.

Odd situation:

<ImprovementType InternalName="Fort">
    <Prereq>
      <Type>RestrictedAbilityBonusOption</Type>
      <Attribute>GreatFortressTest</Attribute>
      <Target>Player</Target>
    </Prereq>
  </ImprovementType>

Although the faction has GreatFortressTest, it can still build Forts?

The problem lies with the fact that one never builds a fort. The city levels to a fort. So you prevent the city from leveling to a fort.

That is go to CoreAbilities.xml and add your prereq to 

<AbilityBonus InternalName="CityLevel_UnlockLevel2">

    <AbilityBonusOption InternalName="UnlockFortress">
        <Prereq>
            <Type>RestrictedAbilityBonusOption</Type>
            <Attribute>GreatFortressTest</Attribute>
            <Target>Player</Target>
        </Prereq>
    </AbilityBonusOption>

</AbilityBonus>

This should prevent the choice from being available on city level-up.

Nah it was building a fort as Primal said. Got it fixed last night.

Hypothetically, you could have the CityTrainingBonus apply an attribute which specified that a spell be cast at start of combat (similar to the "Noble Legacy" for Pariden.)  The spell could then check a condition and apply results based on the results of the check (boolean.)  Not sure if there are any testable conditions to see if a unit has an equipped ranged weapon, though.