Visual Aids:
System Information:
Intel(R) Core™ i7-14700F
Expected behavior
When I say things that people pronounce fast like “Jupiter is a big gas planet”, I would expect me to not get moderated, as Jupiter IS a gas giant, and I was stating a fact saying It’s a big gas planet.
A similar thing to this like “Jupiter is a Big gas planet” could be "gamemode’, some pepole say it as gaymode or gammode
I don’t think this should be considered a bug because even in the single example you gave, you’re swallowing the ‘g’ sound in ‘gas’ while pronouncing it, and it sounds like you’re saying it the other way.
Not to mention, even YouTube’s subtitles pick it up that way.
It is an issue, I only had to read the title, and I know exactly what this is about.
An error in precision. Luckily this automation gives you a warning first. Depends on what games you play.
17+ compared to non-17+ acts a bit different.
They should add a cooldown on the warning button that says “Got It” though, maybe. There’s people I know that were clicking very fast on their screen, at the end they didn’t even realize what that pop-up said because they clicked so fast, the pop-up closed, because they clicked on “Got It”.
Hard to tell how it works. Based on the things I heard, it transcribes your text, so it’s basically like most of the Voice To Text things.
And then there’s apparently an additional factor that checks if two people are arguing, regardless if they’re saying something bad or not, but I don’t know, that’s just something I understood based on RDC. That they’ll issue a warning on both players. Can’t really say how that one decides that though…
I talked for hours about my childhood memories in voice chat, mentioned very tragic events, and not once was any action taken. I literally yapped for hours about everything, so I’d like to know how anyone gets moderated unfairly because I really tried and nothing happened. For instance, I can clearly see why the original poster in this bug report got moderated.
This is just an acknowledgment announcement!
We’ve filed a ticket into our internal database for this issue, and will come back as soon as we have updates!
Thanks for flagging!