| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
Allows for persistent, dynamic storage of configuration options outside
of the config.json file.
The bot_state table is, essentially, a key-value store for config
options. There are two new prepared statements, `state` and
`update_state`:
- `state` will return the value for the provided key
- `update_state` will create the key or update an existing key
|
| |
|
|
|
|
| |
for now
Change-Id: I77c7d319ddf37c7259f4de89567f9a6719f88796
|
| |
|
|
| |
Change-Id: I6796976649ee59f4e647148e77d76effa7315f73
|
| |
|
|
| |
Change-Id: If56998535b8067b29ea34c760ac2da4339174983
|
| |
|
|
| |
Change-Id: Icda968ab189d601c5e390dfee094ae4419cce9e6
|
| |
|
|
| |
Change-Id: I3cff2a05c63e88abddc8eff6a3ee9a9f73a5172d
|
| |
|
|
|
|
| |
Supports migrations
Change-Id: Ifca8358d4f57a4b417f1d972e400e98767e01bb5
|
| |
|
|
|
|
|
|
|
|
| |
When unloaded, modules attached to OnMessage events would still be part
of the list used by FOREACH_MOD to send events to, leading to a
segfault.
This changes the behavior of load and unload to place new modules at the
*start* of the event handler arrays, leading them to already be
processed by the time the bot gets to the ModuleManager.
|
| | |
|
| | |
|
| | |
|
| |
|
