Miserable time design a "fancy" settings menu
I'm making a bot for my server (with help of AI, not gonna lie), and as the functionalities increased, the way i was organizing the
So, when using Rythm, i really fell in love the way it manage its myrad of settings, but to implement my version of it for my bot... it was a nightmare.
For example, i have a system of "memories" for each member that i end up forwarding to the AI api (it's a chatbot too), its organized in per-guild-per-user way (there is also a per-whole guild memory set too, not the focus on it for now), and handling text input in this settings style (using forms and dropdowns) became quickly miserable too, because the AI tried to make a dynamically ID'ed for that module's interactions using the target member ID.
I really don't know if that style of Rythm's would be the way for my bot to have its settings, or if i should separate the modules that have text input as subcommands, etc.
What are your thoughts about this?
/configSo, when using Rythm, i really fell in love the way it manage its myrad of settings, but to implement my version of it for my bot... it was a nightmare.
For example, i have a system of "memories" for each member that i end up forwarding to the AI api (it's a chatbot too), its organized in per-guild-per-user way (there is also a per-whole guild memory set too, not the focus on it for now), and handling text input in this settings style (using forms and dropdowns) became quickly miserable too, because the AI tried to make a dynamically ID'ed for that module's interactions using the target member ID.
I really don't know if that style of Rythm's would be the way for my bot to have its settings, or if i should separate the modules that have text input as subcommands, etc.
What are your thoughts about this?
Support server for discord.js, a Node.js module to interact with Discord's apps API.
57,693Members
Resources
Similar Threads
Was this page helpful?
