{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
9/20/2017 5:23:45 PM
3
@Miss__Scarlet @xPipxPsx4s
So I had "lemonparty" (don't ask) and "pre-pubescent" in the About Us section and replaced both of those. Changes took after that.
Still would be nice to know what words are flagged.
English
-
Lmao @ "lemonparty" I'm glad you got yours fixed! Thanks for the update. I'm not sure that there's anything I've tried to post in the clan description that could possibly be flagged, but I'll play around with it some more. My error is a little different than yours was, though, as mine is claiming the clan name is already in use, not that it's unacceptable. Ughhhhhh, so annoyed right now.
-
Okay I changed the clan name right before migration, but the old name still gives me the "already in use" error as it's still also a group (I tried changing the name before changing lemonparty occurred to me). The detail is in the URL. Did you change anything right before migration?
