rp_tracker intergration

[lenscas]

Maybe make the bot work nicely with https://github.com/lenscas/rp_tracker as soon as that support the needed features?

Currently that project is lacking some things the bot needs (turn switching and character edits to name two) but those are planned. As for the different combat systems problems, supporting the one that is used by the bot is already planned and so is being able to make custom charsheets for an RP.

Doing this allows for a nicer database without introducing a (No-)SQL database as a dependency. The only dependency it would introduce is something to allow python to make http(s) requests but I think that the discord api we use already has a dependency on that.

Obviously though, I am biased when it comes to rp_tracker

[SomeoneElse37]

Ehh, maybe, but it's not going to be a high priority for me. Although since you have rp_tracker and your clone of this bot running all the time on the same machine (I assume), this might be a bit more feasible than it would be otherwise.

It might be better just to write an entirely new bot that acts as a Discord-based rp_tracker client. After all, by the time rp_tracker implements all the things that BattleBot needs, there's going to be a lot of overlap between them. A bot to interface with rp_tracker won't need to do all the things that BattleBot already does, since rp_tracker will take care of them.

On the other hand, I think we can both agree that BattleBot could use a more sensible database system, and you know a whole lot more about databases and SQL than I do. If you give BattleBot an SQL database formatted the same way as the one rp_tracker uses, then... maybe?

[lenscas]

in that case I suggest to make 3 files (especially considering #6 )
1 with functions to use the current database
1 with functions to work with an sql database.
later on with functions to integrate with rp_tracker if we decide it would benefit the bot.
This way we keep the dependencies at a minimum and get the benefit of a proper database.