Limnoria icon indicating copy to clipboard operation
Limnoria copied to clipboard

A robust, full-featured, and user/programmer-friendly Python IRC bot, with many existing plugins.

Results 135 Limnoria issues
Sort by recently updated
recently updated
newest added

## Scenario 1: *You have multiple versions of Python *All of your plugins are compatible with all of them If you switch switch between Python versions, and run the bot...

Bug

The number of times I've had the Seen plugin kill my bot for one reason or another has gotten to be quite annoying. The new annoyance lately is some quit...

Bug
Need more info

The goal is to sequence multiple commands which are (in this case) called at different times via scheduler. The command executed is an `echo` (or `reply`) command. But when doing...

Bug

In case of error "482: You're not a channel operator", request op and retry them.

Feature request

With Python2 EOL approaching and [deprecation warnings](https://github.com/ProgVal/Limnoria/commit/46935370557937f1c2c91234b18e2beac3276e94) added to Limnoria, I thought having one place to keep track of any incompatible third-party plugins would keep things easier to find and...

Python 2 compatibility

Steps (with ~/.local/bin/ in $PATH): 1. python2 setup.py install --user 2. supybot foo.conf (runs on python2) 3. python3 setup.py install --user 4. supybot foo.conf (runs on python3) 5. python2 setup.py...

Bug

Just another itch of mine: you are shipping manpages for all the scripts, except for `supybot-reset-password`. I'd find helpful if also that script was documented by a manpage.

Documentation

I'm trying to restrict my Limnoria bot to owner-only operation, so I have set `defaultIgnore` to _true_, which in turn necessitates identification by hostmask, because everything else is ignored. To...

Bug
security/DoS

The only solution for the moment to run commands in plugins like GitHub, Trigger, etc. is to have a fake hostmask.

Feature request
Help wanted

There are a way to rotate channels logs but no way to do the same with the bot's main log "messages.log" Sometimes messages.log it gets too big.

Feature request