Rift Tokens (Forgotten Circles)

Question

Rift Tokens (Forgotten Circles)

Closed this issue 4 years ago · 3 comments

Affected Scenario(s): 96 and all FC scenarios

Describe the bug
Once a Rift Token is placed it cannot be moved or removed. Ethereal Vortex card allows these to be moved, but we are unable to using either the move character function or move obstacle or trap function.

To Reproduce
Steps to reproduce the behavior:
Place rift token, try and move or remove it.

Browser : Chrome

Answer 1 · 2021-02-10T07:56:36.000Z

This is a two part issue really - the first is that Rifts can't be removed, and the second is that obstacles overall can't be moved in Chrome.

Rifts are now removable! 🎉 This should sidestep the second issue, but doesn't fix it.
The second issue is more widespread and something I've been looking into for quite some time. A release of Chrome seems to have caused all obstacles to no longer be draggable. Despite my best efforts I can't see any reason why this would be the case when monsters and characters (which are semantically the same as overlays) are not affected.

I'm going to keep this open until I can find a fix for Chrome or until Google fix it themselves, but at least there's a workaround now.

Answer 2 · 2021-02-10T14:41:03.000Z

Thanks for the update! Your board had been a huge help allowing you group to play during COVID and from different states in the US. We used to set a camera up over the board but that obviously left one person moving characters and monsters.

…

On Wed, Feb 10, 2021, 1:56 AM David North ***@***.***> wrote: This is a two part issue really - the first is that Rifts can't be removed, and the second is that obstacles overall can't be moved in Chrome. Rifts are now removable! 🎉 This should sidestep the second issue, but doesn't fix it. The second issue is more widespread and something I've been looking into for quite some time. A release of Chrome seems to have caused all obstacles to no longer be draggable. Despite my best efforts I can't see any reason why this would be the case when monsters and characters (which are semantically the same as overlays) are not affected. I'm going to keep this open until I can find a fix for Chrome or until Google fix it themselves, but at least there's a workaround now. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#61 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASZOWI5CKQE32Z2VR6L4AFLS6I34DANCNFSM4XMECTMQ> .

Answer 3 · 2021-02-11T17:50:23.000Z

No problem! Really glad you're enjoying it - hopefully that Chrome bug won't be too troublesome until I can get a fix 🙂