Files
discord-aidolls/docs/events-guide.md
Jonathan Smoley 2ea77c92f0 Prepare Redis Environment (#133)
* add redis container

* Updated Guides and Goals  (#134)

* Update README.md

* Update commands-guide.md

* Update events-guide.md

* Update commands-guide.md

* Added: redis client

* Fixed: redis mock in commands.test.ts

* Updated: npm package patches

* Fixed: redis ip name in keys.ts

* update Node LTS version, workflow env vars

* Updated: node package engine requirements

* Updated: documentation

* fix: upgrade dotenv from 16.4.5 to 16.4.7 (#152)

Snyk has created this PR to upgrade dotenv from 16.4.5 to 16.4.7.

See this package in npm:
dotenv

See this project in Snyk:
https://app.snyk.io/org/jt2m0l3y/project/d8b070a3-e4a3-457a-977b-7eb6a4a48346?utm_source=github&utm_medium=referral&page=upgrade-pr

Co-authored-by: snyk-bot <snyk-bot@snyk.io>

* Update: docs patches, connection ordering

---------

Co-authored-by: snyk-bot <snyk-bot@snyk.io>
2024-12-30 15:53:29 -08:00

1.0 KiB

Events Guide

This is a guide to all of the client events for the app.

Note

  • Each of these is logged to the console for a developer to track.
  • Possible interactions include commands, buttons, menus, etc.
  1. ClientReady
    This event signifies that the Discord app is online.
    Here the app's activity is set and its commands are registered.

  2. InteractionCreate
    This event signifies that a user interacted from Discord in some way.
    Here commands are selected from a knowledge bank and executed if found.

  3. MessageCreate
    This event signifies that a message was sent.
    Here user questions and comments for the LLM are processed.

    1. check message is from a user and mentions the app
    2. check for interaction preferences
    3. add the message to a queue
    4. check the response for success
    5. send a response back to the user.
  4. ThreadDelete
    This event signifies that a Discord Thread was deleted.
    Here any preferences set for interaction within the thread are cleared away.