Force Combination for subfolders?

[echo-of-machines]

Is it possible to force combinations on folders?
For example, if I have a "Fire Hair" folder with different layers, and I want this specific folder to combine with only "Fire Body", which also contains a bunch of layers, is this doable?

[nftchef]

Hi,
ForcedCombinations is only intended for single file combinations. This can and should be done by organizing subfolders into branches.

hope that helps!

[echo-of-machines]

Thanks for the answer, that helps a ton :)
But I ran into another problem.
Using the example above, if I need OptionA from the folder "body" to OptionA in "Hair" when using the force combination, there will be times where OptionA from "Hair" would appear alone without OptionA from "body" in some of the images because of folder order, and combining doesn't work backward. Is there a solution to that?

[echo-of-machines]

For example, if I type
OptionA:["OptionA"], this would let the first OptionA from the folder "Body" to force combine with OptionA in "Hair" thus successfully combining the two. But if the combination didn't pick OptionA from "Body", there will be times where I'll have images that only have OptionA from "Hair". In the situation where OptionA must only appear with OptionA, is there a solution?

[nftchef]

if the combination is truly a 1:1 forced combination, then you can use forcedCombinations, but yes, you would need to adjust the layersOrder to make sure they are chosen in the correct order.

if you have more options, then you can branch the folders "one more branch" deep, using folders as "if,then" decisions
something like

[soulmv]

There is also a workaround - setting incompatible layers. I know it's too much code but it worked for me.
For example you ve got two folders with Option A B C in one and Option D E F in another, and you want to pick Options A and E together. It should look like this in incompatible layers code:

OptionA: [ " OptionD", " OptionF" ]

That sets incompatibility between A and D F options, kind of reversal method.
But if you have 20 items in each folder - that might become a bit of pain to set up :)

Hope that helps.

[echo-of-machines]

This would still cause the same problem where the folder with D E F comes after the folder with A B C. This means E can't check if it's paired with A. So once we get to the D E F folder, we'll have E appear without A. In other words, OptionE: ["OptionB, "OptionC"] won't work because of the layer structure.