Подпишитесь, чтобы загрузить
Whip's Auto Door and Airlock Script

"Sure, I could turn around and close the door like a civilized man.
Or I could let a robot do it for me... like a modern man."

- Acarii on the virtues of automatic doors

This script will close any door once it has been fully open for over 3 seconds (10 seconds for hangar doors). The duration that a door is allowed to be open is independent of the status of any other doors. This is to say that if I open one door at a certain time then open another door a second later, each door will stay open for 3 seconds, then close. This script also supports an INFINITE amount of simple airlock systems.

1. Place this script in a programmable block
   
2. (Optional) Set up airlock systems

If you don't want/need the airlock functionality, only step (1) is necessary!

The script will fetch ALL doors on the grid and automagically close any
door that has been open for a set number of seconds. Doors can also be excluded from
this feature.

You can change the auto close interval one of two ways:

• Globally by changing the "auto close time" in the Custom Data of the Programmable Block
  
• Per door by changing "Custom auto close time (s)" and setting "Use default auto close time" to false in the Custom Data of a Door.

Add the tag "Excluded" anywhere in the door's name to exclude it from auto closing. Hangar doors are excluded from auto closing by default, but you can change that in the Custom Data of this programmable block.


This script supports the optional feature of airlock systems. Airlock systems are composed of AT LEAST one Interior Door AND one Exterior Door. The airlock status lights and sound blocks do not affect the functionality of the doors so if you don't have space for them, don't fret :)

• Interior doors should be named like so: "[Prefix] Airlock Interior"
  
• Exterior doors should be named like so: "[Prefix] Airlock Exterior"
  
• (Optional) Airlock status lights should be named like so: "[Prefix] Airlock Light"
  
• (Optional) Airlock Sound Block should be named like so: "[Prefix] Airlock Sound"
  
• The "[Prefix]" is the unique name that you group your airlock doors by
  
  Example Names:
  
  • "Main Airlock Interior" and "Main Airlock Exterior"
    
  • "[Main] Airlock Interior" and "[Main] Airlock Exterior"
    
  • "Potato Airlock Interior" and "Potato Airlock Exterior"
    
  • "1337 Airlock Interior" and "1337 Airlock Exterior"

Rules:

• An airlock system is composed of at least one Interior Door and one Exterior Door. You can have more than one of each type of door. If you do not have one or more Interior and Exterior doors in your airlock system, that particular system will be ignored.
  
• Prefixes are case insensitive and spaces are ignored
  
• Doors with the same prefix are linked together in an airlock system
  
• You do not need an airlock light for the doors to function properly
  
• For each airlock system, if an Interior Door is opened, all Exterior Doors are locked and vice versa
  
• Each airlock system operates independently of others

I've rewritten this code (yet again) to support Custom Data configuration. This means that you do not need to touch any values inside of the code.

In the Custom Data of the programmable block, you can change the global default auto close intervals as well as any and all of the name tags used by this script.

By popular request, if you want to set auto close intervals per door, you can do so in the Custom Data of a door.

Because hardcoding stuff is mega lame, I've also added configuration settings in the Custom Data of light blocks that are being used as airlock indicator lights.


This script has been rewritten (on 2021/02/22) to support Custom Data configuration. The script is still very performance friendly, and this should make configuring stuff much cleaner since you no longer need to edit variables in the code.

This is/was my first script, I hope y'all enjoy! :)

Thanks to LordTylus for the script in his Self-Maintaining Survival Ship that I initially based the logic of the auto door closing on. It was.one of my first exposures to C# and partially responsible for piquing my interest in programming :)

If you have any questions, comments, or concerns, feel free to leave a comment.

- Whiplash141 :)

(Do not reupload without permission, not even to mod.io)