I believe the name change policy needs adjusted.
1. Provide a name change token if a name is moderated. You can limit tokens going to repeat offenders if you feel the system will be abused.
2. Provide clear information to the user about the alleged violation so they can avoid accidentally repeating the offense, and if you cannot do this, publish a list of prohibited terms and phrases that users impacted by name changes and/or prospective users creating a new account can review. Broad suggestions to not use the same name or risk being moderated again are not helpful if the user has no idea which part of their name was moderated.
3. Provide name change historical data to a user's profile so they can verify when a name change has occurred. This helps establish timelines for the potential catalyst if there is an issue somewhere.
4. Historical data should show if a name change was automated, automated with peer review, or human initiated with peer review (all name moderation decisions should have some sort of peer review to prevent abuse by disaffected employees). This can be tagged automatically based on how the report and peer review were handled. If you allow changes prior to peer review, the tag should indicate that a peer review is pending.
5. Allow appeal of name changes and/or of terms included on the prohibited list. If you want to limit appeals, restrict them to users whose accounts have a certain age and/or to names that have been in place on the service for a minimum amount of time. This should filter out a large number of appeals for flagrant violations of policy, most of which would be captured upon account creation or initial visits to Bungie's worlds or forums.
Why should these changes be made? While I understand the need for moderation, as well as the reticence to offering up justification or details why the majority of names may have been reported and changed, preventing targets of said policy from requesting appeal or review is inherently problematic. This is especially true when it is also coupled with a limited use name change system where tokens are offered sporadically over vast spans of time and when the user impacted by said policy may not be aware of what the violation is which risks them repeating it.
As recently as last year, changes to the automated filtration process caused a large number of players to have names changed. That bug was reported as fixed, but any suggestion that there could be an additional issue has been met with dismissal. I've had lack of apparent reports cited as equivalent to a lack of an issue when the two are not related (there can be problems without large impact; there can be large impacts without singular problems). Mistakes get made all the time and the reach of their impact is always going to differ.
Case in point, my Bungie name was (recently, I believe; see item 3 above) changed. I suspect it was flagged somehow as part of entrance into the Marathon Closed Technical Test. At least a handful of others admitted to the test reported the same. In those cases I saw, there were no obvious name or conduct policy violations. One user also cited that a developer team member ultimately corrected their name (mind you, I have no way for me to confirm this), which could suggest a systems issue. I added that I was impacted to an open bug report thread about this, but when I was not sure if that was getting further examination, I also opened my own. As I have not received a response from the Marathon team, I posted in the Help forum (Website Companion as there was no Bungie.net specific forum), but the moderators -blam!- offered only blanket statements about the name policy and complete dismissed the possibility of there being a potential issue in the system. They also suggested changing my name IF I had a token, and to not use the same name or risk repeat offense. Without knowing what the offense was, however, the only manner to do so is to avoid all possible combinations of letters from my prior name. Users with longer names or names that include more common letter combinations could make this especially problematic. Additionally, since there is apparently no data shared or available to the user or the moderators that indicate when a name was changed, what reporting mechanism was employed, or whether or not it was human peer reviewed or fully automated, etc, they have no evidence to support or dismiss the possibility of a systems issue.
My name has been in use across multiple platforms for nearly 30 years, gaming or otherwise. I can't say for sure, but I'm pretty sure I used the same name with Bungie since the launch of Myth TFL back in the day. I've never once had it moderated or been told that it is offensive or the like, by users or platforms. It does not contain PII, and to my knowledge includes no known religious references, hate speech, etc. Any matches to filtered terms should be coincidental at best. A human report seems unlikely as I have not been active on Bungie games since roughly June or July of 2024. As I noted above, I suspect that my name was flagged by the automated filtration check for unknown violation as part of being admitted to the closed technical test for Marathon. It was updated before I had even entered a match. The moderation team says it was human reviewed, but I'm not sure they can confirm this. After 30 years of use, being told I have no recourse to support use of my longstanding gamer tag/alias is frustrating. If I were a content creator, I feel like this would already be reviewed and a response given, but alas, I've only been a Bungie customer for the past 32 years.
Anyway, please consider updating your name policy with the suggestions provided. I'm not against changing my name, 30 years in use or not, if it really is somehow offensive or in violation, but having zero avenues for appeal, recourse, or even meaningful data to avoid repeat offense is unacceptable.
Your role as a moderator enables you immediately ban this user from messaging (bypassing the report queue) if you select a punishment.
7 Day Ban
7 Day Ban
30 Day Ban
Permanent Ban
This site uses cookies to provide you with the best possible user experience. By clicking 'Accept', you agree to the policies documented at Cookie Policy and Privacy Policy.
Accept
This site uses cookies to provide you with the best possible user experience. By continuing to use this site, you agree to the policies documented at Cookie Policy and Privacy Policy.
close
Our policies have recently changed. By clicking 'Accept', you agree to the updated policies documented at Cookie Policy and Privacy Policy.
Accept
Our policies have recently changed. By continuing to use this site, you agree to the updated policies documented at Cookie Policy and Privacy Policy.