Erroneous, Spontaneous Token Duplication Issue

So I am running into an issue with player tokens duplicating when editing a token bar value. For example, Player A took 5 damage. -5 to hp token bar. When enter is pressed, all of the other locations the player token was initially placed (i.e. when dragged from journal to map), suddenly show up again on every map they have previously been placed on. I just don't get it. This is only occurring for two out of the five player tokens. If I change or completely dissociate the specific player token from the character, upon changing the token bar value for whatever new token I link to the character, all of the previous token will still show up, even if they are linked as the token to the player character. Also, for one of these characters, the token bar values and associated attributes do not save when re-placing said character. I just don't get what is going on. I am new to Roll 20, and that's my excuse if I introduced this phenomena by accident...but still...very frustrating. Thank you in advance!

That's one of the weirdest bugs I've ever heard of. The token, not the token values, is re-appearing? The actual graphic? That would require something pretty powerful acting upon your game. Some initial questions: Are you playing in a game in which API scripts are enabled? Are you running any browser extensions or userscripts which alter the behavior of Roll20? Does the problem occur if you are running your game in a private browsing window? Have you tried deleting the cache and cookies in your browser? Are you using a browser other than Firefox or Chrome? As for your last question, this could simply be due to improper setup of the token, usually making changes to a default token and expecting them to propagate back to the saved default token. Saving the default must be the last step. If you make any changes to a token that you want to be there the next time you pull it out, you must re-save the default: Here is the wiki article on  Linking Tokens to Journals Here is a  video  which demonstrates the procedure

keithcurtis said: The token, not the token values, is re-appearing? The actual graphic?  I woke up today. Cleared cookies/cache. Disassociated all of the player tokens and then reassociated them. And the problem doesn't seem to be occurring again. But lemme tell ya, it was one of the weirdest things.  To your questions: No API scripts enabled, a few browser extensions (grammarly, adblocker, honey) but I don't keep them active on Roll20, I am using Chrome, and I did not try a private browser while the problem persisted. 

If it doesn't recur, I would suggest walking away, pretending it never happened, and maybe leaving a saucer of milk out to appease any ill-natured Fair folk. That was weird.

Everett Z. said: keithcurtis said: The token, not the token values, is re-appearing? The actual graphic?  I woke up today. Cleared cookies/cache. Disassociated all of the player tokens and then reassociated them. And the problem doesn't seem to be occurring again. But lemme tell ya, it was one of the weirdest things.  To your questions: No API scripts enabled, a few browser extensions (grammarly, adblocker, honey) but I don't keep them active on Roll20, I am using Chrome, and I did not try a private browser while the problem persisted.  If you have the third party tools don't use third party image hosting.  The buttons in the tools that show up by the default token and portrait that don't show up in chrome.  Roll20 doesn't like quota dodging.  You likely had a bunch of invisible default tokens and if you had the tools and changed the URL to a quota version of the image, it suddenly updated all the dragged out invisible token replacements to a bad url with the new image making it look like tokens were appearing but they were always there as bogus url tokens.  

I'm having this same issue. -The game isn't using any API scripts as far as I'm aware. -No browser extensions that mess with Roll20. -It happens even in a private browsing window. -I deleted my cache and cleared my cookies and it's still happening -I'm using Chrome.