About Tides

I am CX. I am the developer of Tides.

The bot, the dashboard, the appeal site, the music player and its front end are all written by me. There is no second developer and no bought-in template underneath any of it.

I am not doing it on my own though. The Tides team test what I build, find the things I missed, and tell me when an idea is worse than it sounded. A lot of what shipped well only did because somebody there pushed back first.

Music is the clearest example. It would not run at all on the main server's network setup, so audio goes through a local proxy that relays it back. Vitals runs that. Without it there would be no music side of Tides at all.

#Honourable mentions

Tides is my code, but it is not mine alone.

Vitals manages the Tides Discord and has backed this project since the first version. He tests what I build, brings ideas, tells me when something is wrong, and runs the local proxy that keeps music working. He is also a good friend, which is the part that has mattered most on the days when nothing worked.

bloxbuster is a Tides Leader alongside me and the person who created the Tides Discord in the first place. The community exists because of him. Without that community there would have been no reason to build any of this, so in a real sense the project traces back to him.

JerryKiller, our other Leader, makes videos the same way bloxbuster does, and between them they brought the server the people who fill it.

And everyone else who keeps it running: the moderators, the giveaway hosts, and the members who report the bugs I did not catch. Tides is built for that server first, and it shows.

#Where it came from

Tides started as a ticket bot. One server, hardcoded, no dashboard, no settings, nothing reusable. Every value it needed was typed into the source.

It has grown into a multi-server bot that does moderation, tickets, giveaways, leveling, appeals, logging and music, with a dashboard where every message it sends can be rewritten. The plan is to open it up for public use one day, once it is good enough that I would want to use it in a server I did not run.

#Standing on other people's work

Tides is heavily inspired by bots that got there first, and it would be dishonest to pretend otherwise.

Sapphire is the reason the dashboard looks and works the way it does. Their dashboard set the bar for what a Discord bot's settings should feel like, and a lot of Tides is me trying to reach it.

Rythm did the same for the music side. The music dashboard owes its shape to theirs.

Plenty of others fed into it too. If you are looking for a bot for your own server, go and look at those two properly. They are excellent, and both have been at this far longer than I have.

#On AI

I use AI to help build and test Tides, and I would rather say so than have you assume otherwise.

Where it earns its place is the boring, repetitive work. Driving the dashboard and the sites through a real browser to hammer every page, every form and every permission combination. Checking data across hundreds of records at once. Hunting for the one setting out of four hundred that is wrong. That kind of testing is slow and easy to skip by hand, and skipping it is how bugs reach you.

#What it is built on

#Frequently asked

#Is Tides open source?

No. It is not a fork of anything and it is not a resale of somebody else's bot.

#Can I add it to my server?

Not at the moment. Tides is invitation only and there is no public invite link anywhere, including on this site. It runs in a small number of servers on purpose. I would rather it work properly in a few than badly in thousands. Public access is the plan eventually.

#Does it cost anything?

No. There is no premium tier, no paywalled command, and no feature that is worse until you pay.

#Where is my server's data?

In a database on the same server as the bot. It is not sold, not shared between servers, and not sent off to an analytics service. Ticket transcripts and moderation cases are kept per server and are only readable by people you have given dashboard access to.

#What happens if the bot leaves my server?

Your configuration is kept on purpose. If it is added back, your settings, cases and templates are all still there rather than starting from nothing.

#Is there a support server?

Yes, the Tides Discord. Ask there and you are asking me.

#Why it exists

Most bots are fine until you want something specific. Then the message you want to reword turns out to be hardcoded, the setting you need is premium, or the module does most of the job and nothing will move it the rest of the way.

Tides is the answer to that. Every message is editable. Nothing punishes people by default. The dashboard is the real source of truth rather than a toggle panel bolted onto something else.