I've been working on an API for players to target their spells/abilities. Been a few headaches running into Roll20's current limitations (mainly the state of gifs and animations) but I've been able to work past most things until now. Long story short, when a spell is used, a 'targeting' token is generated that the player can move about the map then confirm the placement when an associated token action. It was working perfectly fine from the GM's perspective but when testing an unrelated issue from a separate, non-GM account, I noticed a pretty fatal problem. For some reason, the targeting token doesn't respect toFront() for the controlling player the same way that it does with the GM. Now, I noticed that tokens the player has control over seem to exert some kind of priority in the layering, which is understandable. But between two equally controlled tokens, one can get stuck under the other with which both toFront() and manually setting it from the GM's context menu has no effect. Again, from the GM's screen, everything is lined up perfectly fine. But trying to select a newly spawned token is a mess from the player's screen since it seems to be permanently ordered underneath the older ones. Am I missing something here? The help page doesn't have much to go on and a cursory search of the forums here only seems to bring up bugs from 5+ years ago. It's entirely possible I'm just an idiot here and overlooking something but forcing the player to move their tokens out of the way to be able to select the crosshairs token around really breaks this feature for me and I'll have to completely rethink how I'm going to implement this if I've run into a wall here.