Natural Selection - A solution to stacked tokens

[Saagael]

Has there been any movement on the issue [string "CoreRPG:scripts/manager_actor_display.lua"]:501: attempt to index local 'cImage' (a userdata value)? Would love to use this extension again since my group currently has a lot of summons and it can be a nightmare to keep everything orderly lol

Nope. All of my attempts to track down the issue have failed.

[rhagelstrom]

You could work around it with

if type(cImage) != 'userdata'

or

if type(cImage) == 'image'

[Saagael]

Hey all, I think I got it fixed finally. v1.9.0 is out and should fix this problem.

[Saagael]

This is the same issue I reported with Indicators ext also.

Im able to get this issue with B9 Spell Tokens as reported here. My guess is if you can work with Mattkure and get Indictors to work, it will likely fix this issue too.

I posted this on discord but I'll post it here too.

I looked into this issue and found it is reproduceable with just Indicators loaded (haven't tried it with Spell Tokens, but if they're the same system them they'll have the same problems). It's a result of invisible widgets that Indicators gives all tokens. These invisible widgets seem to not obey the normal z-layering rules that tokens do. So even if token A is above token B, token B's widget will be above token A. Thus when you click on the stack, you get token B, since you clicked on its widget. I was able to confirm this by disabling the invisible widgets in Indicators. Doing so produced the desired behavior, both with and without Natural Selection.

This sounds like a bug in how widgets are processed, and might need to be something Smiteworks fixes on their end. Other than that, I can't do anything from my side as the behavior occurs even without Natural Selection loaded. It just so happens that NS is intended to work in exactly the weird and potentially buggy space that this behavior occupies

[eporrini]

I posted this on discord but I'll post it here too.

I looked into this issue and found it is reproduceable with just Indicators loaded (haven't tried it with Spell Tokens, but if they're the same system them they'll have the same problems). It's a result of invisible widgets that Indicators gives all tokens. These invisible widgets seem to not obey the normal z-layering rules that tokens do. So even if token A is above token B, token B's widget will be above token A. Thus when you click on the stack, you get token B, since you clicked on its widget. I was able to confirm this by disabling the invisible widgets in Indicators. Doing so produced the desired behavior, both with and without Natural Selection.

This sounds like a bug in how widgets are processed, and might need to be something Smiteworks fixes on their end. Other than that, I can't do anything from my side as the behavior occurs even without Natural Selection loaded. It just so happens that NS is intended to work in exactly the weird and potentially buggy space that this behavior occupies

I am not sure exactly what you are suggesting to help make this function correctly again. Is there a recommended course of action?

[Saagael]

I am not sure exactly what you are suggesting to help make this function correctly again. Is there a recommended course of action?

Only speaking for the Indicators extension, which is what I tested, the issue will need to be brought up with the author of that extension. The widgets that are attached to tokens need to be set to ignore mouse events [via setEnabled(false)].

[SillyOldeBear]

Hey all, I think I got it fixed finally. v1.9.0 is out and should fix this problem.

I am still seeing the problem after closing and reopening the map with stacked tokens and then hovering over a token. It doesn't happen when Natural Selection is not loaded.

[Saagael]

I am still seeing the problem after closing and reopening the map with stacked tokens and then hovering over a token. It doesn't happen when Natural Selection is not loaded.

Can you do an update and confirm that you're still getting this issue on version 1.9.0. Thanks.

[MrDDT]

Can you do an update and confirm that you're still getting this issue on version 1.9.0. Thanks.

Tested and it's working great for me thank you.

[SillyOldeBear]

Can you do an update and confirm that you're still getting this issue on version 1.9.0. Thanks.

It looks like it's working now. Thanks!