安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
Now the problem is, after the update yesterday, the game doesn't even start for me anymore. No idea what happened, if it is spyware or whatever the hell, but this is not normal and no matter if its a false positive or not, I won't leave anything up to chance.
If you reading this do the same or not, is up to you. I will only play the game again, when they fix this issue, until then I play something else and keep this game off my harddrive.
I really liked this game so far and already spent a lot of time on it, but it's not worth the risk, even if I may sound stupid. (Also I really hope my savefile isn't gone, I do not have time to replay 25 hours that I sank into this.)
Situations like this are not "relatively common" as the dev's official post here manipulatively states. It is a result of studios/publishers cutting corners in the development process. Full stop. That is the reason. It doesn't "just happen", because if it did the dozens/hundreds/thousands of games that release each year would invariably produce this situation far more commonly.
Before you cite some other INDIE (keyword there) game that has had this happen in recent memory, keep in mind that this situation is essentially exclusive to indie/smaller studios and a AAA game will not have this happen. This is because AAA games have an established QA pipeline in place to specifically ensure things like this don't happen.
Smaller studios/publishers run into this issue when they skip code signing certificates because they don't want to pay the fee for them, or push builds out as soon as they get them working WITHOUT running it through QA first, or just lacking QA as a whole and use the community to sniff out bugs for them so they can enact "community driven" updates and development (aka, pushing playtesting/QA onto the player to save money).
Personally, I don't give studios a pass when something like this happens, as they aren't really innocent in it's occurrence. It happened for a reason, and that reason is a lack of the proper steps in place to specifically catch and prevent this, something that has been common, baseline practice for the past 30+ years. It's only relatively recently, when the bar for entry as a game studio has been lowered so that indie's can join the industry, does this happen, usually due to the indie flying by the seat of their pants and not following the proper protocols.
The studio should be thoroughly embarrassed that this happened, but it seems they are taking the low road and instead are trying to present this as nothing more than a consequence of doing business, a "relatively common" issue that just *happens*, not because of any reason in particular. The universe just happened to select their game to have this happen to. Poor, poor developer! We should have sympathy for them and give them a free pass, not hold them accountable for their corner-cutting.
lmao, what an absolute joke.
refund bro
Would if I could, more than 2 hours playtime and steam rejected my refund request.
Game looks great but I am bit sceptical as I never had any steam game flagged before, so would prefer to buy it once it is resolved.
Closing and archiving this thread.