Token strata (stacking order)

[Weissrolf]

Non CT based tokens (assets) still cover CT based NPCs. Please change the order/strata of these things so that NPCs are on top of asset tokens.

[LordEntrails]

Please remember that the Laboratory is for discussing features in the test channel. Currently this would be lighting and vision. Feature requests should always be added to the Wish List, and if appropriate a discussion thread in the correct ruleset thread (or CoreRPG for generic or multi-ruleset suggestions).

[Moon Wizard]

Our plans are to eventually fix token stacking so that last token touched is on top.

There is no concept of token ordering from a ruleset/API level; and it's not on our list to add anything like this at this point.

Regards,
JPG

[Weissrolf]

The challenge right now is that the token ordering code is in the middle of a huge refactoring that cpinder is working on for lighting/vision; so any updates to any image/token logic are gated right now.
This is the light/vision beta, so according to this quote this also is the token ordering refactoring beta.

Putting non CT tokens on top of CT tokens was wrong to begin with and should have been fixed already. Not only does it break both spell token extensions, but makes asset based tokens (plus any such bought token image files) mostly unusable when CT NPCs are present.

[Zacchaeus]

This is the light/vision beta, so according to this quote this also is the token ordering refactoring beta.

Putting non CT tokens on top of CT tokens was wrong to begin with and should have been fixed already. Not only does it break both spell token extensions, but makes asset based tokens (plus any such bought token image files) mostly unusable when CT NPCs are present.

You are misunderstanding what Moon Wizard is saying. He's saying that token refactoring is in the middle of code that is needed for lighting. So that code won't be changing until after lighting is finalised (at the earliest).

[Weissrolf]

I understood that one goes hand-in-hand with the other, which is why we had to wait for token stacking fixes to happen. Now that lighting code is active in the beta I expected token strata to be fixed as well. It is not, hence my feedback on noticing the missing fix.

What you are saying now is different from what was presented beforehand.

Before: Token stacking is refactored with LoS/lighting.
Now: Token stacking is refactored after LoS/lighting.

Seeing how demanding lighting will be on player hardware I suspect that my groups will not be able to use it. We would have been using spell tokens for light areas for months already if it token strata had been fixed. Instead the GM (me) has to manually push circle pointers around (the small center of which are often half-hidden on PC tokens).

[Zacchaeus]

My understanding has always been the same; token stacking isn't something that would be looked at until way down the road. Especially since we have map layers and can use spell tokens perfectly without having to worry about token stacking.

[Weissrolf]

Only of "perfectly" translates to "awkwardly". Maybe fix the features I already paid for instead of promising to fix it after new features may or may not arrive in usable form then.

[Zacchaeus]

Token stacking was already in the software when you paid for it. So you already have what you paid for.

[Weissrolf]

Classic, mostly working (with quirks). Unity, broken from the beginning, fixes being promised with LoS/Lighting features.

[LordEntrails]

Regardless of what you want or your opinion on the matter. This is not the place, the time, or the way in which to get it addressed. Making your opinions known is great and desired. Hence why I made the suggestion of how to do that above (and again since it seems it is not something you agree with either).

Making a pest of yourself when the devs do not agree with the priority you place on your opinions is not. It's akin to being a bully and is not appreciated by the community. Your opinions are no more or less important than any other user's opinions. You frequently come across as if your opinion is the most important or even the only one that matters. As well you seem to get offended when others do not agree with you.

To directly address token stacking; It has been acknowledged that there are known issues with it. There have been since I used FGC in 2015. FGU is not (imo) significantly different in that regard. Depending upon one's interpretation of previous statements, it would either be addressed with vision and lighting, or after vision and lighting. Given that it clearly has not been addressed with vision and lighting and what features have been introduced in 4.1 beta clearly do not include token stacking, then one can make the definitive conclusion that it the devs did not intend to address token stacking with 4.1. Regardless of what anyone's thought or desires are/were.

Therefore, since token stacking is not in 4.1 beta, and it is not in beta testing, this forum is the incorrect place to discuss it.

Asking about a status update on when it might be addressed is normal/fine/acceptable. Repeating already discussed issues and complaints is either an attempt to garner more importance for your opinion or other impolite behavior. Therefore I'm closing this thread.

For anyone who would like to voice their opinion on the importance of token stacking issues, please vote on the feature request here; https://fgapp.idea.informer.com/proj/?ia=135367 This is the way the devs have asked the community to show what is important to the community at large.