-
Notifications
You must be signed in to change notification settings - Fork 16
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
Drop Rarity for Collection Log and Loot #139
Comments
We don't know which pet the user has received as the messaging is only "something has snuck into your pocket", so that wouldn't be possible. Right now, drop rarity is not something we have accessible to us. I imagine this would need to be data we fetch from the wiki on a per-item basis. If we can add the ability to map an item + source to a drop rarity, this would be something we can add to some Loot notifications, most Clue Scrolls, & most of the Collection Log items. |
The problem I have personally with drop rates is how do we actually know it's the correct one? Unless the game secretly tells the client what drop it actually is, I see a problem with drop rates. For example, So how are we supposed to know what notif to fire for 8, 9, and 10 sweets, as it's a possibility from both pools. 🤔 |
If an item has multiple rarities, we could just omit that information. I imagine that won't be the case for very many items since it can only apply to stackable items |
I didn't know it worked like that. I thought it already mapped the right NPC / activity. I don't really know how the other plugin does it? Maybe you could get some inspiration out of that code. |
Which plugin is this @zeroquinc ? |
https://github.com/BossHuso/discord-rare-drop-notificater |
It would be a nice touch to see the drop rarity for the Collection Log and Loot tabs. Maybe also for Pets and Clues?
Something like this I have in mind:
Now it only shows you the GE value.
Maybe also a toggle to set
Min Drop Rarity
to filter out some loot drops that wouldn't get passed if under theMin Loot Value
threshold.Thoughts?
The text was updated successfully, but these errors were encountered: