安装 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 don't know if the Walrus Town is caused by this mod, but it's crazy. Like 16 or so McTusk igloos together. Never seen that before ever.
Also to the mod's design, I personally found in my testing that adding additional instances of biomes worked significantly better in my opinion for successful world gens vs larger biomes; for those who call for many/a specific set piece also, allocating space for 2-4 more of a biome to spawn worked quite efficiently at avoiding crashes and making sure the number of set pieces requested were accomplished :) Another issue is also set pieces are not duplicated in a biome, for instance there wouldn't be 2 reed traps in the same swamp biome; because of that, adding more reed trap set pieces in the world requires adding biome tasksets, if that makes sense.
I may consider your methodology more broadly and to a limited extent, but at the moment I think the mod is in an okay place design wise, I'll think on it some more though :)
base = task.room_choices["LightningBluffLightning"]
task.room_choices["LightningBluffLightning"] = base + 2
end) or does worldgen care more about how many biomes there ar rather than how big each one is? good modding
I hope you can manage to do it in the future
Ty for answering