Soooo... i looked into the item (dust talisman) who regenerate, and how the regeneration works in fight :

[CODE]









($Property(ClassUnit:CantBeDebuffed) le 0) and ($Property(ClassUnit:Health) lt $Property(ClassUnit:MaximumHealth))





[/CODE]

As we can see, the targetProperty affected IS well and truly Health.

So :

[CODE] [/CODE]

Should works. But no.





[CODE] [/CODE]

Works , my units dont regenerate in Winter... but all my units, everywhere :s



So... i really need to know how to Path, because [CODE]Path="ClassUnit,#Winter"[/CODE] was not a good path.

Thus i'm guessing that some targetproperty affects only some classes/path, or my Path was wrong, and that's all V_V

yeah yeah negative regen have been done, look at the Frostbite Trait Mod.

Isn't it enough to give negative value to regen ?

So we cant use the "start of the round" as "start of the turn" or make winter do some battleaction ?

As the Health is a "proportion" of the maximum health, you will increase a little the health... but yes, you are right it's not the same.



In a battle, you can use some "Direct health change" because the BattleAction allow this kind of stuff. It's build to be able to change the simulation based on action (hit, start of the round, etc).

But in the simulation, it's more a description of the things regardless of the moment of the time...



Don't know if that helps...

ok...

But IMHO (as a player), i have seen games where units can have a health buff like 53/40. It is not the same buff as 40/53.

Because if we fight, and we receive a 40 damage, in the first case we still live with 13/40hp, the second case, we are dead, with 0/53.

About the regen in those case, the 53/40 unit will stay at 53/40, and the 40/53 will progressivly up to 53/53.



Anyway, ok, i'll not try to mess with the Health directly.

The health is automatically sealed due to be a SimulationProportionalPropertyDescriptor...



So no, you should never ever touch the health property directly. otherwise you will be able to have more health than the maximal health...



There is no one shot instruction in the simulation. Like, loose 10 hp now.

Another things good to know is the sealed properties.

You will find them sometimes. They are used to define a property which is not modifiable by modifier and simulation. They are used when we need to store a value computed in the code. Like the health of a unit for example.

If you want to modify the Health of a unit you have to modify the MaximumHealth or the unit regen. but you should never try to modify directly the health.

The Health don't seem to be sealed, but can we just add ? :

[CODE]IsSealed="false"/>[/CODE]

I know that our simulation is pretty hard to handle and even more when you have no tools to display it... but yeah, we are able to do a lots of stuff with it ^^

I will try to keep giving you input when I see something wrong or when you are totally lost... I just have a lot of work and cannot answer all your question... but I will read them and try, with Pikou to give you answer as much as possible...



Head up guys, your are tearing our game apart to make it even better and we love that!

Keep up the good work and we will try to support you as much as possible.

Thanks you for your time and your support

One thing to know is:

The path depend on where you are starting in the hierarchy.



If you start on the empire (like it is for the faction traits) and you want to modify a property in all the unit of all the armies of your empire, you have to write this path:

ClassEmpire/ClassArmy/ClassUnit



If you are modifying a unit ability which is applied directly on a unit and you want to modify a property in the corresponding unit your path will be:

ClassUnit or nothing.



if you are modifying a unit ability which will modify a property on all units alongside it and this in a city or an army then you will need:

../Garrison/ClassUnit



(../ will try you then your parent and the parent of the parent and ... until it find the next tag which is "Garrison" in the example. So if you are starting on a unit in an army, the path will ask the unit if it has the "Garrison" tag which is not the case, then ask the parent of the unit. The parent is the army and an army has the tag "Garrison" so the path will say "ok, I can continue the search from the army".

It will then try to find the tag "ClassUnit" in all the army children.)



Another things good to know is the sealed properties.

You will find them sometimes. They are used to define a property which is not modifiable by modifier and simulation. They are used when we need to store a value computed in the code. Like the health of a unit for example.

If you want to modify the Health of a unit you have to modify the MaximumHealth or the unit regen. but you should never try to modify directly the health.



I know that our simulation is pretty hard to handle and even more when you have no tools to display it... but yeah, we are able to do a lots of stuff with it ^^

I will try to keep giving you input when I see something wrong or when you are totally lost... I just have a lot of work and cannot answer all your question... but I will read them and try, with Pikou to give you answer as much as possible...



Head up guys, your are tearing our game apart to make it even better and we love that!

Keep up the good work and we will try to support you as much as possible.

The short version is:

SimulationDescriptors are built from SimulationProperties and SimulationModifiers

SimulationDescriptors include Classes that are related by a hierarchy, including ClassEmpire.EmpireTypeMajor/ClassArmy.ClassCity.Garrison/ClassUnit

SimulationModifierDescriptors (anywhere) point to TargetProperty and Path

Path points to the SimulationDescriptor that contains those SimulationProperties that are the subject of TargetProperties



You can think of it as analogous to a folder structure. You have a bunch of folders (SimulationDescriptor is the folder, Path is the folder path) and within the folder you have a bunch of files you need to access (SimulationPropertyDescriptor is the file, TargetProperty is the filename). Then you have software that accesses and edit those files (SimulationModifierDescriptor is the software). So you need to look through all of the folders, and see what files are in them, to see what you will be able to change or work with; then keep track of their paths and filenames which you will need to input into the software.



In more detail, with examples:

There are a number of things you have to look at:



First, SimulationDescriptors[Class].xml

has the following classes (these are SimulationDescriptor of Type "Class"):

ClassArmy

ClassBattleUnit

ClassCity

ClassConstruction

ClassDistrict

ClassEmpire

ClassEmpirePlan

ClassImprovement

ClassMinorEmpireGarrison

ClassPointOfInterest

ClassResearch

ClassTimedBonus (Type "ClassTimed")

ClassTradeRoute

ClassUnit

ClassItem

MainCity (Type "SubClass")



Now, they are all related with a hierarchy, too. Something like

ClassEmpire

> ClassCity

> > ClassDistrict

> > ClassUnit

> ClassArmy

> > ClassUnit

etc.



Notice that you can have both ClassArmy and ClassCity as the parent to ClassUnit? Yeah. Confusing. But my theory is that ClassArmy/ClassUnit corresponds to field units, and ClassCity/ClassUnit corresponds to garrisoned units.



Now, for each of those Classes, there are SimulationPropertyDescriptors. For example:

[code]

















[/code]

For any object that is of ClassArmy, there are a whole bunch of properties such a MilitaryUpkeep. Now, ClassArmy are the stacked units that you move around on the map.



These are the properties that you modify when you use a tag. If you want to modify MilitaryUpkeep on an army, you have to point the path to ClassArmy.



But ClassArmy is below ClassEmpire, and ClassEmpire has its own properties, such as ArmyUnitSlot, CityUnitSlot, EmpireUpkeep and so on. ClassEmpire, obviously, is your empire. But for some reason, there are only a handful of properties.



And below ClassArmy there is ClassUnit. ClassUnit are the units that you make armies with, and garrison cities with. Now, ClassUnit has A LOT of properties. Many of those are shared by ClassArmy, such as VisionRange (Army VisionRange = best unit's VisionRange), MaximumMovement (Army MaximumMovement = worst unit's MaximumMovement), MilitaryUpkeep (army upkeep = 4 + sum of unit upkeep); but there are other unit-specific properties, such as Experience, Attributes, and UnitRegen.



To further complicate matters, there is an oft-used "Garrison" class, I believe it's defined in: SimulationDescriptors[Garrison].xml; and for some reason, it appears to be assigned to all units, as you will find "Garrison" in the path of many different SimulationModifiers. There are only a few properties, and they don't appear to be relevant to this discussion.



Then there's EmpireTypeMajor (and EmpireTypeMinor) which you will find defined in SimulationDescriptors[EmpireType].xml: This is where all of the empire's properties generally sit, including "GlobalUnitRegenImprovement".



To really complicate matters, if you're only going to be modifying a property of ClassUnit (the lowest in the hierarchy), do you really need to point to the upper two hierarchy levels? I'm not sure. And if so, do you pick ClassEmpire or EmpireTypeMajor? Do you pick ClassCity or ClassArmy or Garrison? Will it matter? What about faction traits? They are never seen alongside ClassEmpire, and always seen alongside EmpireTypeMajor. Why is that? Is there a significance or is it really just a preference?



On that note, it's worth mentioning the extra options (as if it wasn't complex enough):

You can use "#Summer" or "#Winter" in the path to only apply the modifier during those seasons (but I'm not sure where these are defined). You can also exclude SimulationDescriptors from the search by using an exclamation mark (!) prior, e.g. "EmpireTypeMajor/Garrison,!Militia,ClassUnit". You can also include or exclude FactionTraits or Affinities in the path.

Hi



I'm trying to create a new trait. "Cold blood". In winter, units cant move and lose health.

I followed the tutorial modding pdf step by step.



1) My NewTrait.xml

[CODE]











Nomis





Aquatique : Obligation de construire près d'une rivière ou d'un lac.

Sang froid : Les unités en dehors des villes durant l'hiver perdront progressivement des points de vie et ne peuvent pas bouger.





















Gui/GuiElements

.xml









Simulation/FactionTraits.xml

Simulation/FactionTraits

.xml







Simulation/SimulationDescriptors.xml

Simulation/SimulationDescriptors

.xml









Localization

[/CODE]



2) gui element faction trait :

[CODE]











Les unités en dehors des villes durant l'hiver perdront progressivement des points de vie et ne peuvent pas bouger.







[/CODE]

It is not a problem if my title is "Sang-froid" instead of "SangFroid", right ?



3) Faction trait custom

Code:



































4) And the last but not the least, the simulation descriptor (and i think it's why my mod crash ^^" :

[CODE]























































[/CODE]



As u can see, i didnt worked on the Aquatic trait (not yet ), and i have "commented" the regen part of the Cold blood trait. I just want to work on the movment.

And i'm pretty sure that's the line who is faultive.

Code:



a)TargetProperty : is it the right property to affect the movment? (seems to be a silly question but... i want to be sure ^^' I guess yes... didnt see any other movment stuff in the simulation descriptors :

Code:



b) Operation : Can i use percent? where can i see if i can ? What's the Composition="Minimum" mean in the simulation descriptor?

c) Value : Can i use a negative %? like that? or just "-100" ?

d)Path : I didn't really understood how "to designate the target".

Seems to be easier to only work with ".../" ?

Where can i find all the Class ? all the classes are here ? :

EmpireTypeMajor (ou plus simplement ClassEmpire) <= some french words in the tutorial

>ClassCity

>ClassDistrict

>ClassPointOfInterest

>ClassArmy

>ClassUnit

>ClassEmpirePlan



#Winter ? didnt see any reference in the pdf, i guess that's a sort of trigger who affect the unit only in winter ?







PS : Should i create one unique trait per mod or can i create multiple traits per mod ?

I don't know the difference between a SimulationModifierDescriptor and a BinarySimulationModifierDescriptor though.



If you scroll up to the top of each SimulationDescriptor, you'll see the reason there's two instances of line 91/268:

One is for "EmpireTypeMajor" (major faction, e.g. Broken Lords), the other is for "EmpireTypeMinor" (minor faction, e.g. Ceratan)

EmpireTypeMinor have less variables to deal with (no heroes for example).



Also, I replied to the Winter Mechanics thread you posted in, with three possible solutions. I haven't had the opportunity to test them. If you could, let me know how it goes.

Yeaah... easier to say than done

Tried all of this :

[CODE]



























[/CODE]



And none of this worked.



I begin to think that i maybe have to understand how units inflicts damage to other units, and maybe doing "winter inflicts damage to unit" instead.

I have to check how the item who give regen works too...



And i dont see where it's written that units regen 5%....

Edit : hahaha... i ctrl+f "0.05" and finally found it in the simulation descriptors [empiretype] :

[CODE] [/CODE]

line 91 & 268 (dunno why there is two "instances" of that")

and i totally forgot about the necrophages skill (and sisters of mercy does the same) :

[CODE]







[/CODE]



Sooo now i have finally the right TargetProperty





@Pikou : in the pdf, could you explain the difference between Operiation et BinaryOperation ? Like :

[CODE] [/CODE]



EDIT : Ho thanks Tigregalis, i understand it a little bit more now ^^

Well, the first example checks two properties of an empire related to Luxury1, takes the difference, and tests if that difference is equal to zero. I'm not particularly sure why. "MaximumLuxury1Count" and "NetLuxury1" are no longer SimulationPropertyDescriptors of the SimulationDescriptor "ClassEmpire" defined in SimulationDescriptors[Class].xml; through looking at ResourceDefinitions.xml, it looks like there used to be a monopoly bonus for Luxury1 but that effect has since been deprecated, so the example might have been an old version of that bonus.



The second example does this

1.

new NetDust = NetDust + ($(RawDust)-$(DustUpkeep))

but if I'm not wrong, NetDust is initially zero, so it's really:

NetDust = $(RawDust)-$(DustUpkeep)

In simple terms, it's the calculation of dust profit (NetDust), from dust income (RawDust) and dust expenditure (DustUpkeep)



and

2.

new Offense = Offense * (1 + $(Morale)*0.1)

In other words, it adds X% to offense, because of morale, based on the formula X = Morale * 0.1

So if Morale is, say, 5, then Offense is multiplied by 150% because: new Offense = Offense * (1 + 5*0.1) = Offense * (1 + 0.5) = Offense * 1.5



Modifiers are quite simple once you understand them (tedious though):



Imagine we want to do this

new X = X * A

we would write

X" Operation="Multiplication" Value="A">



But let's say we want to do this instead

new X = X ^ (A - B)

we would write

X" Operation="Power" Left="A" BinaryOperation="Subtraction" Right="B">

I would give a negative value to regen.

Thanks for the answers

I dont hesitate i think i maybe havent read each .xml once, but i read some .xml more than 6 or 7 times (simulation folder i hate u )



About the modding tutorial pdf, thanks a lot for doing this Pikou, it's really useful.

I think an exhaustive list of the TargetProperty and the Classes could be a great addition to the modding tutorial pdf.

Also, there are some example in this pdf, but i dont understand them

By example p.45 :



[CODE]Examples:

($Property(ClassEmpire:MaximumLuxury1Count) - $Property(ClassEmpire:NetLuxury1)) eq 0[/CODE]



or



[CODE] [/CODE]



Well... it could be useful to "shell" (décortiquer in french) the example, and tell what is doing what. Translate it in human words / make commonplace.



@VieuxChat thanks for the tip about the morale



---



I'm now at my second step of my trait, the anti-regen while winter.

I tried a lot of things :

/#/endless-legend/forum/5-general/thread/1948-winter-mechanics

I can modify MaximumHealth, but not the (current) Health...

And even if in my trait it shows something like "-50% health regen on unit while winter" it does nothing.

What targetproperty should i use ? There are so many :/ Health? HealthRegen ? OwnedUnitRegenModifier ? UnitRegen ? RegenerationBonus ?

I tough about a new simulation descriptor like "Antiregen" but it seems to be unnecessary.

Any leads ?

I will have a look again at the pdf (thanks for the french words, did not catch those ones in my last reading).

I will see what we can do to add explanation about path.

Otherwise please do not hesitate to look at the numerous xml of the game considering there are a lot of elements that can be used as example.

I will also add info about the season check that can be done through path: #Summer or #Winter

To detect if a unit is on a district, look at the morale bonuses in the Class xml. One morale is given if a unit is on top of a district.

b) Operation : Can i use percent? where can i see if i can ? What's the Composition="Minimum" mean in the simulation descriptor?

c) Value : Can i use a negative %? like that? or just "-100" ?

d)Path : I didn't really understood how "to designate the target".

Seems to be easier to only work with ".../" ?

Where can i find all the Class ? all the classes are here ? :

EmpireTypeMajor (ou plus simplement ClassEmpire) <= some french words in the tutorial

>ClassCity

>ClassDistrict

>ClassPointOfInterest

>ClassArmy

>ClassUnit

>ClassEmpirePlan



#Winter ? didnt see any reference in the pdf, i guess that's a sort of trigger who affect the unit only in winter ?







PS : Should i create one unique trait per mod or can i create multiple traits per mod ?

You can use percent.

Minimum means the Movement will be the "minimum" from all the properties that are tied to it (in an army, the movement is the movement of the unit with the least movement points)

You can use -100%.

Paths : I'm not sure how it works, I had a lot of difficulties to make my mod works because of that

The #Winter is a global variable (as the # means), it means your path will only look at the path that will also have the winter tag.

Sorry for the point 3 code tag didnt worked properly, and i cant edit my post dunno why ^^"



I tried this :

[CODE][/CODE]

And tadaaa ♪ :

[ATTACH]14396[/ATTACH]



That's not percentage but...it's nearly what i wanted to do ...



EDIT : after looking how the seasons works i copy pasted this :

[CODE] [/CODE]

Aaaand it works



Sooo... i answered to my a)b)c) questions... but i'll be glad to have some enlightments about the Path.

By exemple, how to detect if an units is on a town center / district ? How to know if an unit is "into the wild" (not on or near a city, district, watchtowers) ? How to detect ... if x unit is in garnison ? (well for that i could try to find the .xml with the cultist quest with 2 preachers lvl 6 i guess), How to detect terrain? ?