Paginated message maze error...?

I'm getting a strange message from the PaginatedMessage class:
[PAGINATED_MESSAGE_RUNS_IN_NON_PARTIAL_DM_CHANNEL] PaginatedMessageRunsInNonpartialDMChannel: PaginatedMessage was initiated in a DM channel without the client having the required partial configured.
If you want PaginatedMessage to work in DM channels then make sure you start your client with "CHANNEL" added to "client.options.partials".
Furthermore if you are using message based commands (as opposed to application commands) then you will also need to add the "DIRECT_MESSAGE" intent to "client.options.intents"
If you do not want to be alerted about this in the future then you can disable this warning by setting "PaginatedMessage.emitPartialDMChannelWarning" to "false", or use "setEmitPartialDMChannelWarning(false)" before calling "run".
[PAGINATED_MESSAGE_RUNS_IN_NON_PARTIAL_DM_CHANNEL] PaginatedMessageRunsInNonpartialDMChannel: PaginatedMessage was initiated in a DM channel without the client having the required partial configured.
If you want PaginatedMessage to work in DM channels then make sure you start your client with "CHANNEL" added to "client.options.partials".
Furthermore if you are using message based commands (as opposed to application commands) then you will also need to add the "DIRECT_MESSAGE" intent to "client.options.intents"
If you do not want to be alerted about this in the future then you can disable this warning by setting "PaginatedMessage.emitPartialDMChannelWarning" to "false", or use "setEmitPartialDMChannelWarning(false)" before calling "run".
However, this command was called from within a guild and not a DM. Intents: [GatewayIntentBits.Guilds] FYI, I'm running with only the application.commands scope, not bot Here's the relevant code:
const paginatedInfo = new PaginatedMessage().addPageEmbeds(
Object.entries(beeData).map(([_, data]) =>
new EmbedBuilder()
.setTitle(`${data.emoji} ${data.name}`)
.setDescription(data.description)
.setColor(Colors.Yellow),
),
);
await paginatedInfo.run(interaction);
const paginatedInfo = new PaginatedMessage().addPageEmbeds(
Object.entries(beeData).map(([_, data]) =>
new EmbedBuilder()
.setTitle(`${data.emoji} ${data.name}`)
.setDescription(data.description)
.setColor(Colors.Yellow),
),
);
await paginatedInfo.run(interaction);
This is running inside of a chatInputRun(). Version: "@sapphire/discord.js-utilities": "^7.3.3",
No description
7 Replies
alaninnovates, the sequel
Relevant research - https://discord.com/channels/737141877803057244/1151938957806940160/1151938957806940160 This was the only past time this error was mentioned in this server. Appraently it got closed without an actual resolution.
Seren_Modz 21
Seren_Modz 21•2mo ago
do you have the guilds intent? the solution for the linked issue was https://discord.com/channels/737141877803057244/1151938957806940160/1151962183933100103 (as per what the user marked the solution as with @Answer Overflow)
alaninnovates, the sequel
yes. I mentioned in my message:
Intents: [GatewayIntentBits.Guilds] FYI, I'm running with only the application.commands scope, not bot
Favna
Favna•2mo ago
Best you can do is run with a debugger and set a breakpoint before the error is thrown so you can trace what went wrong but this should only happen if there is something wrong in terms of config.
alaninnovates, the sequel
i ended up just implementing it myself 🙃 sorry yall!
Favna
Favna•2mo ago
Implementing what exactly? if you mean a paginated message then that's silly and you're shooting yourself in the foot... very hard. A little bit of debugging now would safe you a lot of pain later when you're own code eventually needs adjusting. But you do you I suppose.
alaninnovates, the sequel
yeah i just needed the back and forth buttons. it was very simple to implement, i just stored the index in the custom id of the button and matched that with an array of embeds. I'll probably debug it at a later time but I wanted to get an update out

Did you find this page helpful?