Up-Votes Needed Blank Character Name Bug — Name Restore/Change Token Misapplication

M

Mxkekxng

Well-known member
Issue Summary:
Bug with the DCUO name change / restore system resulting in blank character names and name-token misapplication.

What Happens:

  • A character name restore or name-change token process gets interrupted (e.g., cancelled mid-action, connection hiccup, or navigating away too early).
  • This leaves the character with a blank name instead of completing the restore/change.
  • If a name-change token is used afterward on the blank-named character, the system may show a "successful" confirmation — but the new name gets applied to a different, unrelated character instead of the one that used the token.
  • The token is consumed regardless, even though it didn't affect the intended character.
  • The originally affected character is left permanently blank-named, with no way to self-correct.
Effects:

  • Loss of a paid/earned name-change token with no name change actually applied to the correct character.
  • Blank-named characters may persist indefinitely, affecting league rosters, LFG listings, and social interactions where a name would normally display.
  • Possible cross-account impact: names can end up transferred onto unrelated/inactive characters that never requested a change.
Request:
Please investigate the interaction between the name restore/change flow and interrupted requests, and provide a way to manually correct blank names or reverse mis-applied name changes for affected players.
 
M

Mxkekxng

Well-known member
Additional Comment:

I also want to flag a related issue I've noticed: when a name-change token is used to set a character's name to one that is currently blank/unclaimed, the system may end up assigning that name to a different blank-named character than the one the token was actually applied to.

This suggests the name-reservation logic may not be correctly binding the token action to the specific character initiating the change when the target name has no prior owner. This seems like it could be a broader issue affecting any name-change onto a currently-unclaimed name, not just the specific case in this report, and I'd recommend looking into whether the name-assignment step is validating against the correct source character or just grabbing the first/any blank-name match in the database.
 
You must log in or register to reply here.
Top