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









Delete the 'installed_mods.json' and 'mods_enabled.json' files located in
C:\Users\[[YourName]]\AppData\Local\ZERO_Sievert,
then try running the game again
This resets the list of mods that apply to you. All excluded mods will be restored.
Sometimes, even though you’ve subscribed to a mod, it doesn’t appear in the in-game mod list for some reason. In such cases, reinstalling or deleting the mod won’t fix the issue. The files I’m suggesting you delete are the ones that record which mods are applied to your account and which ones are enabled or disabled.
Can you help me? I truly wish to have this mod
I set the probability to around 2~5%, but it feels way higher in practice
For now, I’ve cut the drop rate down to about half.
did you update the game?
Since the Saiga-12 is a weapon included in the base game, there shouldn’t be any errors if the October update has been applied.
of Alarm Event for alarm 11 for object obj_npc_parent:
Item "saiga12" not recognised
at gml_Script_trace_error
############################################################################################
gml_Script_trace_error (line -1)
gml_Script_item_get_category
gml_Script_item_get_trader_page
gml_Script_trader_unpack_to_loot_array
gml_Object_obj_npc_parent_Alarm_11