Bond vs YAGPDB
YAGPDB is open-source, self-hostable and very configurable, and its custom commands are written in a Go templating language. That language is the wall you hit if you do not want to write code.
We build Bond. Everything below about YAGPDB comes from its own public pages.
What YAGPDB is known for
Deeply programmable custom commands, configured in its own interface and switched on per feature.
What Bond does differently
Bond's automations are written in plain English and compiled into a checked format, so you get programmable behaviour without learning a template syntax, and it tells you when something will not work before it saves it.
One sentence, instead of the panels.
@Bond Every Monday at 9am, post how many people joined last week in #staff
When to stay on YAGPDB.
Stick with YAGPDB if you are comfortable with the templating language, or you want to run the bot on your own hardware.
It is good at deeply programmable custom commands, and there is no prize for switching a tool you are happy with. Add Bond for the jobs YAGPDB does not cover, and leave the rest where it is.
And if you do switch, in three moves.
Both bots can run at once. There is no import step and nothing to migrate.
Add Bond alongside
YAGPDB keeps doing exactly what it does today. Bond joins without touching a single existing setting.
Move one thing across
Pick the part you like least. Describe what it does to Bond, approve the changes, and watch it run for a week.
Turn the old one off
Only once the new one has run. Repeat for the next part, or stop here and keep both.
Try Bond on one thing this week.
Free to start, and nothing you have set up in YAGPDB changes when you add it.