Thank you for sticking with me on this.
Here is the thought process that led to assigning the expression in an eval script.
I started with the code in the field instead of script. As you can see from your own tests, if the tag is already on the "thing" it shows, but if the tag is assigned later it doesn't (at least i couldn't get it to work for me).
So thinking it might be a timing issue, I tested assigning the expression to the field in an eval script at a later timing to make sure that my script assigning the tag would run before the configurable. Again, if the tag is directly assigned to the "thing" it shows up, but even with the later entry of the expression, anything that did not have the tag directly assigned still does not show.
Here is how I was testing this.
- remove the tag from your fake ability. (of course it won't show now)
- create a feat and bootstrap the ability to it (so it will be on the hero)
- create a eval script on the feat to assign the tag to the ability.
Use the floating windows to verify that the ability is on the hero and that it has the tag. <check>
Then check if it shows on the configurable. <...>
Right now I suspect that the configurable pulls tags at start (ie only initial tags) and sorts them late (I think the task was around
Final Phase 50,000)