-
Notifications
You must be signed in to change notification settings - Fork 9
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
Suggestion: Load current Loot Tracker data on initial install #4
Comments
I didn't do this as it is impossible to determine which account the loot is from (for people who use multiple accounts on the same RL account) and I couldn't figure out a way to preventing it from running again when you change your in-game name. Currently this plugin works like most plugins, which means it only starts tracking once installed. Unfortunately its also not easy to manually convert exported Loot Tracker data from the website as the local-data records the name and price of dropped items where the website just tracks ID and qty. I may come back to this in the future if i can figure out the 2nd issue since the 1st isn't really fixable. |
Was there anyway to import current loot from the loot plugin? |
Unfortunately there is not currently a system for importing data. There have been quite a few technology changes since my previous comment nearly 2 years ago so this feature is now feasible to implement. Unfortunately I am quite busy IRL so I'm not sure when I will get to this feature (if ever). The changes that allow this feature to work now:
It's still not feasible to manually convert from the website but there should be a way to query the Loot Tracker data from within the client and reformat it for the plugin. |
Awesome!!! Looking forward to it. |
It would be nice if the plugin could load the current loot tracker data when the plugin is installed. for example i have 1200 wyvern kills in my loot tracker when I installed this plugin. Not sure if its possible, but if it is it would be nice.
The text was updated successfully, but these errors were encountered: