Player Tokens not moving

My DM and I are having trouble using our tokens and moving them in the map. I am able to drag my character token onto the map but once there it wont work- I cant move it or control it or select it. It's weird because the tokens worked before, so I'm not sure what's wrong with it.

Hi Arb! The most likely reason is that the default token was not saved properly. Have your DM open the token that you currently cannot move, and check the permissions: that it is assigned to a character, and that that character is one you control. If the token was set up and not saved as default after setup, then the default token does not have those modifications. Also, make sure that the token is on the token layer.

We were just having this same issue. However, we did not have this issue when we played on Saturday, so this is a new development.

Okay, so! I was not DMing the game I mentioned above, but I DM my own campaigns on r20, so we were both able to test some things to investigate this ourselves. We found a fix during the session (before I posted above), and after I posted they and I have spent the past couple hours trying to replicate the issue and then fix it after replicating it. It took awhile, but I think we've figured it out. To summarize: it appears that the issue is that it seems that "Controlled By" under edit character sheet  no longer allows a player to control the character unless  the token's cogwheel settings  also is set to "Controlled By" the player (it does not  require "Represents" to be the player's character sheet, but it does  require "Controlled By"). But as long as it's in a player's journal they can  drag the token onto the map, but once they do they can no longer move or even click the token. When a player creates a sheet, it does  automatically set "In Journal" and "Controlled By" in edit character settings  to the player who created it, but it does not  automatically set the token cogwheel settings  to them having "Controlled By" permissions. It appears this applied retroactively to existing sheets we had already made as players. If token cogwheel settings  has "Represents" as the sheet, it sets it to "Determined by Sheet Settings" that does allow the player to move the token as well. I have to step away for a bit but I have my methodology for recreating and fixing the issue partially typed up. I'll finish that and share it once I'm back in an hour or two-ish.

Hi Ramsey! Assuming I read your description correctly, that sounds like standard setup. If a token represents a character sheet, that sheet must be controlled by a player. Note that after the token is assigned to represent a character, the token must then be saved as the default token for that sheet. Otherwise it will not still be properly set then next time it is pulled out. If a token does not represent a character sheet, it must have its "controlled by" field assigned to any non-gm player that wishes to move it. If you see "Controlled by" on a token, then it does not represent a character. Setting representation removes the ability to set a "controlled by" since that option becomes disabled.

keithcurtis said: Hi Ramsey! Assuming I read your description correctly, that sounds like standard setup. If a token represents a character sheet, that sheet must be controlled by a player. Note that after the token is assigned to represent a character, the token must then be saved as the default token for that sheet. Otherwise it will not still be properly set then next time it is pulled out. If a token does not represent a character sheet, it must have its "controlled by" field assigned to any non-gm player that wishes to move it. If you see "Controlled by" on a token, then it does not represent a character. Setting representation removes the ability to set a "controlled by" since that option becomes disabled. Thank you for offering the information. However it seems non-applicable and also irrelevant to the cause and the solution, at least in our case. To be a smidge blunt here: on Saturday the 2nd we did not experience this issue nor have we ever prior. Today we did, and there are absolutely zero things we have done differently. No tokens, sheets, or settings within the game interface nor outside of it were modified between Saturday and today when we experienced this bug. The sheets used were the exact same as Saturday. All tokens placed Saturday still functioned as expected, all tokens placed today did not. DM and I each have over 7 years experience using roll20 (and other VTTs and programs) as both player and DM, with over 20,000 roll20 game hours clocked between us, over 25,000 if you add in the other two at our table. Over 14,000 of those are mine with large majority as DM. So while not developers, we're all fairly familiar with how roll20 should typically function from both player and DM interfaces. And OP clocks over 800 hours including DMing based on their profile, which is not nothing. Bit of a hard sell for it to be a simple PEBKAC issue on one of the VTT's most basic interface functions I feel like, but I could be wrong. It would probably be easier if I just made a simple table with a couple screenshots for reference to show which setting combinations did vs didn't allow players control over their tokens. Something came up that took longer than anticipated and also I need to pop off soon, but I could probably do that tomorrow if it'll be helpful. Real quick, though, here's a bit more on our findings: Our table first experienced this bug on a map with dynamic lighting and presumed the issue was the dynamic lighting, but we ruled that out; it occurred on other maps, both ones with and without dynamic lighting. Tokens still on these maps which were placed on or before Saturday still functioned as expected, but any tokens placed onto those maps today did not.  Based on our troubleshooting, my best guess is that new character sheets which the player  created formerly made the token settings default to "Represents - (sheet name)" and as such "Controlled By - Determined By Character Sheet" (or perhaps even "Represents - None/Generic Token" and "Controlled By - [player name who created the sheet]" which also causes tokens to function as expected), but for reasons unknown to me they no longer do - in our tests they defaulted to "Represents - None/Generic Token" and "Controlled By - [empty]" - and pre-existing player-created character sheets changed to match (as per our findings). Meanwhile, tokens  previously placed by the same player from the same character sheet maintained the former "Represents - (sheet name)" and "Controlled By - Determined By Character Sheet" in its token settings, which is what we saw on all the tokens we checked, hence why those could still be moved by the player.  However, when the DM created a sheet and assigned it to a player, the token's settings automatically defaulted to "Represents - [sheet name]" and "Controlled By - Determined By Character Sheet" and could be moved by the player. The sheets are all 2024 sheets; we did not think to try recreating the issue on 2014 sheets before the DM had to head off.

Hi Ramsey K.,  Could you contact me on Discord via the Roll20 Discord server? (I am near the top as Gauss, in the Champion of Roll20 section). I would like to join you in a call where you share your screen so I can troubleshoot this.

HI Ramsey (and Arb)! It looks like there may indeed be some issues, and this has been escalated. Ramsey—Sorry if my initial response came off as in any way dismissive. Not being acquainted with reporters personally, we usually have to start off with the basic, most common solutions and then drill down until we find out the source of the issue.

This appears to be persisting in the form of when using the card deck and getting cards as well. Once players put cards down on the field they can no longer move them, pick them up, or take them back. Which effectively makes the GM have to deal with all cards all the time on the field rather than Players having free will.

Hi Meta K.,  Can you edit the cards and screenshot the settings? I'd like to try to replicate the issue. See if it is the same issue as the token issue.

I also have same card deck problem as Meta K. players can choice card, and they can  put them on map, but That's it. They can't move, delete, or click card on map no longer.

Confirming as well that I also have this problem with Card Decks. This seems to only be a problem in 'modern' Roll20 games - Legacy games can still move the cards w/out issue. Here's are the settings that both the legacy game and the modern game uses for card decks: {Y} Show Deck to Players {Y} Show card tooltips {Y} Players can draw cards {N} Cards in deck are infinite Allow choosing specific cards from deck: Disabled Discard Pile: Choose: Show Fronts Removed Cards Pile:  Choose: Show Fronts When Played to the tabletop... Played Facing: Up Card Size - left blank In Other's Hands... Players See {Y} Number of cards {N} Front of cards GM sees {Y} Number of cards {Y} Front of cards The only difference between the legacy game and the modern game is the 'considered' setting. In the legacy game, it's a drop down menu, but in the modern game, it seems that roll20 has converted it to a bunch of check boxes - they also call it 'behavior' instead.  In the legacy game, the Considered setting is: Drawing (No Bubbles/Stats) In the modern game, the behavior settings are: {N} Cards snap to grid {N} Cards have token menus and bubbles I have played with the new game's settings to see if it changes anything with no luck.  I'm also a long time veteran of Roll20, and we actually make custom card decks (a Major and Minor Arcana deck) instead of dice for one of the TTRPGs I run and play in. Having the GM be the only one who can move the cards and more importantly, delete them from the tabletop ends up slowing the game down for us, since the GM now has to clean up on top of the other duties they might have. None of us had this problem in April, so my only guess is that something in May has changed how cards (and tokens) are read.

Thanks to everyone replying! (and sorry for late reply I havent used roll20 in a week so I didnt check). I went to my DM's campaign and the issue is still persisting. I can provide information as needed regarding it so long as you let me know what I'd need to provide.

I sent a bug report with the same issue, we had a game where everyone was in a map and I had to add my character, when I added it I could not control it after clicking and dragging from the journal tab. Another interesting thing is when it gets placed on the map it does not line up to the grid. My dm does have the ability to manipulate the token but as far as ownership I do not control it

Meredith said: Howdy, y'all!  Not being able to move tokens is extremely frustrating so we appreciate you all for taking the time to write in so we could look at this quickly. The Forum Champs have escalated this issue up to the VTT Team over the last few days and the VTT Team have released a fix for the tokens being unable to move. This should work as intended going forward. If you are still experiencing issues, give us a shout and we'll check in with the VTT Team as soon as possible!  Hello, its still not working for me, I can confirm.

Hi Arb,  Has your GM edited the token and made the corrections?  The Devs' fix should only prevent it from breaking in the future. It will not correct the existing tokens.  The steps that need to be performed (by your GM):  Edit the token Click the "Represents Character" line In the dropdown menu select the character that that token represents.  Make sure any other settings are correct.  Click "Update Default Token" Save After that the token should work for you, and any new token of your character when dragging it from the Journal tab should work for you. 

Hey, After forwarding this to my DM, I can indeed confirm that it works and the tokens can be moved now! Thanks for all the helping getting this sorted!

We are having the same problem as well. Cards worked 4 weeks ago, then they didn't in our session a week ago.  Mothman said: Confirming as well that I also have this problem with Card Decks. This seems to only be a problem in 'modern' Roll20 games - Legacy games can still move the cards w/out issue. Here's are the settings that both the legacy game and the modern game uses for card decks: {Y} Show Deck to Players {Y} Show card tooltips {Y} Players can draw cards {N} Cards in deck are infinite Allow choosing specific cards from deck: Disabled Discard Pile: Choose: Show Fronts Removed Cards Pile:  Choose: Show Fronts When Played to the tabletop... Played Facing: Up Card Size - left blank In Other's Hands... Players See {Y} Number of cards {N} Front of cards GM sees {Y} Number of cards {Y} Front of cards The only difference between the legacy game and the modern game is the 'considered' setting. In the legacy game, it's a drop down menu, but in the modern game, it seems that roll20 has converted it to a bunch of check boxes - they also call it 'behavior' instead.  In the legacy game, the Considered setting is: Drawing (No Bubbles/Stats) In the modern game, the behavior settings are: {N} Cards snap to grid {N} Cards have token menus and bubbles I have played with the new game's settings to see if it changes anything with no luck.  I'm also a long time veteran of Roll20, and we actually make custom card decks (a Major and Minor Arcana deck) instead of dice for one of the TTRPGs I run and play in. Having the GM be the only one who can move the cards and more importantly, delete them from the tabletop ends up slowing the game down for us, since the GM now has to clean up on top of the other duties they might have. None of us had this problem in April, so my only guess is that something in May has changed how cards (and tokens) are read.

Just a note, the Devs are working on the card version of this issue.  In the meantime, if you edit the card on the table you can assign it to a player.  You can edit it via double clicking it and then assign control of it to the desired player(s).  Alternately, if you have a Pro account you are able to do that via the script TokenMod using the command:  !token-mod --set controlledby|all

Hi Everyone,  The Devs report that this issue has been resolved. Please let me know if it is not working for you. Note: existing cards on the table will not be fixed, this fix is for cards going forward.

When I copy paste characters from one map to another, all their control permissions are reset. We do not play using the built in character sheets, it's extremely annoying.

Getting this issue on a game we're playing too, copying and pasting tokens between maps resets who controls the token.

Hi Blud and Tylian,  With the other issue regarding moving tokens resolved we have now figured out the next issue, that of tokens that never had connection to a character.  The Devs are aware of the issue. 

Having the same issue. Copy and then Pasting a token resets who controls the token. This is the first time it has ever happened to me. Worked just fine for 6 years.

The Devs inform me that this is now fixed. Please let me know if you have any continuing issue with it.  Note: the fix does not fix broken tokens, only fixes new copies moving forward.