aboutsummaryrefslogtreecommitdiffstats
path: root/src/content
diff options
context:
space:
mode:
authorPinapelz <donaldshan1@outlook.com>2023-08-10 19:43:08 -0700
committerPinapelz <donaldshan1@outlook.com>2023-08-10 19:43:08 -0700
commit50ee559510f4ca6468a98d35a5ffdc9bb5b00439 (patch)
tree7c7543fdcd97a60b0ba824d2139caf7df68b5100 /src/content
parent5e13525e84fa62e55b018f7aae1bf1743358bcae (diff)
Edit: Discord-auto-reply post clarification about BD plugins
Diffstat (limited to 'src/content')
-rw-r--r--src/content/blog/discord-auto-reply.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/src/content/blog/discord-auto-reply.md b/src/content/blog/discord-auto-reply.md
index ed87104..a32e7d2 100644
--- a/src/content/blog/discord-auto-reply.md
+++ b/src/content/blog/discord-auto-reply.md
@@ -108,8 +108,7 @@ module.exports = meta => {
};
};
```
-
-With this you should start to see messages being logged to the console. To get them into a Python program, As shwon, I've opted to use a websocket server since it was the most striaghtforward given that Node modules are not possible in BetterDiscord.
+I've opted to use a websocket server since it was the most striaghtforward given that Node modules are not possible in BetterDiscord. All we're doing here is listening for any messages we get and then sending them through to the websocket server. Lucky for us, the JSON version of these messages contain both the user ID and the channel ID already which is all the identification information we will need.
## Integrating an LLM
Now that we have thing up and running on the Discord end, let's connect to a LLM.
send patches to the email below
yukais@pinapelz.com
include the subject [PATCH repo_name]
pinapelz.com
homepage