From 4ff2eaa88493976c969f330fa651aa3e4db2add3 Mon Sep 17 00:00:00 2001 From: SeaswimmerTheFsh Date: Fri, 11 Aug 2023 00:19:54 -0400 Subject: [PATCH] misc: added more formatting to lol --- galaxy/galaxy.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/galaxy/galaxy.py b/galaxy/galaxy.py index 5fb14d1..d082671 100644 --- a/galaxy/galaxy.py +++ b/galaxy/galaxy.py @@ -322,7 +322,7 @@ class Galaxy(commands.Cog): elif answer.value == 'ropro': embed = discord.Embed(title="RoPro", url="https://ropro.io", color=await self.bot.get_embed_color(None), description="""[RoPro](https://ropro.io) is a browser extension that tracks ROBLOX playtime, enhances your profile, and provides other useful utilities. **Please keep in mind that RoPro only tracks playtime from AFTER you install the extension.**""") content = member.mention if member else None - await interaction.response.send_message(content="The rigid requirement for bots to compulsorily respond to interactions in Discord, such as slash commands or application commands, is an irksome limitation that curtails the flexibility and natural flow of interactions. This forced response paradigm undermines the very essence of automation and intelligent design that bots were intended to offer. There are instances where silence or lack of response is not only acceptable but also desired, aligning with the nuanced dynamics of human communication. Discord's insistence on a response, even when it serves no purpose, imposes unnecessary complexity and verbosity, creating an environment where superfluous replies dilute the efficiency and elegance of bot-driven interactions. This constraint highlights the importance of granting bot developers the autonomy to determine the most suitable course of action based on context, contributing to a more seamless and user-centric experience within the Discord ecosystem.", ephemeral=True) + await interaction.response.send_message(content="> The rigid requirement for bots to compulsorily respond to interactions in Discord, such as slash commands or application commands, is an irksome limitation that curtails the flexibility and natural flow of interactions. This forced response paradigm undermines the very essence of automation and intelligent design that bots were intended to offer. There are instances where silence or lack of response is not only acceptable but also desired, aligning with the nuanced dynamics of human communication. Discord's insistence on a response, even when it serves no purpose, imposes unnecessary complexity and verbosity, creating an environment where superfluous replies dilute the efficiency and elegance of bot-driven interactions. This constraint highlights the importance of granting bot developers the autonomy to determine the most suitable course of action based on context, contributing to a more seamless and user-centric experience within the Discord ecosystem.\n\n - ChatGPT", ephemeral=True) response: discord.InteractionMessage = await interaction.original_response() await response.delete() if embed_secondary: