Add Behaviors

[desain]

Make sure that your submission has the following:

• A link to the raw github markdown file with a YAML front matter definition containing:
  • The title of your extension
  • A description of your extension
  • The author
  • A hero image
  • An icon
  • Tags (these will help with your extension's discoverability)
  • A link to your extensions manifest

Please, go through these steps before you submit a PR.

• You have done your changes in a separate branch.

• You have a descriptive commit message with a short title (first line).

• You have only one commit (if not, squash them into one commit).

• Your pull request MUST target the main branch on this repository.

• Your pull request puts your extensions details as the last entry in the extensions.json file

[desain]

A note here -

Like I talked to Mitch about in a thread in the Discord a while ago, I know the frequent scene update API calls this extension can cause don't play all that nicely with OBR's current underlying CRDT data synchronization mechanism, so this may be a bit much to make available to the general public. If yall prefer not approving this for the official store until the potential data sync rewrite for OBR that Mitch mentioned, that's fine, just let me know.

[Several-Record7234]

Validation script and image URLs check out fine. Extension functionality is good.

API usage not checked.

[nthouliss]

A note here -

Like I talked to Mitch about in a thread in the Discord a while ago, I know the frequent scene update API calls this extension can cause don't play all that nicely with OBR's current underlying CRDT data synchronization mechanism, so this may be a bit much to make available to the general public. If yall prefer not approving this for the official store until the potential data sync rewrite for OBR that Mitch mentioned, that's fine, just let me know.

I'll have a further chat with Mitch about this but I really appreciate the understanding 😄