Closed kevinthedang closed 1 month ago
Just found this out while testing out the slash command:
threadMessageCreate
so we just have to use messageCreate
to handle valid chat instances
messageCreate
somehow within those channels. threadCreate
is called, we want to add it to the instance of valid channels to run Ollama.threadDelete
is called, we want to remove it from the instance of valid channels to run Ollama in.The Client Class found in the discord.js docs lists all of their interactions and brief descriptions of how they work.
Since we are dealing with channels that are "valid", meaning they are still up and being used, we need a way to store them:
I thought about:
discord.js
package development to reduce dependencies.Just had a thought:
/thread
command again, it would generate another chat thread. Should we allow this or prevent multiple chats threads with the same user? @JT2M0L3Y Another thing is when a thread is created these appear:
Should we clean this up using the bot or should we leave them there. @JT2M0L3Y Deleting these do not delete the thread.
@kevinthedang I think users should be allowed multiple threads. We should clean up the remnant thread messages in the main channel stream.
@JT2M0L3Y New Idea for this...
We allow threads to be created everywhere, but the bot can no longer talk in channels.
The only exception for this is in #43 as the bot would talk in a regular public channel.
Definitely.
Thoughts:
@JT2M0L3Y
Steps to Reproduce
Ideas
threadCreate.ts
. Maybe the same way but instead it is on a new query.threadId
and make sure that it is a parent of this thread is the one in the environment.