In the description within the GlobalDefsConfig.ecf I miss one elemental information: How is the priorisation structured? What happens if the item has the parameter "ROF", the referenced parent item inherits a second parameter "ROF", the parent item inherits a inherited global third parameter "ROF" and the GlobalDefsConfig.ecf inherits a fourth global parameter "ROF" directly to the item? Or any other of the 16 possible combinations?
Any statement from the devs? I would like to conceptual design the respective behaviour for my ECE tool.
This is the correct forum mentioned in the experimental patch notes right? This is a feedback to a new experimental feature which could be fixed by a one liner in the file in some seconds, right? Or at least (if changing the ecf file is to complex ) needs a response from the devs here in this thread to solve the issue, right? I'm just wondering....one month has passed by....nothing happens....and this is a low brainer change....what's this forum good for?
Hello, I missed this. I'm not a dev and after checking it there will come a fix for it but in general the rule is like that: properties that are directly defined at the level where a GlobalRef is used do not get overwritten, however derived properties get overwritten. Thus a GlobalRef should behave like a directly defined property. Some examples: --- 1. Only Ref, no GlobalRef Items.ecf: ItemA Prop1: 100 ItemB, Ref: ItemA => here Prop1 has a value of 100 --- 2. Ref with GlobalRef and no other definition GlobalDef: SpecialValueOfProp1: Prop1: 500 Items.ecf: ItemA: Prop1: 100 ItemB, Ref: ItemA GlobalRef: SpecialValueOfProp1 => here Prop1 has a value of 500 --- 3. Ref with GlobalRef and with another direct definition GlobalDef + Items.ecf: as in Example 2 ItemB, Ref: ItemA GlobalRef: SpecialValueOfProp1 Prop1: 200 => here Prop1 has a value of 200 or if there was an ItemC like that ItemC, Ref: ItemB Prop1: 300 => here Prop1 has a value of 300 let me know if that makes sense
Thanks for the information. That means the global inheritance is as weak as the parent inheritance? Seems logical to me to preserve the possibility to overwrite the property localy in the item and to let this mechanic work exactly identical to the parent inheritance. I just would mention that the description in the ECF sounds exactly the other way round to me. I would love to see this explicit info in the description in the file. This also applies, if a global is inherited to ItemA? Example1: ItemA <- get global prop1, has no local prop1 ItemB, Ref:ItemA <- get global prop1 inherited from ItemA Example2: ItemA <- get global prop1, has local prop1 ItemB, Ref:ItemA <- get local prop1 inherited from ItemA
The description in the ecf doesn't mention inheritance at all really and as I said, there is one fix to come that will reflect these chains. Your examples sound correct - once the fix is out.
