xurxodiz / iria Goto Github PK

Separate games into a new table with an extra column/flag ACTIVE, so when games are done they are mark as inactive and a new one can begin, instead of deleting them.

To new working architecture.

A new module can be employed to redirect questions to the Tese application I developed.

To new working architecture.

To new working architecture.

Based on #19, adding a different table for games would allow the possibility of adding a column for type of game.

Different modules for other games could be written, so the callbacks are handled into their module depending on game type (also, prefill different content, and so on.

To new working architecture.

A user can type !batalla xxx and other can type !1 and replace the true vote.

Currently, the modules don't listen to what Iria says, to prevent loops and people making Iria act upon herself.

But should this be decided at bot-level, like currently, or at module-level?

Let's keep this in mind. No rush.

Modules should follow a common interface: a function to receive messages and another to for output.

They should also have a way to register the callbacks with the main object.

Similar to what #19 suggests for games, add a status flag for players so their data is not deleted when they leave a game (and could pick it up in the future perhaps).

To new working architecture.

Right now the bot works with IRC. That's outdated. It should be ported to XMPP using the server already set up at iria.me

Iria can only talk in multi-user chatrooms now. Implement the protocols to have her chatting privately with users.

Dice module currently supports the format 4d6+2d20+5. Make it support both 2d12-1d4 and 1d12-1 too.

To new working architecture.

To new working architecture.

To new working architecture.