安裝 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（越南文）
Українська（烏克蘭文）
回報翻譯問題
討論區規矩與守則
2 
檢舉此篇文章
> Using the "code" field: This is a unique identifier that all text files in a mod must have so other game files can refer to it. The convention on these is to omit spaces and, if you don't do anything else, it will auto-generate an in-game name based on this field.
> Using a ".lang" text file: You can optionally include a language file with your mod that provides item names and descriptions using the 'code.name =' and 'code.description =' commands, respectively. This is the preferred method since you can use spaces, a broader range of characters, and separate translations for different language communities.
Since the latter is optional, you'll see a lot of mods which rely on the auto-generated names instead. If you'd like, you can add a .lang file to those yourself (or edit it if one exists) to rename all of the modded items more appropriately in your game client.
Thanks for such the in depth answer! It's really helpful! :) I'll probably end up using a .lang file because I know how to use them, funnily enough the idea never even occured to me... it's pretty obvious now I think about it lol... XD