Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Support used to try and help push them through manually checking through Support tickets years ago but they stopped doing that. They probably don't even have the ability to do it anymore, as if Valve no longer allowed them to.
They need to change it so that it only reviews the content when publishing and after publishing. Or at least make it so that sections are reviewed individually, that way we can work on the rest of the guide while one section is being checked.
Content moderation is good, but the automated system is too strict or has too many false positives. If it starts locking unpublished drafts after every saved change (as it often does), then guide authorship becomes impractical or even impossible.
Already, discouraging users from saving a draft is bad. Doing so is even worse here because each section has to be saved before working on another.
It would be better for the system to hide or flag the final, published guide instead of drafts. This would be more in-line with how the system moderates game reviews and forum posts. In the case of suspicious links, scrubbing or hiding them would also be a good, consistent alternative to locking the entire guide.
It'd also be nice if automatically reported UGC worked like reported forum posts, where the user can still edit and delete their own content and it just stores a second copy of the reported content as part of the report.
I had a player write to me today, worried that I had banned their UltraKill-inspired skins for a game I work on, and basically all I could tell them is that they should either wait for the weekend to be over (when hopefully the flag would be cleared by a global moderator) or try re-uploading the mod with a title and description that had fewer words in it that would scare the content analysis robot.
There's also a community-made game mode that's distributed with the game called Infection Deathmatch, and even though it's a mod of deathmatch mode which means the second word is redundant, I had to insist that guides always use both words to refer to the game mode because otherwise the content analysis engine would decide they were talking about scary gross medical stuff rather than a video game.
I'm also a vivid guide writer (not just for games) and you may have guessed it: today I also got hit with the 'dreaded' Error code 15.... the main problem is that it can become so darn demotivating because here you are... full of inspiration and then wham. End of the line for no apparent reason.
As I mentioned in my previous suggestion: I'd rather wait a whole week for a thorough inspection of my guide before publishing (or sharing) vs. getting locked out in the middle of my work.
I'm probably going to try and take another route (= new guide, and remove what I have now) but... it's just frustrating. Also... no threat or anything (!!) but if stuff like these keeps happening... then I can't help wonder if I'm even going to continue bothering.
But before that I'm going to see if I can finish my Word macro / template; been working on a code snippet which allows me to "translate" the formatting of a Word (365) document into Markup and/or BBCode.
This should allow me to just write my guide in Word, click the button and then I can simply copy/paste all the snippets back into Steam, but for now this is work in progress.
(edit: making a new guide & just copying my contents over (except for the 'open url') actually worked..)