In the character sheet, the player name is currently taken directly from the player's D&D Beyond login name (browser), or the D&D Beyond login name of whoever happens to be viewing it (PDF export). This is sub-optimal in a couple of scenarios, such as:
the DM knows the players by their proper names, and some players have unrelated cryptic D&D Beyond login names
the players manage their characters on D&D Beyond between sessions but the DM prints out paper sheets for use at the table
the players have no D&D Beyond account, but the DM uses D&D Beyond to maintain a digital copy of their character sheet for one reason or another
(I myself am currently running a campaign where all of the above apply.)
I hereby suggest adding a dedicated field "player name" or "player name override" to the character sheet database, to be displayed as the player name, and making it modifiable via the character editor.
In the "player name" variant, the field would initially default to the D&D Beyond login name, but tracked completely separately (caveat: when transferring a character to a different user, the initial creator's login name would "stick" unless actively edited). In the "player name override" variant, the field would default to an empty string, which would signal that the D&D Beyond login name is to be displayed instead (effectively resulting in current behaviour unless the field is actively edited).
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
In the character sheet, the player name is currently taken directly from the player's D&D Beyond login name (browser), or the D&D Beyond login name of whoever happens to be viewing it (PDF export). This is sub-optimal in a couple of scenarios, such as:
(I myself am currently running a campaign where all of the above apply.)
I hereby suggest adding a dedicated field "player name" or "player name override" to the character sheet database, to be displayed as the player name, and making it modifiable via the character editor.
In the "player name" variant, the field would initially default to the D&D Beyond login name, but tracked completely separately (caveat: when transferring a character to a different user, the initial creator's login name would "stick" unless actively edited). In the "player name override" variant, the field would default to an empty string, which would signal that the D&D Beyond login name is to be displayed instead (effectively resulting in current behaviour unless the field is actively edited).