No description

Find a file

jesopo 5338859e31 added a function to Utils to get the "closest" setting, with channel/user settings being more important than server-wide settings.		2016-05-06 13:36:01 +01:00
modules	added a function to Utils to get the "closest" setting, with channel/user settings being more important than server-wide settings.	2016-05-06 13:36:01 +01:00
.gitignore
bot.json.example
Config.py
Database.py	added get_server to Database.py, for some future use. dunno.	2016-04-29 12:43:22 +01:00
EventManager.py
IRCBot.py	added code to allow you to keep a server in the database but not connect to it.	2016-04-27 11:56:37 +01:00
IRCChannel.py
IRCLineHandler.py	decided to not track user realnames as there's no real purpose and it means bitbot does not have to whois newly joined people.	2016-04-22 11:48:59 +01:00
IRCLog.py
IRCServer.py
IRCUser.py	decided to not track user realnames as there's no real purpose and it means bitbot does not have to whois newly joined people.	2016-04-22 11:48:59 +01:00
LICENSE
ModuleManager.py
README.md
start.py
Timer.py
Utils.py	added a function to Utils to get the "closest" setting, with channel/user settings being more important than server-wide settings.	2016-05-06 13:36:01 +01: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.json.example. move it to bot.json, 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.)

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.