[Feature Request] User-Defined Persistent Databases

[Oceanity]

Describe the solution you'd like
Allow users to create arbitrary databases with defined columns in the same vain as defining arguments on Preset Effect Lists, and provide ways to create, read, update and delete entries that persist through closing. Also provide a way in the UI to view and manage the entries of the created database.

Additional context
Can leverage JsonDb to accomplish the functionality side of things and have a dedicated menu similar to Counters.

[phroggster]

This would be helpful, but I'll explicitly tack on that the functionality should also be exposed to thirty-party scripts/plugins, probably via ScriptModules. Maybe even allow custom angular control templates for editing/validating a database/table/unique block of data/JSON file (however the contexts are isolated), similar to how effects do it already.

[Oceanity]

This would be helpful, but I'll explicitly tack on that the functionality should also be exposed to thirty-party scripts/plugins, probably via ScriptModules. Maybe even allow custom angular control templates for editing/validating a database/table/unique block of data/JSON file (however the contexts are isolated), similar to how effects do it already.

This was definitely my thought as well, I would love to move the hacky queueing system I scrapped together for both Spotify and now Quest Master to be something Firebot could natively just store and my scripts could pull from, that way it can be exposed in the UI and more visibly manageable

[Marstead]

This would be extremely helpful. I would recommend adding some mechanism for direct import of CSV files into the database.