Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Support importing Points when using the Import Viewers tool #2788

Open
Marstead opened this issue Sep 7, 2024 · 1 comment
Labels
Enhancement A feature request or improvement Plugin Opportunity Something that should be a plugin rather than a built in feature

Comments

@Marstead
Copy link

Marstead commented Sep 7, 2024

Describe the problem
The Import Viewers tool indicates that the user should import their [Name of Currency].xlsx file from Streamlabs Chatbot. The main use case for viewer database import would be to carry over accrued points/currency from the other bot. The exported [Name of Currency].xlsx file requested by Firebot does contain a column for Points, but this column is ignored during the import, and only the usernames and view hours are imported.

Describe the solution you'd like
The points column should also be imported. If the points name matches the name of an existing currency (i.e. the name of the file and the name of the column are the same as a currency that has been added in Firebot), it should update that currency total for all imported viewers. If the points name does not match the name of any points in Firebots' Currency tab, create a new Currency with the same name as the imported points with default settings to be modified later.

Additional context
This seemed like a defect/issue to me as a user importing to Firebot--especially since the instructions explicitly ask you to grab the Currency file, and the Currency file has an explicit column titled "Points". But after discussing it with CKY in the Discord, it sounds like it's actually a Feature Gap. I expect it has not been raised as an issue in the past as no one has actually needed to use the Import Viewers feature before. Speaking as a streamer with a large database to import, while having the view hours is nice, the main reason I need to use an import tool is to preserve currency totals from my old bot.

Recently DeepBot, a ~9-year old premium bot that has been receiving ongoing updates, has seen its main developer go MIA, and it is expected DeepBot will hit end of service in October or November 2024 when its certificates expire. All DeepBot users were just given a heads-up about this and it's likely many of us will be coming to Firebot. Being able to import Points will be very necessary for that process. (DeepBot already has a way to transfer points from DeepBot to Streamlabs Chatbot, so this request is not asking for a DeepBot import workflow, just for the Streamlabs Chatbot workflow to include Points as it appears it should)

@Marstead
Copy link
Author

Marstead commented Sep 9, 2024

We've found some other problem with the Importer Tool that I'll open as a separate issue, but in the meantime, we have a short-term hack solution to the problem of importing viewer databases.

https://github.com/codemage/firebot-deepbot-importer/releases/tag/v0.0.2

This is a custom script written by Taronin to take an import CSV and add/replace records in the Firebot viewer database. It is designed to work with the DeepBot export CSV specifically, but a user from any bot should be able to copy their bot info into the CSV format and get it to import as well. The link includes a Readme with details on how to complete the export from Deepbot if anyone else is searching and finds this thread.

@CKY- CKY- added the Plugin Opportunity Something that should be a plugin rather than a built in feature label Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement A feature request or improvement Plugin Opportunity Something that should be a plugin rather than a built in feature
Projects
Status: Todo
Development

No branches or pull requests

2 participants