D&D 5E: srd monster linked to token doesn's save the association sheet-token

Hi, I have this annoying problem: when I drag into the game a monster from SRD, and I edit it to link it to a token, when I drag it into the game from that moment it will place only the token, unlinked from the monster sheet. It's absurd, since I'm dragging the sheet into the map. I have to manually link each token dragged into the maps from the sheets this way, to it's sheet itself. I'm doing something wrong? Thank you.

Make sure you are going through the steps of linking a token in the correct order.&nbsp; This wiki article should work to step you through it. <a href="https://wiki.roll20.net/Linking_Tokens_to_Journals" rel="nofollow">https://wiki.roll20.net/Linking_Tokens_to_Journals</a>

I did all the steps: 1) drag item (es: commoner) from compendium (i have only SRD, not any manual purchased) to map 2) select token of commoner (es: dwarf miner) on the map 3) edit commoner sheet, clic on "use selected token" 4) rename commoner sheet to "Dwarf Miner", save and close sheet 5) open token 6) link token to dwarf miner sheet via combobox 7) save and close token Now, dragging the Dwarf Miner sheet from my journal to the map, will create only the token, unlinked from the sheet.

....ok I got the problem. But let me say, it's poorly made... Apparently, order of action matters. If I first link token into sheet. and then link sheet into token, it doesn't work. If i switch the order of these actions, I get a sheet that mantains the link between token and sheet when I drag it on the map. Nonsense to me, as a user and a software developer, but ok. Thanks for the wiki :-)

Luke85 said: Nonsense to me, as a user and a software developer, but ok. Thanks for the wiki :-) When you set the "default", that is exactly what it means.&nbsp; The token as it is at that moment is what will be dragged out from the journal.&nbsp; Any edits you make to the token after that are for temporary changes that are map/situation specific that you don't want to be the default.&nbsp; It is pretty simple.

There are good reasons it is made this way. It lets you make instances after the fact that do not propagate back to the default. In other words, you could name the tokens "Goblin 1", "Goblin 2", and so on, without changing the default. Otherwise the next time you dragged out a fresh goblin, it would have the last name you gave a token instance. Saving as Default is like taking a snapshot, or saving a file. You can do anything you want to the copy without messing up the original. If you need to make a change in the original, just save over the old one.

I get the difference between the two cases, of course they are important to distinguish. I'm just saying that the method implemented here it's just not that intellegibile at user interface level :-) As a frontend developer, I would have chosen a simple combobox, or radio button group, to let the user clearly choose between shared instance and multiple instances (like passing a variable as reference or as value in computer programming), instead of forcing to do some steps in an order or another. But it's just my opinion :-P

Basically something like a "Save as new default" button next to the "Save settings" and "Cancel"? Intriguing. I know there is something similar to this in the VTTES extension, but IIRC, it's a whole new panel. Such a control would be worth exploring. If you want to make a Suggestion in the Suggestion Forum, I'd vote for it.