Triggers to BuildCraft gates are implemented by the class Trigger. You will need to extend this class, providing your own texture, your own conditions, etc. Look at the embedded documentation for more details. Note that your trigger will need an id. Trigger ids go from 1 to 1024, BuildCraft reserves the first 64 slots. You can declare the ids you’re using on this document.
In order to register triggers, you have two options:
- Implement an ITriggerProvider, registered through the BuildCraftAPI. This will be called by any gate to assess which triggers can be send depending on nearby blocks.
- Have your tile entities implementing IOverrideDefaultTriggers. For a given block, default BuildCraft triggers will not be installed, and only the ones that you provide instead. That’s useful if, e.g. your tile implements an inventory but you don’t want the inventory-related triggers to be provided.