安装 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 tried moving that ugc_mod folder (which is just the mod ID number without the "workshop-" at the beginning to the mod folder with workshop- attached, but no luck so far.
Perhaps just using a full path to the mod in the ugc_mod folder in the modsettings.lua file would work? I'll try next time my friends and I are done with the running server and I can test it.
Locate the Cluster folder that contains your "Master" and "Caves" (if you're using Caves). If you're not using caves, create a file called "modoverrides.lua" in "Master". If you are using Caves, place it in the "Caves" folder (only one of the two folders, not both). Then in that file, place the following:
return {
["workshop-791838548"]={
enabled=true
}
}
You can Google modoverrides.lua if you want to see further syntax and options (particularly if you're adding more than one mod in this fashion).
This apparently is the PROPER way to add mods as it is done in the standard GUI version of the game. The method I learned initially with the forcing commands is just one way to do it, but not exactly the correct way unless you're using unpublished mods that are a work in progress.