安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
讨论规则及指引
1 
举报此帖
The commented line you're referring to is documentation on registration of new things, not tweaking existing things.
There is currently no convenient decorator-style way to tweak base-game things, so instead, you have to do it manually — this means, you'll have to do your modification in onInitialize, and undo your modification in onUninitialize:
Example:
All modification of base game content currently works the same way.
For more details on acceptable values for item descriptions or recipes, see:
IItemDescription[waywardgame.github.io]
IRecipe[waywardgame.github.io]
Or view the interfaces by Ctrl+Clicking on tokens in VSCode.
I've managed to modify a few recipes using those guidelines, but am not seeing a way to require a minimum tier when using ItemTypeGroup? Is that something that is possible with the current code?
If not, it looks like I can use a workaround that involves registering a new ItemTypeGroup that only consists of acceptable tiers, but I was hoping to avoid that.
Edit:
One other thing - Is there a way of tying new terrain types into the default generation instead of overriding it like in the Troposphere example?
For example, I'd like to add a new metal that will show up in veins instead of relying on a method hook to replace the generated terrain via RNG.