[BUG] Mount Action and Tagger {#}

[fedeicodip]

Using the mount trigger action (with rideable), the {#} wildcard code (used by tagger to generate an unique variable identifier) isn't parsed and translated to a single number when a tile is placed on the scene. The mount action code remains pointing to a xxxyyyzzz-{#} tag that isn't pointing to anywhere (while the tile tag is translated as expected).

Side note: Rideable is configured to use tiles as rideable entities

[Crowguard]

@fedeicodip You should log with Rideable; its the one adding all the code for those actions.

[Saibot393]

I tried replicating the bug but had so far no success, just to make sure, that we are using the same conditions, are you using a MATT tile template or a token attached template?
Scratch that, sorry, tried it with the wrong field

[fedeicodip]

Thank you, let me know if I can help

[Saibot393]

I have found another core MATT field that behaves the same way, the "token" field of the "Reset Tile trigger history" action will also not update the {#} correctly when placed. From what i can tell, MATT will only apply the "{#}" counter to data fields that are named one of these: "entity", "location", "position".
I was however so far not able to locate the exact part of the code that will update the tags. I also don't think that there is a lot i can do on my end, sorry.

[Crowguard]

No problem; thanks for looking Saibot. Will have to just wait & see Ironmonk says I guess.

[Saibot393]

So, i had another look and figured out why i couldn't find the part of the code that takes care of the {#}. It seems like tagger itself is at fault here as it only takes entity and location fields into consideration when updating tags

[Saibot393]

I have created a PR for Tagger that should solve the issue