@thedog right on so sea transport won't work on 99 plus ? I guess I gotta do some math for the Land and Air boys then : ) Thanks

@rogercooper As "movementCostModifier" is part of territoryEffectAttachment is is very limited to what else you can do. However if each unit type has its nationality/faction built into the unit like "infantry-usa" or "roman-infantry" then you can target who gets the benefit or not. I think that might be as good as is gets.

I'd like this feature as well. It could work great to mimic Brest-Litovsk agreement more realistically without using triggers or Communists. For example CP occupies all these territories but unables to advance more deeper while Russia (Whatever tsarist, democratic or communist) can retake these teritories if CP doesn't defent them properly. So CP will need to tie significant forces to keep these territories.

@rogercooper said in great accurate resource for map making!: 40480105 Thank you Spy!

@pact_of_plastic yea just when it tells you theres a new one. Idk. i guess it doesn't really matter. So you're on the 2.5 stable ? Edit just saw your other post so yea 2.5.

@beelee ++Good! It works, thanks

@wc_sumpton ++Good That looks so much better! Thanks for the quick reply.

@General_Zod I was surprised also by the absent of a line number in the error. Also notepad++ did not find the error until I checked for Artillery " (note the space before the ending quote). Checking for Artillery (note no quote sign after the space) did not find the error. Mostly it was luck when I found it. :astonished_face: Cheers...

@beelee Should be possible. Try placing a construction with isSea attributes and also give it production attributes. But confirm that your current settings allow for construction placement without factory otherwise will need to build next to a factory. Heres a few to check and or use. refer to POS2.xml for complete lists canProduceUnits values: allows a unit to be a factory, without all the other things that come with being a factory (like capturable, land, non-combat, etc). So if you want flying factories, go ahead. Just don't complain if you get errors. isConstruction values: allows the unit to be placed in territories that don't contain factories. Only "constructionsPerTerrPerTypePerTurn" contructions of "constructionType" may be placed per territory per turn. May have only "maxConstructionsPerTypePerTerr" constructions Total per territory with/without a factory unless you enable "More Constructions with/without Factory", which will allow up a total number of up to the territory value. "Unlimited Constructions" game property allows unlimited constructions total in a territory. constructionType values: is just a unique string which identifies what kind of construction this, if two or more constructions have the exact same constructionType (and the same PerType rules), then they will follow the same rules for placement. example: if you have little_bunker and big_bunker both as type "bunker", with constructionsPerTerrPerTypePerTurn=2, then you could place 2 littles, or 2 bigs, or 1 little and 1 big in a territory If you do not want this unit to be effected by the global properties "More Constructions with/without Factory" and "Unlimited Constructions", then make sure the type ends in "structure". example: "harbour_structure" constructionsPerTerrPerTypePerTurn values: is how many of this type you can place in a territory every turn maxConstructionsPerTypePerTerr values: is how many max of this type may be in a territory. this must be greater than constructionsPerTerrPerTypePerTurn if "More Constructions with/without Factory" = true, then the minimum will be either maxConstructionsPerTypePerTerr or the PU value of the territory (whichever number is greater) in territories with/without factories if "Unlimited Constructions" = true, then this number becomes 10000 Also @wc_sumpton is correct the sezone may need production values.

@butterw A quick thought, the unit count for human players could be; Traffic lighted, eg. Green(low numbers), Amber(medium numbers), Red(high numbers) Ideally the above bandings would not be fixed, but would be dynamic, based on the largest stack on the current map for the current turn, although this might not be possible. If it was fixed then some maps with low unit count might never get to the higher banding. Whatever you decide, put me down for giving feedback.

in ww2 air units couldn't effectively be stopped by naval units and torpedo/dive bombers did have the ability to directly target capital ships.

@ebbe i like it

@beelee I downloaded the Windows version of Pinta and it worked with a few clicks, impressive. It coped easily with the resizing of the image and the opacity of the blockade.png.

@butterw Sweet ! I forgot all about that Yea, we'll be a half dozen or so over by the time it's all said and done. Thanks for the heads up

Was trying to add defence and offence in same attachment. Works now. Thanks

@hepps heh heh LCVs are going roundel free Thanks again man

@wc_sumpton oh not having 4 conditions was definitely help :grinning_face_with_smiling_eyes:

@Schulz I think I understand what you are saying. You do not need to "turn off" '<stepProperty name="resetUnitStateAtStart" value="true"/>'. All this does is reset/clear Unit states, which is also done at the end of Non-Combat Movement by default. The only change to game play will only appear when units are spawned, this will allow then to move during the same turn that they appear. If the units do not spawn, that's ok, there should be no effect. '<stepProperty name="resetUnitStateAtStart" ' value can not be changed with triggers. But from what I understand by what you are describing that should be okay. Cheers...