suzumearch 0.2.19 → 0.2.20
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +16 -1
- package/cli.mjs +1484 -1484
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -113,6 +113,8 @@ export DISCORD_GUILD_IDS="345678901234567890"
|
|
|
113
113
|
export DISCORD_USER_IDS="456789012345678901,567890123456789012"
|
|
114
114
|
# Owner IDs allowed to perform Discord write/delete/moderation actions:
|
|
115
115
|
export DISCORD_OWNER_IDS="678901234567890123"
|
|
116
|
+
# Optional privileged intent for reply text that does not mention the bot:
|
|
117
|
+
export DISCORD_MESSAGE_CONTENT_INTENT="false"
|
|
116
118
|
```
|
|
117
119
|
|
|
118
120
|
```powershell
|
|
@@ -123,10 +125,15 @@ $env:DISCORD_GUILD_IDS="345678901234567890"
|
|
|
123
125
|
$env:DISCORD_USER_IDS="456789012345678901,567890123456789012"
|
|
124
126
|
# Owner IDs allowed to perform Discord write/delete/moderation actions:
|
|
125
127
|
$env:DISCORD_OWNER_IDS="678901234567890123"
|
|
128
|
+
# Optional privileged intent for reply text that does not mention the bot:
|
|
129
|
+
$env:DISCORD_MESSAGE_CONTENT_INTENT="false"
|
|
126
130
|
```
|
|
127
131
|
|
|
128
132
|
Then run `/discord on` inside SuzumeArch. `/discord` opens the configuration
|
|
129
|
-
menu; `/discord status` prints the active settings.
|
|
133
|
+
menu; `/discord status` prints the active settings. `/discord on` persists
|
|
134
|
+
env-backed Discord token and ID settings into SuzumeArch config so they survive
|
|
135
|
+
future launches. You can also run `/discord save` after setting env vars to save
|
|
136
|
+
the current effective Discord configuration permanently.
|
|
130
137
|
|
|
131
138
|
You can also configure lists from inside the CLI:
|
|
132
139
|
|
|
@@ -136,6 +143,8 @@ You can also configure lists from inside the CLI:
|
|
|
136
143
|
/discord guild 456 567
|
|
137
144
|
/discord user 678 789
|
|
138
145
|
/discord owner 890
|
|
146
|
+
/discord message-content on
|
|
147
|
+
/discord save
|
|
139
148
|
```
|
|
140
149
|
|
|
141
150
|
Single-value env vars and commands still work: `DISCORD_CHANNEL_ID`,
|
|
@@ -151,6 +160,12 @@ voice, server mute/deafen, set nicknames, time out members, and request the bot
|
|
|
151
160
|
to join or leave voice channels. The bot needs the corresponding Discord
|
|
152
161
|
application permissions in the server for these actions to succeed.
|
|
153
162
|
|
|
163
|
+
Message Content is a privileged Discord Gateway intent. Keep it off unless you
|
|
164
|
+
need replies without an explicit bot mention to include readable text, and enable
|
|
165
|
+
the same intent in the Discord Developer Portal before running
|
|
166
|
+
`/discord message-content on`; otherwise Discord can reject the gateway
|
|
167
|
+
connection with a disallowed-intent close code.
|
|
168
|
+
|
|
154
169
|
Warning: Discord mode automatically switches the session to
|
|
155
170
|
`bypassPermissions` by default. Anyone who can post in the configured Discord
|
|
156
171
|
channels and passes the optional guild/user filters can trigger tools and shell
|