-
Notifications
You must be signed in to change notification settings - Fork 14
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
Always send uniques #130
Comments
My immediate question is how do we go about checking what is a unique? Hopefully there's some API that we could use to figure this out 🤔 |
By unique, do you mean every item in the collection log? So if this setting is on, you'd send a loot notification every time you loot a:
The reason I'm asking is if the above is undesirable, maybe there's another way we can identify items you want to send notifications for instead |
Yeah, that is kinda what I meant. And then for example that you can set a minimum value and drop rate. For example I don't want to have every Mole claw as notification but if I could set the value rarity to have a minimum of 1/256 it would still give me notifications for rare drops that maybe cost less than what I have set up under "Loot" as |
Do you think your recent suggestion of #139 would cover this use-case effectively? |
Yeah, I think it does. Maybe it's better to close this and continue in that topic. |
First of all thanks very much for the embed commit, my notifications look so much cleaner now!
A feature I still would like to see added is an option under Loot; Always send uniques.
The way it works now is that the collection log notification will still pop but if you already have gotten it once it obviously won't.
Could this be a new toggle? Thank you it's very nice to see active development on this!
The text was updated successfully, but these errors were encountered: