Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Gauges produce signals for themselves, as all other buildings. However, you can use "custom signals" broadcast needed signals to the whole settlement. It's what one of the signals templates does (the one with gauge on the image). You will give different custom signal name for every gauge, and this is how you can set rules on different gauges.
I would suggest you to make a very limited set of critical buildings where you need to keep at least one worker. And then make rules, based on the district population. E.g. "if > 40, then set workers 4", or "if < 20, then setworkers 1". Workplace priority is not yet supported, so this you need to set manually.
After reading your github wiki, with the disapopintment regarding the shortness of the signals/actions that can be utilised in the manual scripting and basiclly %80 of the operations can be configured via the constructor (plus the easiness of the usage), + EVEN USING CHATGPT to
check every one and each file in the github library where there might be very well be an operator that does such operations however not introduced in wiki section, as you have explained wiki is not always up-to-date:
MY JAW literally dropped when there was no operator that calls the sum of a good ,n that particular district, where u had bots, beavers , even beds, a building's input/output storage, but nothing that even resembles the global goods in the stocks...
Now u would suggest using signals for gathering the real-time stock value, but imagine having 56 (yes FiftySix) different sized water storage elements (plus additional that default storage types introduced thru mods where i definately lack the name-index of those storage items), imagine setting signals in each and every water related storage ONE-BY-ONE, than finally heading to the building that u would utilise this info to actions finally, yet again using AT LEAST 4-5 lines to manage your goal's introduction thru script names..... (meanwhile the FPS falling to half of its original simply panning thru all those buildings with INDIVIDUAL SIGNALS)
I would purely say & suggest:
NO THANK YOU VERY MUCH I WOULD RATHER KISS H*TLER'S FINGER THAT HE POKED HIS NOSE
Long story short:
We lack ".... District.Storage.<GoodID>..." that either sums up all storage regarding that good in that district automaticly OR simply calls the value on the top of the screen...
I am still amazed how you have missed such a great a brutally important function in the mod..
Notwithstanding; this is a monumentally significant mod that literally allows you to worry with the real-stuff in the game, rathewr than literally micromanaging stuff (especially when you forget to close floodgates right before a bad-tide, good luck withn rescuing the colony without cheatingv in the dev mod...)
Hence; THANK YOU AND PLEASE ENHANCE THE SCRIPT FUNCTIONS!
All The Best, a MSc Civil Engineer with utmost automation desire regarding ANYTHING in his life.... (hate redundant and time-wasting mini tasks)
The district level stock signals feature is tracked here: https://github.com/ihsoft/TimberbornMods/issues/80. This world has more than one smart person, you're not the only one who "figured it out". When I have time to start working on this feature, it will be done. I work on this project in my free time, so no promises on any dates or features.
- If (ne (sig Weather.Season) 'TemperateWeather') --> Then (act Pausable.Pause)
- If (eq (sig Weather.Season) 'TemperateWeather') --> Then (act Pausable.Unpause)
- If (eq (sig Inventory.OutputGood.Water) 1500) --> Then (act Pausable.Pause)
- If (le (sig Inventory.OutputGood.Water) 1400) --> Then (act Pausable.Unpause)
The problem is that if I'm out of a good season, and the storage of the pump is not full the building unpauses, even though I'm telling it to stay paused in that season.
Is there a way I've yet to find to put:
- an AND/& to these rules,
- the 3rd and 4th rules inside of the 2nd rule,
- give priority based on the order of these rules?
Thanks!