Players can drag their token between maps, creating duplicate

[Ecks]

Not sure if this is expected behavior or not, but I seem to recall players shouldn't be able to move their tokens between maps. With token locking disabled, a player can drag their token to a different map. This creates a duplicate of the token, and the new token is not linked to the combat tracker.

In a new 5e campaign:

1. GM: Load FG Battle Maps
2. GM: Open BattleMap01 and BattleMap02, disable Line-of-sight and Lighting. Disable token locking.
3. GM: Create PC and add token to CT and then CT-> BattleMap01
4. GM: Share both BattleMap01 and BattleMap02
5. Player: Open both maps, and drag player's token from BattleMap01 to BattleMap02. The token is duplicated and the new token is not linked to the CT.

FGU v4.1.0 (2021-05-12)
5E ruleset v2021-05-11
Windows 10

[Moon Wizard]

Players can not drag tokens between maps; so basically the players are placing a generic version of their token on the new map. Only the GM client can move tokens between maps by design.

Regards,
JPG

[Ecks]

Right, I know players aren't supposed to drag their token between maps - I'm saying they're able to when they shouldn't. I thought this used to be prevented, but that may have been in FG Classic (which appears to prevent this).

In FGU, a side effect of players being able to drag their tokens between maps is that they can drag their token to an area not visible or blocked by Line-of-sight occluders, and then select the new token and view areas they shouldn't. I actually just tried this and it caused an exception on the player client:

[5/15/2021 7:39:20 PM] [ERROR]  MOUSE UPDATE: System.NullReferenceException: Object reference not set to an instance of an object
  at FG.CompImageTokenLayer.UpdateSelection () [0x0013b] in <8ed54a3091454284b1a1d3848bf00d96>:0 
  at KGNOOCIONDH.DJDKOKMHJAO (System.Int32 MKMNJAEJJLB, JJEKLHKGKBN DOAIEANCHCB) [0x00086] in <8ed54a3091454284b1a1d3848bf00d96>:0 
  at KGNOOCIONDH.FBNJEHOJJJJ (System.Int32 MKMNJAEJJLB, JJEKLHKGKBN DOAIEANCHCB) [0x00108] in <8ed54a3091454284b1a1d3848bf00d96>:0 
  at KGNOOCIONDH.ACAGGENLAAE (System.Int32 MKMNJAEJJLB, System.Boolean CEKOMJKGBNI, JJEKLHKGKBN DOAIEANCHCB) [0x000de] in <8ed54a3091454284b1a1d3848bf00d96>:0 
  at FG.CompImageTokenLayer.ReceiveClickUp (System.Int32 OFIHBJJLLEO, UnityEngine.Vector2 KDOLCCJLOPE) [0x000c0] in <8ed54a3091454284b1a1d3848bf00d96>:0 
  at FMPJEDNFKON.MJNHCNGDOEA (System.Int32 OFIHBJJLLEO, UnityEngine.Vector2 LPJINEPFOMB) [0x000f9] in <8ed54a3091454284b1a1d3848bf00d96>:0 
  at AEKKJAPPMPK.DOPJDILPJCG (System.Int32 OFIHBJJLLEO, UnityEngine.Vector2 OHCOFOJAPAN) [0x00050] in <8ed54a3091454284b1a1d3848bf00d96>:0 
  at KGNOOCIONDH.ReceiveClickUp (System.Int32 OFIHBJJLLEO, UnityEngine.Vector2 OHCOFOJAPAN) [0x0001b] in <8ed54a3091454284b1a1d3848bf00d96>:0 
  at LEECPKFJIAJ.PKJBEAGEEFK (System.Int32 OFIHBJJLLEO) [0x001b0] in <8ed54a3091454284b1a1d3848bf00d96>:0 
  at LEECPKFJIAJ.JIDMLNKADMN () [0x0005c] in <8ed54a3091454284b1a1d3848bf00d96>:0 
  at FG.FGDesktop.OPILCLOHJGM () [0x0002a] in <8ed54a3091454284b1a1d3848bf00d96>:0 
  at FG.FGDesktop.Update () [0x0004e] in <8ed54a3091454284b1a1d3848bf00d96>:0

To recreate the above exception in a new 5e campaign:

1. GM: Load FG Battle Maps
2. GM: Open BattleMap01 and BattleMap02 - enable Line-of-sight on both, disable token locking on both, and share both maps
3. GM: Draw an enclosed area that a player cannot access, e.g. BattleMap01-Occluders.JPG
4. GM: Drop the player token on BattleMap01
5. Player: Open both BattleMap01 and BattleMap02
6. Player: Drag token from BattleMap01 to BattleMap02, a new token is created
7. Player: Drag the new token from BattleMap02 to BattleMap01 inside the closed off area, e.g. BattleMap01-Duplicate.JPG
8. Player: The token isn't visible, but you can click it in anyways and the console opens with the above exception

[Zacchaeus]

I can replicate this. Players can indeed drag their tokens from one map to another. And you don't need to disable LoS. Once the token is on the other map it appears on the DM screen as well; and both the original token and the new one created can be moved around by both player and DM. Furthermore I've just noticed that players can right click on a token and delete it from the map. Was that ever a thing?

[Griogre]

It's probably one of the last way players can create and drag tokens around in FGU. The portrait image could always be converted to a token for the character sheet or the map / combat tracker / map. When doing a manual druid wild shape in FGC last week after the wild shape ended - I grabbed the portrait in the top left and dropped it onto the combat tracker to revert the map token back to his humanoid form, and I always drag off the portraits when dragging multiple copies of the PC token to a map for marching orders, ie 5' corridors, 10' wide, Outdoors when you need duplicate tokens for each PC that I don't want linked to the combat tracker.

This behavior is similar to shared tokens in FGC where the player can drop, move and delete tokens.

[Mike Serfass]

My players discovered they can place, delete, move, resize, and see through tokens on the map. They can do this to tokens that are not linked to CT. They can't do anything to enemies, but sometimes I have unlinked tokens on the map. (i.e. villagers that get under foot during combat, or people that need rescue or escort). There's no point in cluttering CT with those NPCs. But then the players can do all kinds of things to them, including revealing fogged areas of the map. Sometimes I want them to be able to move the tokens (escort quest or mind controlled npcs), but other times I'd like to be able to lock the tokens. At the least they should not share vision or reveal fog of war. At the same time, they can't place their own pets, familiars, companions, allies, or summoned creatures on the map. It's sometimes odd what players can and can't do.