-
Notifications
You must be signed in to change notification settings - Fork 217
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
Heroic raid boss not accessible #236
Comments
Ok, I meant "hard mode boss" and not heroic. So npc 31311 is for the 25 man raid version? if so, just close this issue :D |
from tc wiki:
So 2 questions:
|
References are loot groups, it means there's a 100% chance you'll get an item from the group 34166 which has its own items with different %s. The interface to show this is currently pretty poor it seems |
|
Search results? No. That gets cluttered really fast with up to 5 times the results
ref-loot is normally merged into the loot as, yes, its fkin confusing to look at unfiltered. As the tcubuntu instance is catered to developers, it is displayed separately, so you can understand how the loot is actually composed.
the 'real' id is the base id. iirc the core uses the base entity and just applies the stats, flags and loot from the placeholder creatures onto it.
it doesn't do anything right now. It's just to display the chances of that reference being merged into the final loot. |
indentations are probably impossible with listviews. |
What about adding column with reference ID, next to item name so can also filter out if needed? |
Like the column next to % (drop chance)? |
Yeah, would look better 👍 |
Search for "sartharion", you will only find this guy:
https://db.rising-gods.de/?npc=28860
And there is no heroic loot associated with it.
Here is the heroic version (I think):
https://db.rising-gods.de/?npc=31311
Btw we can see the heroic version shares many loots with the normal version and on wowhead it's not the case, dunno if it's an issue in the cores (TC/AC) or if it's an issue with aowow
The text was updated successfully, but these errors were encountered: