I recently purchased some content and a master tier subscription on this site so I created a campaign to see how content sharing works. I created the campaign, sent a link to a friend that was going to help me and they had to add a character to the campaign. After they did so, we tried to see if they could create a new character using the content I had purchased and we couldn't figure it out. I created a character to see how the claim feature worked, and after a bit the character wasn't updated at all and it was seen by the site as a completely blank character. My friend asked if I could remove their character from the campaign and they would join again to see if it worked. Right after I removed the character, that character was added to my character sheets and removed from theirs for some reason. Does anyone know why this happened?
There's an issue going on right now where if you (the DM) Remove a character from your campaign, it goes into your characters.
You can give it back by readding it to the campaign, Unassigning it, and then letting your friend join the campaign with that unassigned character. Then they can Leave the campaign and keep the character.
Rollback Post to RevisionRollBack
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
There's an issue going on right now where if you (the DM) Remove a character from your campaign, it goes into your characters.
You can give it back by readding it to the campaign, Unassigning it, and then letting your friend join the campaign with that unassigned character. Then they can Leave the campaign and keep the character.
It's not an issue, but claim of ownership.
The claim of ownership happens by the person that is removing it, be it the DM or the player. In the case with OP as DM they are removing the character from the campaign, which then gets it added to their Character list. It stops duplicates of that character happening since each character is given a unique identifying number, which you see if you were to save it as a PDF, share it as a link, or open the character into its own browser tab.
However, when its attached to the campaign, the rights to edit are given to both DM and the owner. That is again comes down to a unique identifying number attached to the campaign itself. Much like rights given to cloud documents on who has access and editing rights to a file. So as with such cloud documents, if someone was then to move that document to their own personal account it disappears from being visible to everyone since its no longer within the shared folder. Which is what happens with a character sheet within the campaign.
So, when it comes to the character itself being removed, it goes to the personal space that the person owns that removed it. Whether its the player, or the DM. So if the DM removes it from the campaign folder, its no longer visible to anyone.
That also means it cant be duplicated between two accounts, unless the person that has it in their personal space copies it, therefore creating a new unique identifying number, and puts either of the two back into the campaign.
...I'm not sure I follow. Is this always what has happened when a DM clicks "Remove"? I don't think so. Also, a person who made another thread Removed a character from a campaign and wound up with more characters than they could have, leaving them with everything locked up. How is this not an issue?
Rollback Post to RevisionRollBack
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
...I'm not sure I follow. Is this always what has happened when a DM clicks "Remove"? I don't think so. Also, a person who made another thread Removed a character from a campaign and wound up with more characters than they could have, leaving them with everything locked up. How is this not an issue?
When the DM clicks remove they are removing the character from the campaign to their OWN folder. Them removing it is claiming ownership. That is not an issue.
The second one is a completely different issue again. If a person removed a character from a campaign and they ended up with more characters than they could/should have, and everything locked up. That issue is would likely caused due to them having a free account and them EXCEEDING their character count. While the character is in the effective shared folder on the campaign, it isnt being counted towards their actual account, that happens because initially the character got created by someone else, and then that person deactivated the character, therefore allowing it to be unassigned. The unassigned character stays attached to that person's account, until someone else assigns it as their character, then it is moved from the person that created it, to the person claiming it to play, however its still within the campaign.
Now, while that character is in the shared area of the campaign, where either the player or DM can edit it, this message when you deactivate shows up:
"Are you sure you want to unassign this character? If the character is claimed by another player in your campaign, you will no longer be able to edit that character unless you are the DM of that character's campaign."
The reason that shows up is as per what I just said above. The character is no longer in your account's access once claimed by another because its been moved to their account, and as said if it's not being counted towards a FREE account's total character count while within the campaign, but does get counted once they remove it, therefore if they are at max character count already it tosses them over that and is causing their account to get locked up, that may also be happening due to a character being made in the shared space using resources normally not available to the person with the FREE account because they dont own the content.
The fix for that could be as simple to fix by simply putting code in to check a FREE accounts character count and if they are at their account limit to not allow them to claim any characters within a campaign as their own to play, it instead throws up a popup box informing them they are at their max limit of characters. Now I dont know if that is happening already since I am on a Master tier.
This is indeed an issue; the DM removing a character should not claim the character. What should be happening is that when the DM clicks 'Remove', the character is removed from the campaign but remains under the control of the current owning player.
I recently purchased some content and a master tier subscription on this site so I created a campaign to see how content sharing works. I created the campaign, sent a link to a friend that was going to help me and they had to add a character to the campaign. After they did so, we tried to see if they could create a new character using the content I had purchased and we couldn't figure it out. I created a character to see how the claim feature worked, and after a bit the character wasn't updated at all and it was seen by the site as a completely blank character. My friend asked if I could remove their character from the campaign and they would join again to see if it worked. Right after I removed the character, that character was added to my character sheets and removed from theirs for some reason. Does anyone know why this happened?
There's an issue going on right now where if you (the DM) Remove a character from your campaign, it goes into your characters.
You can give it back by readding it to the campaign, Unassigning it, and then letting your friend join the campaign with that unassigned character. Then they can Leave the campaign and keep the character.
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
It's not an issue, but claim of ownership.
The claim of ownership happens by the person that is removing it, be it the DM or the player. In the case with OP as DM they are removing the character from the campaign, which then gets it added to their Character list. It stops duplicates of that character happening since each character is given a unique identifying number, which you see if you were to save it as a PDF, share it as a link, or open the character into its own browser tab.
However, when its attached to the campaign, the rights to edit are given to both DM and the owner. That is again comes down to a unique identifying number attached to the campaign itself. Much like rights given to cloud documents on who has access and editing rights to a file. So as with such cloud documents, if someone was then to move that document to their own personal account it disappears from being visible to everyone since its no longer within the shared folder. Which is what happens with a character sheet within the campaign.
So, when it comes to the character itself being removed, it goes to the personal space that the person owns that removed it. Whether its the player, or the DM. So if the DM removes it from the campaign folder, its no longer visible to anyone.
That also means it cant be duplicated between two accounts, unless the person that has it in their personal space copies it, therefore creating a new unique identifying number, and puts either of the two back into the campaign.
...I'm not sure I follow. Is this always what has happened when a DM clicks "Remove"? I don't think so. Also, a person who made another thread Removed a character from a campaign and wound up with more characters than they could have, leaving them with everything locked up. How is this not an issue?
Helpful rewriter of Japanese->English translation and delver into software codebases (she/e/they)
When the DM clicks remove they are removing the character from the campaign to their OWN folder. Them removing it is claiming ownership. That is not an issue.
The second one is a completely different issue again. If a person removed a character from a campaign and they ended up with more characters than they could/should have, and everything locked up. That issue is would likely caused due to them having a free account and them EXCEEDING their character count. While the character is in the effective shared folder on the campaign, it isnt being counted towards their actual account, that happens because initially the character got created by someone else, and then that person deactivated the character, therefore allowing it to be unassigned. The unassigned character stays attached to that person's account, until someone else assigns it as their character, then it is moved from the person that created it, to the person claiming it to play, however its still within the campaign.
Now, while that character is in the shared area of the campaign, where either the player or DM can edit it, this message when you deactivate shows up:
"Are you sure you want to unassign this character? If the character is claimed by another player in your campaign, you will no longer be able to edit that character unless you are the DM of that character's campaign."
The reason that shows up is as per what I just said above. The character is no longer in your account's access once claimed by another because its been moved to their account, and as said if it's not being counted towards a FREE account's total character count while within the campaign, but does get counted once they remove it, therefore if they are at max character count already it tosses them over that and is causing their account to get locked up, that may also be happening due to a character being made in the shared space using resources normally not available to the person with the FREE account because they dont own the content.
The fix for that could be as simple to fix by simply putting code in to check a FREE accounts character count and if they are at their account limit to not allow them to claim any characters within a campaign as their own to play, it instead throws up a popup box informing them they are at their max limit of characters. Now I dont know if that is happening already since I am on a Master tier.
This is indeed an issue; the DM removing a character should not claim the character. What should be happening is that when the DM clicks 'Remove', the character is removed from the campaign but remains under the control of the current owning player.
I have passed this issue along.
Find my D&D Beyond articles here