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(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
In addition, having a group of sound blocks play and a group of lights activate and blink when oxygen levels in all tanks or a room get to low would be great. If it's possible to have the sound blocks and lights reset when a special light is turned off that would be awesome, the alarm could be activated manually via that light as well (either script or player activates light to sound alarm and deactivates light to silence/reset alarm).
I suppose the only way having the airlock system included in this would be to somehow make an exception for the airlock doors and vents that way the bulkhead system won't activate and set off the alarm.
For the oxygen generators and tanks, when the tanks reach normal levels after being at dangerous, toggle stockpile tanks back to stockpile (maybe have to set a tag on the tanks for that so the script can ID them, I'm not sure though).
I see no reason why all of what you described couldn't be combined into one script.
The Emergency Bulkheads feature would be very similar to my bulkhead door manager script as you said. I think it would just be a matter of removing a couple of lines of code to disable the opening of the doors and making it disable/enable the doors.
Once I get my menu code working, you could have multiple consoles on your ship that all give access to a LCD menu for the different statuses you mentioned. So from any terminal around your ship you could access the status of the emergency bulkheads, airlocks, and oxygen management by selecting that menu item.
Instead of using a prefix you could maybe just create a "Ship" group that contains all the blocks on your ship. That might save some time when naming blocks. You could do something similar with airlocks. So you could have a group named "Airlock 1" and another named "Airlock 2". The script could simply search for groups named like Airlock* and then in each of those find the components that make up the airlock, like the air vent and doors. Maybe tagging the doors with [inside] and [outside] or just adding [hull] to the outer door that has space on the other side so the script knows which doors to open/close. It could easily handle multiple airlocks.
It's pretty easy to play sounds or flash lights when certain events occur.
I haven't looked into reading the value of the oxygen stockpile yet but I'm sure it's possible. You can keep track of the current state of the tanks inside the script so there should be no reason you would need to change the tags on them other than to initially set them as stockpile tanks.
Everything you have mentioned adds up to a pretty complicated script. However, each individual piece is not that complicated. It might be best to at first create the three pieces separately (in different scripts) and then, once they are working, combine them into one script.
I hope that is helpful. I'm not sure what kind of help you are looking for but I'm happy to give some examples and answer any questions you have. I'm pretty busy during the week but I'll reply when I have time. Have you looked at my EasyAPI Documentation guide? That might be the best place to start. If you were hoping I would write the script for you I might be able to do that eventually since I am interested it something like this, but I have a bunch of features I am working on for EasyAPI so it will be a while before I have time to work on something like this.