Associate. The damned. Tokens. With the sheet they came off of Already

Its the entire way roll 20 works.  That token on the map is tied to that sheet. That token was made by dragging the sheet onto the map. You HAVE to know that's the character. WHY is roll20 pretending there's no association there? It's not a cache problem. Its not a mod . It happens on fire fox. It happens on chrome. Its been happening for months. I cannot associate my token with my sheet as a player and I should not have to manually do that as a dm for EVERY freaking token. Its annoying AF. The entire point of letting players import or make their own characters is so that I don't HAVE to set a setting for 6 people every time I sit down.

Hi BigNorseWolf,  Are you reporting a bug or trying to make a suggestion? If you are reporting a bug, could you elaborate on what you are seeing?

This is a bug. Roll20 used to associate a token with the sheet it was dragged from ... reliably by roll20 standards. Every once in a while it would bork. Now its constant. Tokens are not being associated with the sheet they came from. Its not what I see its what I DON"T see. Anything working. I drag a character from the sheet onto the map the token then has to be associated with the sheet by the DM.  This is necessary to use token actions. Link since the image button doesnt work either.

I am not seeing what you are seeing.  Using my dummy account, I create a new character, then I drag it from the journal to the table. After that I shift+click to open the character sheet, result is it works.  Could you provide the steps you are performing? Also, regarding the "image button" how are you trying to use it? Copy/paste? Or drag and drop a file from your computer? 

I'm following the same steps you are just not getting those results. Except i thought Alt click click opens the sheet. As a player it consistently will not associate As a DM its hit and miss.

Oops, I always get Shift+Click and Alt+Click switched around. LOL I've created about 10 characters to test so far, none have a problem.  Are there any other steps you might be performing? Adding an image perhaps? Which browser are you using? Have you tried Incognito or Private mode?

aaaand now its working. I made an entirely separate character dragged them onto the map went back to the first character  threatened the computer with a magnet and now the token is associated with the sheet. Both seem as likely to have caused the change.  Perhaps I should try burning sage?

This is at least the third time I've been annoyed with the issue enough to make a post about it.   This is a core functionality of roll20. Perhaps THE core functionality. It should NOT be failing this often.

Just a reminder, making posts about it on the forums is not filing a bug report with the Devs. That is asking for help from fellow users.  If you want to file a bug report with the Devs then you should use the Help Center . 

I have never had this not work. Never.

Hi BigNorseWolf! Without being able to investigate the situation in a hands on way, it's really impossible for a third party to tell what the issue might have been. In most cases, it's simply that the default token was not saved properly, usually steps followed in the wrong order. (Set up the representation field > assign the bars and other values > save as default). I have seen many users do the last step first by accident.

Tokens normally do fine without a default token The share picture thing that is supposed to be in the forum is of course, broken so I'll put these up on google slides <a href="https://docs.google.com/presentation/d/17wN6ON_pe2M3zkVHD9u_jL37ZSYboAWPUojeA3_2kC0/edit?usp=sharing" rel="nofollow">https://docs.google.com/presentation/d/17wN6ON_pe2M3zkVHD9u_jL37ZSYboAWPUojeA3_2kC0/edit?usp=sharing</a> A weird idea occurred to me and I will try to replicate the error.. .. Nope. Its not because one picture was normal and one used transparencies.

BigNorseWolf,&nbsp; Could you give a click by click breakdown of how you are using "Share Picture"?&nbsp; I ran a test and it works for me.&nbsp; Regarding your link, only the first of the three images show for me.&nbsp; From that image, I cannot see any problems. Could you provide exact steps to replicate the problem?&nbsp;

I've only got one image up on the slides because&nbsp; I could not replicate the problem with the tokens not associating Keith said it might have been an issue with the default token. The slide shows that its not a default token issue, since you don't need a default token at all to associate the token with the character.

Alright, well if you have reproduction steps let us know. I'd like to try to reproduce this.&nbsp;