订阅以下载
Room Control Program v1.0

This script provides you an alternative UI to control room pressures and doors instead using the K-menu.

You can use screens to monitor the rooms’ pressure and its vents and doors.

An automatic airlock, hangar and an door control are included.


With the Control Program scripts I want to create a way to build a real control room or bridge with consoles to control the whole ship or station. By using the included automatic resource management of the scripts you will have more time for engineering your next build.

The main features of the Room Control Program

• status screens to monitor room pressure and door and vent status
  
• control screen to watch and change all rooms, doors and vents
  
• airlock screen to show information about an airlock
  
• doors are sealed automatically if the other room has no pressure to prevent open them by mistake
  
• doors to pressured rooms close automatically if a room looses pressure
  
• automatic airlock control makes an airlock easy to use like an elevator
  
• supports rotating lights as warning lights in low pressured rooms
  
• automatic hangar control reduces the room pressure before the hangar gates are opened and pressurizes the hangar after all gates have been closed again
  
• automatic leveling of the oxygen tank to prevent a tank connected to an airlock from becoming completely full or empty
  
• all automatic controls can be turned on or off for each room through the user interface of the control screen
  
• could be controlled by the H2O2 Control Program control screen

First steps:

When the code is loaded to a programmable block you only have to enter two setting values.
The first setting is the maximum number of separated conveyor systems in your grid. Two systems are separated, if there is no connection between those systems.
The second is the list of room names. Internally, the script works with room numbers. You can match these numbers with room names. If the name contains "Airlock", the script will treat that room as an airlock. If the word “Hangar” is part of the room name, that room is treated as a hangar.

With default settings the script analyses the grid to find connected blocks.
If you are using merge blocks to connect seperate ships or stations you need to enter a specific name. Switch "scanConstruct" to false and enter a name/phrase between the quotes at "gridName". Each block of your grid has to have this name/phrase in its custom name.

The custom data field of the blocks is used by the script for all the block specific setup information. All information are given in the custom data field. It is very important to set up all blocks with the room number that the block is in. For doors, the two room numbers that are separated by the door must be specified.

To use the script to control your airlocks and hangars those rooms have to have a specific setup:
Airlocks:
An airlock needs at least two doors leading into to different rooms. Of course one of those different rooms can be the outside atmosphere. Additionally you have to build at least one vent to control the airflow of the airlock and you have to build at least one sensor to tell the script when you enter or leave the airlock. The whole airlock must be covered by the sensor area. If neccessary you can build several sensors into one room. Adjust the sensor areas to match with your room shape.
The vents you are using to control the airflow of your airlock have to have the word "Airlock" as part of its blocknames.
I personaly build two vents into airlocks, one connected with a single oxygen tank and the other one is connected to my main oxygen system. With this setup the air can be sucked out of the airlock, even if the main oxygen system no longer offers any storage capacity. If you are using a seperate O2 tank and vent system those vents have to use "Airlock Backup" as part of its block name.
It is also possible to use built-in lighting to indicate whether the room has a safe atmosphere.
Hangars:
A hangar needs the same setup like an airlock, but the connection between the outside atmosphere and the room itself have to be build with a gate or airtight hangar doors.

Remember to add the token @RoomControl and the room number to every block you want to use with the script. The same you have to do with sensors or lights the script should have access to.

To get a screen used by the script simply open the custom data field of the screen and enter “@RoomControl” to the field. After leaving the custom data field it takes a few seconds and now you have a new custom data field with all screens provided by the block, the possible settings and all available screens of the script. Follow the instructions given in the custom data field. If you are using a RoomScreen or an AirlockScreen, you will also receive information on setting up the room numbers on the screen.

Using buttons to control a room:

You can use buttons to control your rooms, airlocks and hangars. This is a list of all available commands.

• to change the pressure of a room

# is the room number which should change

• to depressurize a hangar and open all gates

# is the room number of the hangar

• to close all gates and pressurize a hangar

# is the room number of the hangar

• to apply for entry into an airlock

1 is the room number of the airlock, 2 is the room you want to enter from - it's important to enter the spaces between the numbers of the rooms and the sign <

• to adjust the airlock to exit to a specific room

3 is the room number of the airlock, 4 is the room for which a request to leave is made - it's important to enter the spaces between the numbers of the rooms and the sign >

The direction of the arrows < or > is the way your character want's to change the rooms.
Entering an airlock with the command "useAirlock=5 < 1" means you want to path a door from room 1 into room 5.
Leaving an airlock with the command "useAirlock=5 > 1" means you want to leave the airlock with room number 5 into room number 1.

Using the script as an H2O2 Control Program Add-On:

If you want to use one control seat to access both scripts, this is set up in the H2O2 Control Program.

Uninstalling the script:

I've added the programmable block command "uninstall" to completly remove all changes the script made to your blocks. If you want to test the script and you don't like it, please use this command before you remove the script.

Discord, Feedback, donations & credits:

And if you don't like the script or have problems with it please let me know down in the commends.
Or enter the Discord-Community:
https://discord.gg/2a52ftDyXX

But if you like my scripts and would like to be kept up to date on the current progress and upcoming projects, you can get regular information from now on here:
https://www.buymeacoffee.com/AlfRomeo80

To bypass the programmable block's character limitation, I used Malware’s Development Script MDK-SE.
https://github.com/malware-dev/MDK-SE

Thank you for your feedback and your support!