Yes, I generally design my scripts to work with any (conceptually compatible) build, needing only naming or block groups to identify the components.

I have used quite a lot of both timers and gateway scripts, but none of them suited me to this extent for some reason. Even almost nothing had to be added to fit your requirements.

By default all you need to do is have "Airlock" in the name of a block for the script to interpret it as being a member of an airlock of that name. To be meaningful, an airlock has to have a vent and two doors. The doors should also be discernible whether inner or outer, using the return values of those functions. By default, anytihng with "External", "Exterior", or "Outer" are the outer doors, and anything with "Inner" or "Interior" are the inner ones. You can change this as you see fit.

Look at some of my sample blueprints, such as the waypoint station, which is featured in the screenshots for this page.

Relka - could you offer some examples of the naming conventions you used for the airlock parts? My thick brain can't grasp the instructions you placed at the top of the script. Thanks.

It looks like you named an air vent in a way that confused it. This script - and most of my other "grid monitoring" scripts only work as intended if you name your vents/doors/etc according to a specific template specified in the settings at the top of the script.

Compilation is successful, but upon running the script, I get this message:

Caught exception during execution of script:Index was outside the bounds of the array.
at Program.createID(IMyAirVent vent)
at Program..ctor()

I'm testing this script out right now, however it doesn't seem to work at this time. Any plans on fixing it? Or if it's something I did wrong, is there a guide or instructions anywhere?