Issues with Duplicating Characters

I'm using the Duplicate Characters functionality quite a bit (via Character > Edit > Duplicate; from a template high-level character, making a duplicate for each player that they tune to taste). The master sheet has an attached default token, with several token settings in place (represents the given character, token bars linked to attributes, player permissions set to taste). I'm running into two related surprise issues when I use the duplication facility. I'm hoping someone can explain why it works this way, or confirm if there's a bug? Duplicated Token Represents Original Character & Attributes Delinked At the moment of duplication, the new PC's token still "Represents Character" to the original source character. Also, the Token Bar linked attributes are broken (reset to "None"). I would think the more obvious thing is to link the copied PC's token to the new PC, and keep the attributes linked (to the new PC). Why doesn't this happen? Token Bar Player Permissions Reset on First Token Drag to Map At the moment of duplication, the new PC retains the Token Bar Player Permission Settings (e.g., some have Edit on, others off). But once the new PC's token is drag-dropped from Journal to Map, then the Player Permissions are all reset to have Edit: on in every case. Note that other edits don't trigger this same permissions reset (changing PC name, player, represents character, attribute linkage, etc.) I don't see any reason why Player Permissions should be reset on the first token drag-drop of a duplicated PC. Why does this happen?

Hi Daniel,  Yes, PC tokens would still represent the former character. You need to reset the token to the new character. That is normal behavior.  Token Bar Player Permissions reset: As with the first point, make sure you edit the token and set it up after duplicating the character. Then make sure you set the token to the new character when you are done, otherwise it isn't saved to the character. 

As Gauss stated, what you are seeing is not a bug but the intended behavior. I personally find this behavior annoying, as well as the fact that the duplicate character or NPC sheet is always sent to the bottom of the journal . I very often drag an NPC/Monster from the compendium and duplicate it to make a custom version (A Custom Compendium would be handy for this, but that's another issue). Having to reset the token's ownership and redefine the token bars every time is a pain. Having the duplicate's token call back to the original has IMO very limited usefulness. If you decide to post a suggestion to change this behavior, you'll have my vote. Daniel C. said: I'm using the Duplicate Characters functionality quite a bit (via Character > Edit > Duplicate; from a template high-level character, making a duplicate for each player that they tune to taste). The master sheet has an attached default token, with several token settings in place (represents the given character, token bars linked to attributes, player permissions set to taste). I'm running into two related surprise issues when I use the duplication facility. I'm hoping someone can explain why it works this way, or confirm if there's a bug? Duplicated Token Represents Original Character & Attributes Delinked At the moment of duplication, the new PC's token still "Represents Character" to the original source character. Also, the Token Bar linked attributes are broken (reset to "None"). I would think the more obvious thing is to link the copied PC's token to the new PC, and keep the attributes linked (to the new PC). Why doesn't this happen? Token Bar Player Permissions Reset on First Token Drag to Map At the moment of duplication, the new PC retains the Token Bar Player Permission Settings (e.g., some have Edit on, others off). But once the new PC's token is drag-dropped from Journal to Map, then the Player Permissions are all reset to have Edit: on in every case. Note that other edits don't trigger this same permissions reset (changing PC name, player, represents character, attribute linkage, etc.) I don't see any reason why Player Permissions should be reset on the first token drag-drop of a duplicated PC. Why does this happen?

I agree that this behavior is unintuitive, and though it does have use cases, they are probably outweighed by the benefits a change would bring. The reason it does work this way is that a default token is essentially a little datafile of its own (technically a JSON string), with all the settings internal to it. If you duplicate a character, it duplicates that default token "file" exactly, including the part of it that says what character sheet it points to.