You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attaching one token to another (such as for riding a mount), and holding Shift + W, A, S, or D, to change their facing but not move them, the primary token will point where you tell it to, but the attached token will point in the opposite direction. It's not a 180 from it though, it's closer to like, 150 degrees off or something.
The same thing occurs if you hold Ctrl or Shift and use Mouse Wheel to pivot the token facing.
The text was updated successfully, but these errors were encountered:
Ah, it seems to be an incompatibility with the module Auto-Rotate, when Default Rotation Mode is turned on. I imagine this is a problem with that module rather than yours, though.
Basically how token attacher deals with rotation: When a token is attached to a base token, it's rotation relative to the base token will be saved. After the base token moves/rotates/etc. the attached token will get it's rotation(and other data) set to the saved rotation relative to the new rotation of the base token.
Auto-Rotate might react to that and overwrite the rotation for whatever reason and overwrite what token attacher just set. I haven't looked at their code yet, but I can check next time I'm at my code.
When attaching one token to another (such as for riding a mount), and holding Shift + W, A, S, or D, to change their facing but not move them, the primary token will point where you tell it to, but the attached token will point in the opposite direction. It's not a 180 from it though, it's closer to like, 150 degrees off or something.
The same thing occurs if you hold Ctrl or Shift and use Mouse Wheel to pivot the token facing.
The text was updated successfully, but these errors were encountered: