See SETUP.md for how to setup and run the template project.
A reference of each file included in the template repository, its purpose and
what it does.
The majority of the code is kept inside of the
matrix_trivia_bot folder, which
is in itself a python package,
__init__.py file inside declaring it as such.
To run the bot, the
matrix-trivia-bot script in the root of the codebase is
available. It will import the
main function from the
main.py file in the
package and run it. To properly install this script into your python environment,
pip install -e . in the project’s root directory.
setup.py contains package information (for publishing your code to
setup.cfg just contains some configuration
options for linting tools.
sample.config.yaml is a sample configuration file. People running your bot
should be advised to copy this file to
config.yaml, then edit it according to
their needs. Be sure never to check the edited
config.yaml into source control
since it’ll likely contain sensitive details such as passwords!
Below is a detailed description of each of the source code files contained within
Initialises the config file, the bot store, and nio’s AsyncClient (which is
used to retrieve and send events to a matrix homeserver). It also registering
some callbacks on the AsyncClient to tell it to call some functions when
certain events are received (such as an invite to a room, or a new message in a
room the bot is in).
It also starts the sync loop. Matrix clients “sync” with a homeserver, by
asking constantly asking for new events. Each time they do, the client gets a
sync token (stored in the
next_batch field of the sync response). If the
client provides this token the next time it syncs (using the
AsyncClient.sync method), the homeserver will only return new event
since those specified by the given token.
This token is saved and provided again automatically by using the
This file reads a config file at a given path (hardcoded as
main.py), processes everything in it and makes the values available to the
rest of the bot’s code so it knows what to do. Most of the options in the given
config file have default values, so things will continue to work even if an
option is left out of the config file. Obviously there are some config values
that are required though, like the homeserver URL, username, access token etc.
Otherwise the bot can’t function.
Creates (if necessary) and connects to a SQLite3 database and provides commands
to put or retrieve data from it. Table definitions should be specified in
_initial_setup, and any necessary migrations should be put in
_run_migrations. There’s currently no defined method for how migrations
should work though.
Holds callback methods which get run when the bot get a certain type of event
from the homserver during sync. The type and name of the method to be called
are specified in
main.py. Currently there are two defined methods, one that
gets called when a message is sent in a room the bot is in, and another that
runs when the bot receives an invite to the room.
The message callback function,
message, checks if the message was for the
bot, and whether it was a command. If both of those are true, the bot will
process that command.
The invite callback function,
invite, processes the invite event and attempts
to join the room. This way, the bot will auto-join any room it is invited to.
Where all the bot’s commands are defined. New commands should be defined in
process with an associated private method.
help commands are
provided by default.
Command object is created when a message comes in that’s recognised as a
command from a user directed at the bot (either through the specified command
prefix (defined by the bot’s config file), or through a private message
directly to the bot. The
process command is then called for the bot to act on
Where responses to messages that are posted in a room (but not necessarily
directed at the bot) are specified.
callbacks.py will listen for messages in
rooms the bot is in, and upon receiving one will create a new
(which contains the message text, amongst other things) and calls
on it, which can send a message to the room as it sees fit.
A good example of this would be a Github bot that listens for people mentioning
issue numbers in chat (e.g. “We should fix #123”), and the bot sending messages
to the room immediately afterwards with the issue name and link.
A separate file to hold helper methods related to messaging. Mostly just for
organisational purposes. Currently just holds
send_text_to_room, a helper
method for sending formatted messages to a room.
Custom error types for the bot. Currently there’s only one special type that’s
defined for when a error is found while the config file is being processed.
Any questions? Please ask them in
and we’ll help you out!