安装 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(越南语)
Українська(乌克兰语)
报告翻译问题








- Happy to help, thanks for making a great mod and maintaining it for all of us.
Do you think your fix will effectively disable moddable weather? Do you mean automation will stop responding to season changes? Or do you mean automation just won't offer options for addressing mod weather, like rain and monsoons?
v0.7.9.3-7f397d5-sw
InvalidOperationException: Unknown hazardous weather type: Drought (DroughtWeather - ModdableWeather.Defaults.GameDroughtWeather)
IgorZ.Automation.ScriptingEngine.ScriptableComponents.WeatherScriptableComponent.OnHazardousWeatherStartedEvent (Timberborn.HazardousWeatherSystem.HazardousWeatherStartedEvent event) (at <58c6e8f6a1a44ce3a11ce807ead48799>:0)
It's a bit sad that the constructor can only work for stock game seasons. Did you have to populate the season list manually? Is there some script or signal moddable weather's author could add to their seasons so that the constructor recognizes the new weather as a season automatically?