In some cases, disconnection from the server can be unclean and won't be noticed until the bot tries to send a message, which may never happen if it did not disconnect during the game. To solve this problem, it will now ping the server every 2 minutes by default, which will result in a broken pipe error if the connection is dead. This won't be able to detect netsplits where the server the bot is on stays online, because those are impossible to correctly detect in every case. This commit also adds a !latency command so that users can verify if the bot is lagging. |
||
---|---|---|
messages | ||
oyoyo | ||
roles | ||
src | ||
.gitignore | ||
.mailmap | ||
botconfig.py.example | ||
CONTRIBUTING.md | ||
gamemodes.py.example | ||
LICENSE | ||
messages.json.example | ||
README.md | ||
requirements.txt | ||
wolfbot.py |
This is the Werewolf game bot for ##werewolf on freenode. It's a fork of lycanthrope, which was the last bot used in #wolfgame before it died.
We have an active community, and we'd love for you to join us!
Running your own copy
You need Python 3.3 or newer to run the bot. Python 3.4 and higher is recommended.
Copy botconfig.py.example
to botconfig.py
and modify the settings as needed. You can also copy-paste individual settings from src/settings.py
into botconfig.py
if you want to modify them. You may also add or customize your own game modes by renaming gamemodes.py.example
to gamemodes.py
and using the same layout used in src/gamemodes.py
.
Note: you should never alter files under the src
folder directly (unless you are submitting a change to the code), use botconfig.py
and gamemodes.py
for related changes.
To start the bot, run ./wolfbot.py
. You can use --verbose
to log all raw IRC messages and --debug
to enable some debugging features. These options should not be used in production.