In the open beta discussion, it was mentioned that "a disabled trigger should not be able to be acted upon".

With custom triggers, this is not true. If you create an onInteract to execute a custom trigger on a disabled object you can have different results. I have reproduced two cases but know there are more when the object is enabled but the trigger component is disabled.

Case 1:

I have 3 objects. One button and two objects to handle custom trigger actions.

The button has an OnInteract that has an Activate Custom Trigger for both the other objects.

One of the other objects starts on and the other starts off. These objects toggle each other. When you interact with the button, it behaves as expected with the quote. The enabled object executes, the disabled object does not. When you press the button again, both triggers activate, even though the first object is now disabled.

Case 2:

Everything is the same as above, but the entire system has a parent object in the hierarchy. Both custom triggers execute from the start.

This behavior is unreliable and unintended according to the quote. Please prevent custom triggers from executing when the object or VRC_Trigger component is disabled.