Does Your Bot REALLY Need a Dashboard?

1 год назад

7,191 Просмотров

Комментарии:

waya - 24.07.2023 21:02

Because I think under ctrl kinda missed the title of this video of "Do you really need a bot dashboard":

It comes to the complexity and features of your bot. Let's say you make a bot that only has one feature i.e.: welcomer (greeting people on join), then I think using some sorts of in-discord (in-app) config solution is perfectly fine, or if it's a bot just for your server it's completely fine to just code variables into a JSON file (called "hard coding").

If your bot aims to many features (such as Waya/Wamellow), I think you're better of making a dashboard, for multiple reasons:
- In-discord (in-app) config can get overwhelming and confusing for the users of your bot, that's what I see a lot with Waya's config solution.
- Dashboards have a greater overview, can be more personalized to your bot needs.
- In-discord (in-app) configs can end up like mine with 9.000 line of total code just for the config in a single file, completely no way to continue working on it, completely in efficient and slow to run, leads to multiple interaction failed inside of discord.
- Dashboards can have better general user experience and design compared to in-app configs.

TL;DR:
When should you use a static (not changing) JSON file:
- when it's private, just for your and/or for your friends server.

When should you use a in-discord (in-app) config command (using JSON):
- when you want to use it in multiple of your servers and maybe a small public bot.

When should you use a in-discord (in-app) config command (using a database, i.e.: MongoDB):
- when you plan to make a public bot with not all too many features.

When should you make a web dashboard (using a database, i.e.: MongoDB):
- when you plan to make a (biggerish) public bot with kinda a lot of features *OR* want to learn web development.