54de373242
It simply didn't work before now for a while (as in, you could still join/start). Also make it function during join phase, because having weird restrictions on which it does/doesn't disable the commands is weird. The admin can still !fjoin/!fstart as needed if they do want to run one more game after executing this command during join phase. |
||
|---|---|---|
| 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.