charchter limit

Reply part 2 of 2

Example for (C) going from outside to inside

Button panel near a light and external vent (only 1 external vent needed on entire grid and is used ___to detech pressure outside to tell if the airlock needs to de-compress or not)

Outer door

Button panel with a light and vent (vent to add/remove air from airlock) (this button panel will use ___2 buttons 1 for inside and 1 for outside so you can change the airlock state while inside the ___airlock)

Inner door

Button panel near a light and inner vent (inner vent is the one that is in the same section)

Last feature I would add is the ability to control o2/h2 production to prevent over filling the tanks ___(you want to keep about 20% empty to allow you to de-compress the airlock/hangar)

Reply part 1 of 2

Thats true
I have already had isues with 2 or 3 scripts trying to control the same thing. (like doors for example)

Then what about having the brakets like I mentioned but also have a prefix at the begining of the block name.

Example (using the [PS] as an example instead of [Pressure Section]
"[PS] (block name) [sectionname] [section name]" (this would be a door)
"[PS] (block name) [section name]" (this would be a vent)

This would also allow you to add an auto closing door system tot this that would be able to
(A) close normal doors,
(B) lock 1 door of an airlock if the other is open
(C) use a 1 button system for changing the airlock state

The problem with that is that most scripts on the Workshop use the bracket and list scheme, so if the script only looked for brackets then there might be conflict between multiple scripts on the same ship. The current method is just a "works anywhere and with anything" type of deal

That makes sence.

Then what about making it just search for the "[" and "]" in the block names then match the parts on the door names with the part on the vent names.

This would be something like if block a is a door and blocks b and c are vents then it could look like this:
Example:
search for "[" , "]" in name of blocks a b and c.
if block is vent then check if able to hold pressure
if block is door then open when vent shows pressure and close when leaking

I coded it the way it is on purpose so that the sections could be custom named. They don't need to include the word "section", you can just name them "bridge" or "hangar bay" or whatever you like. It does require editing the list, but to me that still saves time over trying to remember which part of my huge ship I named as section 1 or 2.

I just checked it out using a station and found that if you have 2 vents (sections) then you name the door as "door name [Section A] [Section B] " then the door will close when one of the vents has no pressure.

I also found out that if it can only find 1 of the vents then it will just use that vent until you build the 2nd vent (no error)

Can you try to get this so you dont have to add a LIST of sections, but instead so it will just look for the tag "Section " as a prefix then the remainder will be your section name.
It would look like "(block name) [Section + (section name)]"
Example:
"Air Vent [Section A1]"
"Door [Section A1] [Secton A2]"
"Air Vent [Section A2]"

(Still using the same naming system but the script would no longer need a list as it would just look for the [Section XX] tag.

yes @jarhead it can work with multiple doors in one room or section or multiple sections each with multiple doors.

can this work with more than 1 room like my door being named
bulkhead [section a] [section b]