System-specific plugins facilitate bi-directional communication with Rocketship by creating, sending, and receiving targets, actions, and emitters over the network.
When a system comes online, its plugin hooks directly into the system's API, and Rocketship dynamically generates GUI elements that reflect the state of the system. No patching, no protocols, no science project.
Actions are grouped into 'bundles' - when a bundle is triggered, all of the actions in that bundle are performed simultaneously.
'Bindings' dynamically connect emitters to bundles. With user-created bindings in place, Rocketship will reactively trigger action bundles upon receiving emitters.
Scenes in Rocketship allow a user to orchestrate bindings within a scene's local timeline. Scheduling, on the other hand, allows a user to orchestrate scenes on a global timeline.
Rocketship features a flexible tool for manual scheduling, as well as constraint-based procedural schedule generation.