Setting sub-properties false when their general property is true

Cernel

I've tested that if I set this:

                <property name="WW2V2" value="true" editable="false">
                        <boolean/>
                </property>
                
                <property name="Transport Restricted Unload" value="false" editable="false">
                        <boolean/>
                </property>

The "Transport Restricted Unload" behaves as true, as per general "WW2V2" setting. Is this how the system is supposed to work?

To make sure the issue is not in the specific property, I've tested "Transport Restricted Unload" false alone and it worked correctly as implied by being "false".

To clarify, I understand the "Transport Restricted Unload" property is supposed to disable the ability of offloading into multiple territories during Non Combat Movement, and it is a subset of the "WW2V2" property (being set true when "WW2V2" is true).

I've also tested this other, but similar, case (same inter-properties dynamics, I believe):

                <property name="WW2V2" value="true" editable="false">
                        <boolean/>
                </property>
                
                <property name="Unit Placement In Enemy Seas" value="false" editable="false">
                        <boolean/>
                </property>

And to make sure the issue is not in the specific property, I've tested "Unit Placement In Enemy Seas" false alone and it worked correctly as implied by being "false".

Also in this case, the "Unit Placement In Enemy Seas" behaved as "true", as per general "WW2V2" behaviour, ignoring the fact that I specifically set it as false.

More in general, what I'm asking is if I can set general Revised ("WW2V2") rules true, yet still turning some of its sub-properties (that this general property sets true) specifically false?

If this is not allowed, and it is intended that when I set "WW2V2" as true all its sub properties are also true, no matter if they are specifically set false (thus false totally equalling the property being simply absent in the xml), this should be documented in pos2. If not, this is a problem (engine bug).

@redrum @LaFayette @RoiEX @ssoloff Can a developer take a look at this and clarify whether the current behaviour is correct or not? I'd push an informative update to pos2 once this matter is sorted out.

redrum

@Cernel generally no. I'd have to look through the code but at least in most cases I've seen it checks if ww2v2 or some property is true. So that means if either or both are set true then you get true for that property.

I generally don't like this behavior but would have to consider existing maps if updating it.

Cernel

@redrum One way or another, if this can be confirmed, I would push an update to officialise it in pos2, unless a developer wants to do it himself. Logical or not, at least let it be known. If then, anything gets reworked, pos2 would be updated anyways.