Hard fork of Zeppelin discord bot
![]() This enables better interoperability with other bots that apply roles on join. This is because bots that apply roles on join often run into a race condition where they're both setting the member's roles at the same time without knowing about the other, which results in one bot's roles overriding the other one's. Reapplying Zeppelin's roles after a delay should ensure that persisted roles get applied properly even in these cases. |
||
---|---|---|
.devcontainer | ||
.github/workflows | ||
assets | ||
backend | ||
dashboard | ||
debug | ||
docker | ||
presetup-configurator | ||
shared | ||
.clabot | ||
.editorconfig | ||
.env.example | ||
.eslintrc.js | ||
.gitignore | ||
.nvmrc | ||
.prettierignore | ||
.prettierrc | ||
dependabot.yml | ||
DEVELOPMENT.md | ||
docker-compose.development.yml | ||
docker-compose.production.yml | ||
LICENSE.md | ||
MANAGEMENT.md | ||
package-lock.json | ||
package.json | ||
PRODUCTION.md | ||
README.md | ||
update.sh |
Zeppelin
Zeppelin is a moderation bot for Discord, designed with large servers and reliability in mind.
Main features include:
- Extensive automoderator features (automod)
- Word filters, spam detection, etc.
- Detailed moderator action tracking and notes (cases)
- Customizable server logs
- Tags/custom commands
- Reaction roles
- Tons of utility commands, including a granular member search
- Full configuration via a web dashboard
- Override specific settings and permissions on e.g. a per-user, per-channel, or per-permission-level basis
- Bot-managed slowmodes
- Automatically switches between native slowmodes (for 6h or less) and bot-enforced (for longer slowmodes)
- Starboard
- And more!
See https://zeppelin.gg/ for more details.
Usage documentation
For information on how to use the bot, see https://zeppelin.gg/docs
Development
See DEVELOPMENT.md for instructions on running the development environment.
Once you have the environment up and running, see MANAGEMENT.md for how to manage your bot.
Production
See PRODUCTION.md for instructions on how to run the bot in production.
Once you have the environment up and running, see MANAGEMENT.md for how to manage your bot.