Firepup650/bitbot-3.11-fork
2
0
Fork 0
Code Issues Pull requests Activity Actions
No description
352 commits 2 branches 0 tags 4.4 MiB
Python 100%
Find a file
jesopo f7e4d08eb0 Switch to using monotonic time in Database.py timing
2018-08-09 10:38:13 +01:00
modules fixed typos in !channelget 2018-08-08 20:49:34 +01:00
.gitignore Added rotated log files to gitignore 2018-08-08 20:24:51 +01:00
bot.conf.example switch to using configparser for config files 2018-07-16 00:36:52 +01:00
Config.py switch to using configparser for config files 2018-07-16 00:36:52 +01:00
Database.py Switch to using monotonic time in Database.py timing 2018-08-09 10:38:13 +01:00
EventManager.py move priority constants to root of EventManager namespace 2018-07-15 23:53:59 +01:00
IRCBot.py Fixed another reference to the old database structure 2018-08-08 10:33:00 +01:00
IRCChannel.py Moved table-specific logic to their own "table" classes in Database.py 2018-08-05 22:41:38 +01:00
IRCLineHandler.py "self.nick" event didn't get updated 2018-08-03 16:39:53 +01:00
IRCLog.py Handle empty CAP, additional IRCLog feature, better tls, better channel_save logic, add sed-sender-only setting 2017-10-27 13:15:33 +01:00
IRCServer.py Moved table-specific logic to their own "table" classes in Database.py 2018-08-05 22:41:38 +01:00
IRCUser.py Fix 2 typos from the database restructure 2018-08-06 14:10:14 +01:00
LICENSE Initial commit 2016-03-29 12:44:46 +01:00
ModuleManager.py assert statements are optimised out, these statement were useless. 2018-01-09 15:35:33 +00:00
README.md switch to using configparser for config files 2018-07-16 00:36:52 +01:00
start.py Moved table-specific logic to their own "table" classes in Database.py 2018-08-05 22:41:38 +01:00
Timer.py did what I said I would sooner than I thought I would. centralised persisting timers through bot restarts. 2016-04-19 13:25:50 +01:00
Utils.py Added highlight spam detection/prevention logic to channel_op 2017-12-26 11:50:18 +00:00

README.md

BitBot

Python3 event-driven modular IRC bot!

Dependencies

Configurating

To get BitBot off the ground, there's some API-keys and the like in bot.conf.example. move it to bot.conf, fill in the API keys you want (and remove the ones you don't want - this will automatically disable the modules that rely on them.)

Eagle

BitBot's National Rail module can optionally include output from Network Rail's SCHEDULE via Eagle. Configuration on BitBot's end is covered by the eagle- keys in bot.conf.example.

Running

Just run ./start.py

On first boot, he'll ask for a first server to connect to then exit. do ./start.py again and he'll connect to that server and join #bitbot (to get him to join other channels, simply invite him to them.)

Data storage

The main data storage for Bitbot is done in his sqlite3 database, bot.db.