安装 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(越南语)
Українська(乌克兰语)
报告翻译问题









I think that @Brett himself will decide who to ignore and who not and he does not need your instructions.
I have passed on my experience to author, not for you.
@Brett Maybe I'm wrong, but as soon as I disabled this mod, the problem I mentioned below disappeared...
You again mickey? Brett, please ignore him.
He shows up in every comment section and always bothering the authors.
I have already blocked him. ;p
Here example: if player you opened a mission in the editor and launched it, then when you exited the mission, you get to an empty map (without your) mission and the editor loads your mission again. Sometimes an additional (double) editor loading occurs if first the player first time tries to load a mission. This is what happens. The player has selected a ready mission, pressed "open" But instead of a mission, an empty editor will open and then the mission will load a second time.
In any case, I did not notice any super fast noticeable loading of attributes. For this reason, the mod creates more problems than solves them.