-
Notifications
You must be signed in to change notification settings - Fork 1
Trigger System
bglasber edited this page Jul 2, 2012
·
4 revisions
Bucket follows a trigger-response system, which means that certain messages will cause bucket to respond in a specific way. This a many-to-many relation, so there can be many triggers which trigger the same response, or a single trigger which has many possible responses.
When bucket is triggered by a message, it will look up an appropriate response. If there is more than one response, he will randomly choose one, and respond with that.
To illustrate this, suppose bucket has the following trigger:
test -> example
Now, whenever a message contains test, bucket will respond with example. If we add another trigger:
test -> example2
Bucket will now randomly choose between "example" and "example2" when a message contains test.
- Bucket is not able to trigger himself - only other users can send messages which may trigger him.
- Any trigger provided is a substring of the message. If we use the triggers provided in the examples above, both "this is a test" and "wow testing 123" would also cause the trigger to activate. To this end, it is advised that you use fairly long triggers, to avoid having bucket respond to unrelated things often and unnecessarily.