A highly configurable bot that is built around a single TOML file
Go to file
2023-08-14 10:29:27 +02:00
src find redirect target by user ID 2023-08-14 10:29:27 +02:00
.editorconfig Indent with 2 spaces instead of 4 2019-11-14 15:10:30 +01:00
.gitignore Add .idea to gitignore 2019-07-13 15:40:27 +02:00
build.gradle.kts update javacord and run ktlint 2023-08-14 10:14:19 +02:00
CHANGELOG.md Added readme and changelog 2019-07-14 18:36:36 +02:00
check.sh Minor changes to deployment process 2019-11-14 15:30:52 +01:00
deploy.sh Minor changes to deployment process 2019-11-14 15:30:52 +01:00
README.md update javacord and run ktlint 2023-08-14 10:14:19 +02:00
settings.gradle bot runs and can ping/pong 2019-06-08 11:07:52 +02:00


Kinda dead.

This bot is a replacement for my old one with a very simple premise: As much as possible should be configurable in a human-readable way. This will allow anyone to modify the config to host their own instance tailored to their own needs, and it allows server moderators to make changes without any coding experience. Even at runtime. I try to maintain a comprehensive default configuration as part of the repository because the past has taught me that I’m not good at updating readmes.

A few months after

The bot has become somewhat specialized at this point, but I think it should still be generally reusable if a similar use case arises. The implementation has kind of deteriorated into a playground for me (adding arrow-kt and just generally trying out FP stuff)[1], but it’s been running and moderating a 1000+ user server for over a year with relatively little maintenance.

[1]: While arrow is great, adding it to a project after the fact leads to a very weird combination of FP and non-FP constructs. Would not recommend in production. This was also built in an early version of arrow that still had Kind and other concepts that were scrapped later, but I don’t plan to update that ever. The bot can keep running as-is until it breaks.