Make simple enable/disable block in configuration. about spaceengineers HOT 7 OPEN

Personally I'd prefer the building object checks a hook to see if the requested block can be built so limits can be determined dynamically, a la #59. But the above would be a nice additional feature for a slight performance boost.

from spaceengineers.

This already exists:

Definition xsi:type="MyObjectBuilder_AssemblerDefinition" Enabled="false"

Almost all definitions can be disabled this way.

from spaceengineers.

If it does is not documented, could you tell us the secret? :)

On 20 May 2015 at 07:10, Tyrsis [email protected] wrote:

This already exists:

—
Reply to this email directly or view it on GitHub
#87 (comment)
.

from spaceengineers.

Yep just used this today with respawn ships - if you add that Enabled attribute (attribute, not child node, and make sure to use lowercase for its values), you can disable blocks at init. But this does not allow for a dynamic check during run-time.

from spaceengineers.

@zrisher Enabled node on blocks that derive from MyFunctionalBlock effectively sets block to On/Off state.

eg. if you for example have Turret with false this turret is loaded inactive (you need to switch it on in terminal gui)

Enabled attribute in block definition root node enables/disables block definition (it's easier than commenting whole block out, or deleting from definition file)

from spaceengineers.

Ah thanks, I was wondering about that distinction.

from spaceengineers.

Enable node is actually quite practical, and of course is used in savefiles ;o)

from spaceengineers.