KayelGee / token-attacher

MIT License
11 stars 18 forks source link

unable to select token with 4.1.0 #38

Closed wmve closed 3 years ago

wmve commented 3 years ago

versions: image

i've been waiting for more stability from Token Attacher with D35E and latest update shows a new behaviour with an existing token in my world.

  1. load world
  2. select token in question expected behaviour: able to select token (see yellow outline) actual behaviour: unable to select token

i watched the console and only see one strange info message, but it only when i successfully move OTHER tokens. not sure if it means anything. i'll let Rughalt (D35E) know as well. image

wmve commented 3 years ago

sorry, forgot to add export of actor:

fvtt-Actor-meranis.210614.zip

KayelGee commented 3 years ago

so I checked your actor export and I don't see any token attacher related data in there. Are you sure this is the correct actor?

When you attach a token to another token then by default you're unable to select the token anymore unless you unlock the token in the attach ui. You also are able to select the token if you have the attach ui of the parent open or if you enable quick edit mode.

If you accidently deleted the parent token while you had token attacher disabled you can clear the flags of the token via macro like this token.update({['flags.-=token-attacher']:null})

wmve commented 3 years ago

yup, pretty sure that was the right one. i have deleted the token from the map (which i could only do with the module disabled), and dragged the actor to the map again. the new token does not exhibit this behaviour. don't know what to suggest if i can't reproduce anymore. close but keep an eye out i guess?

KayelGee commented 3 years ago

I think what happend was that you had the token attached to some parent token and while the module was disabled you deleted that parent. Because the module was disabled the data on the child didn't change so it still thought it was attached to something.