安装 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