Plugins-oriented bot
Go to file
2023-05-31 07:11:04 +06:00
.fleet start 3.2.0 2022-12-05 15:31:19 +06:00
.github/workflows remove redundant config test and update build workflow 2022-06-08 17:13:46 +06:00
badges update readme 2020-11-12 13:45:23 +06:00
bot setupBotPlugin now works synchronously 2023-02-12 01:29:45 +06:00
gradle Update libs.versions.toml 2023-05-31 07:09:05 +06:00
plugin add gitea publication 2022-11-17 11:29:02 +06:00
_config.yml Set theme jekyll-theme-cayman 2020-11-12 13:34:22 +06:00
.gitattributes Initial commit 2020-11-08 19:04:44 +06:00
.gitignore update dependencies and add logging 2022-06-11 19:15:09 +06:00
build.gradle add own repo 2022-11-17 13:00:19 +06:00
changelog_parser.sh add github workaround 2020-11-12 12:03:33 +06:00
CHANGELOG.md Update CHANGELOG.md 2023-05-31 07:09:31 +06:00
github_release.gradle Update github_release.gradle 2022-07-09 09:47:34 +06:00
gradle.properties start 6.0.0 2023-05-28 20:53:32 +06:00
gradlew Initial commit 2020-11-08 19:04:44 +06:00
gradlew.bat Initial commit 2020-11-08 19:04:44 +06:00
LICENSE Initial commit 2020-11-08 19:04:44 +06:00
README.md fill readme + rename fallback state handler 2022-08-13 20:37:17 +06:00
settings.gradle remove redundant modules 2022-08-13 20:09:21 +06:00
template.config.json improve reconnect feature 2022-09-04 15:07:30 +06:00

PlaguBot

For users

Template: Use template

You can create your bot using this template by following of its instructions

For developers

Template: Use template
Bot version: Maven Central
Plugin version: Maven Central

That is a set of libraries for plagubots. Look at the PlaguBot Plugin template to find how to create your bot.

Technical help

In this bot has been used variant with FSM. That means that you may use all the Behaviour Builder with FSM functionality. In case you wish to setup states repo, you should use the next code in the setupDI of your plugin:

single<StatesManager<State>> {
    // setup your manager and return here
    // Default is:
    DefaultStatesManager(
        InMemoryDefaultStatesManagerRepo()
    )
}

Besides, you may setup handling errors lambda in the same function:

single<StateHandlingErrorHandler<State>> {
    { state, e ->
        logger.eS(e) { "Unable to handle state $state" } // logging by default
        null // you should return new state or null, default callback will return null
    }
}