GeekyDeaks / discord-destinybot

Discord Destiny Bot
MIT License
8 stars 3 forks source link

Remove VOC specific commands #7

Closed GeekyDeaks closed 8 years ago

GeekyDeaks commented 8 years ago

Thinking about creating a new project to contain the VOC server specific commands and features, then make this a pure destiny bot.

I'd still like the @discordtag lookup to work as intended, which means the two bots need some way to maintain a shared instance of the data. This way we can move the hacky #psn parsing into the VOC bot, which just updates the DB (or whatever is used). Going to look into options on this, was initially thinking sqlite, since it does not require a DB server instance, but the API for this is not really JS friendly like say MongoDB.

GeekyDeaks commented 8 years ago

Since we will need to use SQLite for #8, I am thinking of using sequelize. I just cannot find an embedded database that has the same level of concurrency SQLite offers.

GeekyDeaks commented 8 years ago

Ok, spoke with the server maintainer and he's happy to have two bots, so I'm going to fork this project, remove the destiny parts from it and vice-versa. I'll focus on the DB aspects, but I am thinking it would be still good to have a DB of the @discord to XBL/PSN mappings, so will at least need maybe the xbl set [gamertag] and psn set [gamertag] commands?

GeekyDeaks commented 8 years ago

this is no longer necessary with the modular approach