sorry, I had no time last week to reply... there was a big festival in town...
ehm, yes, I remember I tried to merge the promotion tree and unit upgrade tree from a mod, where the buttons are connected by arrows like in the tech tree, but I was limited in programming skills for that. I gave up. ;(
Yes, I've finished PAE VI for alle MAC users and start to create a dll version. Python has its limits and first of all, I wanted to add big rivers with fresh water, moveable for small ships and moveable for land units on river fords.
then I've changed the BTS bug to only get the feature defense points on a certain terrain (eg swamp), instead of the terrain too. or I'd like that units that can't move into forests, can do with roads (eg chariots). at them moment (alternatively) chariots only have 50% stength penalty. bears should not leave forest plots, wild horses shouldn't move into forests and dense forests (only tamed ones)..... and so on....
But Sarmakand?

what do you think about it?
Oh, I thought BUG would be in SDK too...In fact, I already play a merged version of BUG + modified PAE
I certainly forgot things here and there. Probably more on the interface. In fact, I'd need a advanced save of PAE in order to compare
What do you mean about the SDK? You won't try to kkep compatibility with Mac? I meant just BUG, not necessarily BULL. But I have also (at least) some minor improvements about on the dll that wouldn't break the compatibility with Mac.
ehm, yes, I remember I tried to merge the promotion tree and unit upgrade tree from a mod, where the buttons are connected by arrows like in the tech tree, but I was limited in programming skills for that. I gave up. ;(
Yes, I've finished PAE VI for alle MAC users and start to create a dll version. Python has its limits and first of all, I wanted to add big rivers with fresh water, moveable for small ships and moveable for land units on river fords.
then I've changed the BTS bug to only get the feature defense points on a certain terrain (eg swamp), instead of the terrain too. or I'd like that units that can't move into forests, can do with roads (eg chariots). at them moment (alternatively) chariots only have 50% stength penalty. bears should not leave forest plots, wild horses shouldn't move into forests and dense forests (only tamed ones)..... and so on....
Ok, I can change this.TXT_KEY_CIV_MINOER_DESC
hm.. oh.... I did't see that this is taken into account in the pedia.... concerns only the concept pedia file. I'll change that, thx! Yes, it happens in the file generation of the online tool.In lots of concepts pedia entries, there are 3 tabulation at the beginning of each lines. You can see them in xml files but they're not present on your online tool. Is there a problem with file generation?![]()
Ok. Done.TXT_KEY_TERRAIN_OCEAN
Byzanz: ok.Could you do the same with byzantine civilization (Team 49 in xxxl 52 civs map)?
Edit: And Samarkand (Team 51)
Thx
But Sarmakand?
OKAgain in XXXL 52 civs map, you used the Jutes for the team 12. I think that a more ancient people, the Cimbri, should be used. BTW, the leader used, Boiorix, was king of the Cimbri.
Oh yes. I don't have the file in my working version anymore. But you're right, it's in the PAE VI version... damn.. I have to upload this again....I think the PAEGameText_Misc.xml file should be removed from XML/Misc. It is already present in XML/Text (its right location).
oh,... then it would be better to set bMilitaryHappiness to zero....Is it normal that Seer unit has:
?XML:<bMilitaryHappiness>1</bMilitaryHappiness>
It triggers a bug in PAE_City.doSupplyUnit.
First, the number of units that could suffer of starvation takes into account only "Military happiness" units.
Then a list of units that will suffer starvation is built. In this list, UNITCOMBAT_HEALER are excluded.
Problem: Seers are both "Military happiness" and UNITCOMBAT_HEALER so it may end in a bug depending on the whole number of units in the city.
When building the list (lUnitsAll), I think the code should be:
Python:if pLoopUnit.getUnitCombatType() != -1 and pLoopUnit.getOwner() == iPlayer: if pLoopUnit.getUnitType() == gc.getInfoTypeForString("UNIT_SUPPLY_WAGON"): iExtraSupply = PAE_Unit.getSupply(pLoopUnit) if iExtraSupply <= iMaintainUnits: iMaintainUnits -= iExtraSupply iExtraSupply = 0 else: iExtraSupply -= iMaintainUnits iMaintainUnits = 0 # set new supply tickets PAE_Unit.setSupply(pLoopUnit, iExtraSupply) elif pLoopUnit.isMilitaryHappiness(): lUnitsAll.append(pLoopUnit)
PS: I'm not sure Seers should have "Military happiness" in any case.
Ah... and here, it would be easier to just allow hunters only to build outlook posts? later on, there is no need to and people can do betterView attachment 699553
Finally I didn't do that for nothing. The TXT_KEY_BUILD_TURM key isn't used only by Hunters. If you write everything in this tag, you'll see the whole in place you don't want to (take a look at the Work Elephant in the pedia).

what do you think about it?