variables in wildcards doesn't apply to upper scope same-name variable

[teamolhuang]

I wrote some generic prompts to combine funny arts, like this

# main-prompt.txt
${character:__characters/**__}, ${default-eyes:{looking at viewer|averting eyes}}

# characters/a.txt
${default-eyes=ahegao}morikubo nono, other tags...

and in UI prompt I wrote it like:

${character=__characters/a__}__main-prompt__

This results in all images are with character A, but ahegao never gets used. Instead it's using the default values in main-prompt. Is this expected behaviour?

When I write it like this in UI prompt:

${character=__characters/a__}${default-eyes:ahegao}__main-prompt__

It's now character A with ahegao always as expected. I wish to exhibit this behavior without defining default-eyes in UI prompt.

I've tried immediate evaluation in characters/a.txt, but still doesn't work.

This can apply to outfits, etc. I want to define default outfits for each character in the character's template, and later in the main prompt decide to use those or not. Current behaviour makes it difficult to achieve.

[teamolhuang]

With further test, I think this is related to variable scope. If I change to a structure like this,

# main-prompt.txt
${character:__characters/**__}

# eyes-picker.txt
${default-eyes:{looking at viewer|averting eyes}}

# characters/a.txt
${default-eyes=ahegao}morikubo nono, other tags..., __eyes-picker__

# characters/b.txt
kobeni higashiyama, other tags... __eyes-picker__

This works as ahegao is now successfully constantly chosen, but now every character/*.txt has to have eyes-picker. Is there a better way to structure this?