Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Character Token not assigend

Can you please fix the issue where characters/reskinned/duplicated monsters maintain their Represents Character? It takes alot of time to have to keep reassigning the characters to their tokens and to mobs. Its bad enough with all of the other usual crashes/issues we experience. I have added the character several times and when I log out and back in I have to di this all over again. I want to run my game not have to deal with this every session. This has been an issue for some time and I cannot be the first to report this as an issue.
1663627532
Gauss
Forum Champion
DM Mularki said: Can you please fix the issue where characters/reskinned/duplicated monsters maintain their Represents Character? It takes alot of time to have to keep reassigning the characters to their tokens and to mobs. Its bad enough with all of the other usual crashes/issues we experience. I have added the character several times and when I log out and back in I have to di this all over again. I want to run my game not have to deal with this every session. This has been an issue for some time and I cannot be the first to report this as an issue. Just to confirm, are you saving the token settings?  Are you then saving the token to the character?  Also, are you using any APIs? Some of them can interfere with token settings. 
Hi Gauss, thanks for the reply, I have assigned and saved, multiple times. The only API on the game I am setting is Dungeon Master Tools.
1663632102
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
Hi DM Mularki! There are several ways to interpret exactly what's happening here. Can you give step-by-step reproduction instructions? This sounds more like a procedural error than a bug.