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 (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
the numbers that I gave were being very liberal with my times: effectively 2 minutes to load the game from the executable/library (loading the game felt very front heavy, and after doing some memory profiling on it most things in this game seem to be rather memory efficient after initial creation), and 2 minutes to go through the results screen, evit the game, and wait for sync to complete (steam raises a hissy fit at times if this does not complete before the same game, or any game is launched). I did these considerations if the player is not playing this game on a very fast machine (though I do assume a faster internet connection)
so accounting for small math you were doing between 2, and 2.5 minutes per run your system must have a good performance setup
Used clonehenge on casual and took under an hour
not to mention by even having such a guide in a publicly viewable location means that any marketing statement from braging about such a thing is automatically called into question, and then this method could probably be replicated on any device that the date can be manually altered. calling the metric into question on all of it.