Thanks a lot from me as well!Congratulations on the release, I already had the chance to see it, and I can assure everyone it is great.
Now a bug report, as there seems to be a regression regarding the buildRestrictionsUnits list, conditionMet refers to defaultBuildFunction which is not in scope. Replace lines 2177-2179 with this and it should work again:
Code:["romanCavalry"] = {unit=civ.getUnitType(72), conditionMet=function (city, state) return civ.hasImprovement(city, civ.getImprovement(18)) end} ,["scorpioArtillery"] = {unit=civ.getUnitType(70), conditionMet=function (city, state) return civ.hasImprovement(city, civ.getImprovement(17)) end} ,["onagerArtillery"] = {unit=civ.getUnitType(71), conditionMet=function (city, state) return civ.hasImprovement(city, civ.getImprovement(17)) end}
Just to be sure, that means if I want to set the condition such that it works like "default AND additional Condition", then I have to actually write the conditionMet such that it contains the default? Like "tribe.hasTechnology(unit.requirement) and civ.hasImprovement", we cannot access the default function directly?