Support priority definition

redrum

@Cernel I see. Well, I don't think it would be easy to add an option to order them by the unitType list in the supportAttachment given how its currently implemented. The reason for that is that support is calculated 1 unit at a time and the support attachments are essentially sorted before that. An easier approach would be providing a list for each unit for the order it would prioritize receiving support or just have a way to globally define a list of the ordering for all units. But I'm not sure whether that would work for your particular map.

Cernel

@redrum said in Support priority definition:

An easier approach would be providing a list for each unit for the order it would prioritize receiving support

Can you clarify what this mean with an example? I'm not sure I understand.

or just have a way to globally define a list of the ordering for all units. But I'm not sure whether that would work for your particular map.

This would be a little limiting, in perspective, but still much better than nothing, and would at least cover all I have at the moment.

redrum

@Cernel So instead of specifying the priority units receive the support attachment in unitType list. You would have a unit option where you could list what order support applies to a unit:

<unitAttachment>
   <option name="supportOrder" value="supportAttachment1:supportAttachment2:...."/>
</unitAttachment>

Or have a global property that does that for all units:

<property name="supportOrder" value="supportAttachment1:supportAttachment2:...."/>

Cernel

@redrum said in Support priority definition:

@Cernel So instead of specifying the priority units receive the support attachment in unitType list. You would have a unit option where you could list what order support applies to a unit:
<unitAttachment>
   <option name="supportOrder" value="supportAttachment1:supportAttachment2:...."/>
</unitAttachment>
Or have a global property that does that for all units:
<property name="supportOrder" value="supportAttachment1:supportAttachment2:...."/>

Oh no, you misunderstood! Maybe my fault.

By the way, that would be nice to have too, but it's just not this feature request.

What I was saying is ordering the units that receive the support, not ordering the supports that the unit is receiving.

For example (not my case), if I have artillery supporting infantry and marines, being able to define whether the artillery is going to support infantry or marines units first. Currently I believe how it works is that the one with the lowest basic strength is supported first, and alphabetical order if they have the same value (this can remain the default behaviour, though I think list order would make more sense than alphabetical).

Cernel

@Cernel Side note, the way it works should be documented in pos2 anyways. I just believe that is how it works by testing it, but I may miss something, so a developer would need to look at the code and confirm, before anyone documents it.

redrum

@Cernel I see. I think probably the best that could be done without a very significant rework would be to have a global property that defined the priority of units for receiving any support:

<property name="supportOrder" value="unitType1:unitType2:...."/>

The units would then be sorted to match that and then each unit checked against all support attachments 1 by 1.

Cernel

@redrum That would be good for me. I can see it maybe being a little limiting, and my proposal was basically to use the order you are already going to define in the "unitType" option (which is currently just a set), so that it can be set for each support attachment, then a global property for telling using that, instead of ordering by the current default method, whatever it is.

Cernel

@Cernel But currently the default is global too, as it is based on the values and names of the units, so I see it would make sense to modify that globally, as well, instead of per attachment. Anyways, as I said, this would be really good, especially if you want to make a game and be sure to define such behaviour as you wish (currently you have to rely on a default that is not even documented!).

redrum

@Cernel Yeah, you could potentially just have a boolean property and use the ordering of the unitType list in the XML but since that list is used for what order units are displayed in, I figure its better to have a separate list for support ordering in case you want them to display in a certain order that is different from what order they receive support.

Cernel

@redrum said in Support priority definition:

@Cernel Yeah, you could potentially just have a boolean property and use the ordering of the unitType list in the XML but since that list is used for what order units are displayed in, I figure its better to have a separate list for support ordering in case you want them to display in a certain order that is different from what order they receive support.

I don't really see why, and I actually think it might be better if the two are the same. Anyways, any very good quality maps should use custom tooltips, if you ask me.

Cernel

I'll add to the initial post a request for documenting exactly how the current system works. A thing I didn't test is, for example, if changes to the strength values of the units due to technology or territory effects will change the support order.

redrum

@Cernel I think an example would be you want units to display generally from weakest to strongest in the BC and other places (inf, art, tank, etc) but maybe you want support for a certain map to apply in the opposite direction and apply first to strongest units to weakest units.

Cernel

@redrum said in Support priority definition:

@Cernel I think an example would be you want units to display generally from weakest to strongest in the BC and other places (inf, art, tank, etc) but maybe you want support for a certain map to apply in the opposite direction and apply first to strongest units to weakest units.

Again, I'm not sure we are talking about the same thing.

By "unitType" I (always and only) meant the option called as such in the support attachment.

I don't think that influences in any ways the listing in the battlecalculator or anywhere else, does it? That is why I said "which is currently just a set", isn't it?

redrum

@Cernel Oh ok. The issue with using the supportAttachment unitType is that if 2 supportAttachments had conflicting ordering, the way its implemented couldn't handle that as units are all sorted first then support is applied to each one. So you could only have a single ordering for supports which is why I recommended a global property.

Cernel

@redrum Ok, cool, I didn't know that. I can see it would be off the mark asking for reworking the general process to support what is a rather peculiar feature, so I'm editing the first post as requesting just a general customizable listing per game. I understand you know exactly how that support list is sorted and I'm guessing that same listing is used for other reasons too; it would be good to clarify this in pos2.

Cernel

There is also the matter that I believe currently you have two priority lists, one for when the units are on the offence and one for when the units are on the defence. How I believe it currently works is that if you have a unit that it is 1/2 and another unit that it is 2/1, the first unit is supported first if it is attacking and it is supported last if it is defending (again; this should be documented exactly in pos2).

So, I don't actually want having the same priority order for both offence and defence and, if it can be confirmed what I'm saying here is correct, I've updated the first post with the request of two global properties, one for the offending and one for the defending units.

Cernel

@redrum Am I being correct about this, that currently there are two global lists per game for prioritizing support amongst units?

redrum

@Cernel Yes I believe the sorting of units based on either attack or defense of the units whether they are the attacker/defender.