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






Is it posible to use the code on a mod with more then one ModID, but it has the same Workshop ID ??
fwiw I'm using both the autotsar mods, and the MH Armored MK II in my game. it seems that if you log into the game while in the MH MK II it causes a bunch of errors for the Tsar complete library. it doesn't seem catastrophic.. when I left the MH and relogged the errors went away.
(by which I mean errors despite identical files, which would normally pass this inspection method.)
This is perfectly fine to do until you decide to be a goofball about it and make your amalgam of other people's tweaked and probably horribly outdated mods public
I tend to instruct my friends to just drop whatever pack i write up to their mods folder instead of using workshop, then yeet it when they gonna play elsewhere, apparently yielding great success.
@iBrRus guide looks good - thanks! I will check on the merging of the list this weekend.
Which is exactly how you create and keep outdated mods in circulation. One month into PZ MP there were automated tools for reboots available for everybody but a year later the workshop is still full to the brim with these packs and the comment sections of the originals even fuller of people reporting issues that have been resolved weeks or months ago. In most cases they aren't aware of this so it is rarely their fault, but it wastes time for the people who get bombarded with "does not work" style "bug reports" anyway.
If you have any suggestions for fixing/improving this guide, write them in the comments.