安裝 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(越南文)
Українська(烏克蘭文)
回報翻譯問題
was that your first mission?
1a. No briefing at all. That's not really a problem but you should either set briefing = 0 so you load straight into the mission and get briefed there, or put something in the briefing to get a quick overview. It'd be nice to know what the target looks like for example. This saves people from being confused (that's what a briefing is for after all).
http://community.bistudio.com/wiki/Description.ext#briefing
1b. No map markers at all. You already mention the approximate location of the target and task a good overwatch position. Mark those for the briefing and diary.
2. Command refers to you as "Sniper Team". But I'm by myself? Add a spotter!
https://www.youtube.com/watch?v=A97iXLuxJvs&list=PLQEd6zRLOafX53dmxxugEoVNaJyC307fi&index=13
3. The extract chopper showed up right at the beginning and just kinda hung there.
5. The overwatch position was pretty crappy. No hard cover, no keyhole, just a bare hill that skylines you and was really close to the enemy.
6a. Like 1shot1kill_PL, the extract chopper flew off with me and just hung around at its final waypoint, never ending the mission. I had manually to end it.
6b. It's really not necessary to make the player do a helicopter ride if all you're gonna do at the end is, well, end it. Might as well run a script and call the mission end right after the chopper flies off with you.
Here's my entire playthrough.
http://www.twitch.tv/l3tuc3/b/501147242