Alek Ratzloff a0070fca38 Small fix for plugins that accept non-channel messages
There's a long explanation in the code of this commit that says this:

> TL;DR OF THE BELOW: if the first parameter looks like a channel in
> addition to message type, then filter by channel. Otherwise, don't
> filter by channel.
>
> Here's the issue: plugins are *usually* multiplexed by channel. But
> that's only for messages that target channels, such as PRIVMSG and JOIN.
> For non-channel messages, such as server status messages (such as 001 on
> connect, or 372 for MOTD, etc) we want to ignore the channel aspect of
> plugin multiplexing. In order to accomplish this, we just check if the
> first parameter looks like a channel - i.e., starts with an octothorpe #.

Signed-off-by: Alek Ratzloff <alekratz@gmail.com>
2022-05-30 19:43:39 -07:00
2022-05-23 19:04:03 -07:00
2022-05-30 17:40:17 -07:00
2022-05-27 19:16:44 -07:00
2022-05-23 20:54:54 -07:00
2022-05-23 20:54:54 -07:00

omnibot

"Fourth time's the charm!"

This is an IRC chatbot that can be extended with plugins. Omnibot comes with a few plugins pre-packaged.

Configuring and running

Copy the config.example.toml file to config.toml and fill it out for your needs.

How do I add multiple servers?

Simply put, you don't. Run another instance of the bot with its own configuration if you want to do that.

Running

  1. Install dependencies pipenv install
  2. Run pipenv run python -m omnibot

Troubleshooting

aiohttp fails to install

pipenv run pip install "aiohttp[speedups]"

Description
No description provided
Readme 790 KiB
Languages
Python 99.7%
Dockerfile 0.3%