{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/2/2019 1:55:34 PM
10
That’s on Steam, not Bungie. Steam blocks anything. They blocked out the word “braw” before
English
-
Why are you posting this without any sort of evidence? How come I can play any Valve published game or post on their forums with my name as usual and it won't be censored? No, really, explain it to me. Explain to me how this is Steam's fault.
-
This is on Bungie. Not Steam. Steam allows these words to be written in it's own forums, which have their own filters, but not on Destiny. Destiny is the only game in my library that I have this problem with. The same goes for many others. [url=https://steamcommunity.com/app/1085660/discussions/0/1628539187762014311/?ctp=2]See here if you're interested how it's going on Steam Forums.[/url]
-
If it's steam, how come they let me set it as a username in the first place, without censoring. And it's not censored in any other games
-
If it was bungie, why did it not get censored before on Battle.net but suddenly get censored when they moved to steam?
-
That’s just how steam works. It’s stupid I agree. But I’m pretty sure they only stuff censor in online only games.
-
Im sure bungie must have a choice in this tho
-
Edited by Seth, Knower of Things: 10/2/2019 2:16:27 PMNot really. It’s their game sure but they have to abide by the T/C of steam. If steam doesn’t want certain words or phrases to appear online on their platform(no matter how stupid it seems), there isn’t much can do/say about it except that they’re sorry.
-
I have forwarded the same message to steam support cus this is ridiculous
-
Yeah definitely direct your anger towards steam. It is very stupid, but unfortunately Bungie has little say in the matter here. This is like the only thing they can’t control in D2 now, is what the platforms that host D2 ask/require.
-
https://ibb.co/LNt7kyg --- It's definately Bungie, not Steam, and Steam has little say in the matter here. Whereas Bungie has actually backtracked, and admits awareness of the problem now: https://www.bungie.net/en/Forums/Post/253740906?sort=0&page=0&path=1 Notice how they edited their post. They originally blamed Steam.
