Loot tables not working

[Kobiesan]

I have an item that when opened contains two loot entries. The first entry has a 90% chance to drop a certain item and the other entry has a 10% chance to drop a different item from a list in reference_loot_template. However, for some reason it's not working.

My referenced loot entries have chances on their own so it would be 10% on top of maybe a 30% chance within that reference. But, for some reason, sometimes when my item is opened, it contains either nothing, one of the 90% items, or both a 90% and 10% item.

None of them have groupids in either item_loot_template or reference_loot_template.

Here's a picture of my item_loot_template entries:


Here's a picture of the reference_loot_template entries:

[Supora]

Did you set up a GroupId in loot_template?

[Makpptfox]

I never use 0 as a GroupID, set 1 for both of your references, it should fix the problem of looting both of the row instead of one.

I don't really get why you would have nothing in it tho, since the reference is a total of 100%.. Try again with 1 as GroupID too, because I don't see anything wrong in your tables beside of that.

[Kobiesan]

I never use 0 as a GroupID, set 1 for both of your references, it should fix the problem of looting both of the row instead of one.

I don't really get why you would have nothing in it tho, since the reference is a total of 100%.. Try again with 1 as GroupID too, because I don't see anything wrong in your tables beside of that.

Okay I changed the item_loot_template to this:


and now there's no more duplicates BUT whenever the drop lands on the 10%, nothing is inside. It's completely empty.

[Amaroth]

First of all, 0 GroupID for loots is fine in many cases. It only means "no group" - which means that more than 1 out of items in group can drop at once (or none can drop as well). And thats what you don't want in this particular case, yes. What happens at the moment is that in 10% of cases references are used, which have up to 26% to drop. 26/10 = 2.6%.

So there is only up to 2.6% of anything from references dropping, the rest what remains to 10% is quite high chance that NOTHING will drop. Because of groupID=0 which says "none, one, or multiple can drop at once". Set groupID to 1 in references, too.

[Kobiesan]

First of all, 0 GroupID for loots is fine in many cases. It only means "no group" - which means that more than 1 out of items in group can drop at once (or none can drop as well). And thats what you don't want in this particular case, yes. What happens at the moment is that in 10% of cases references are used, which have up to 26% to drop. 26/10 = 2.6%.

So there is only up to 2.6% of anything from references dropping, the rest what remains to 10% is quite high chance that NOTHING will drop. Because of groupID=0 which says "none, one, or multiple can drop at once". Set groupID to 1 in references, too.

My reference chances total 100 not 26.

Here is what happens when my groupid is set to 1 for both the reference and the item_loot_template:

This is also what happens when the item_loot_template groupids are set to 0 and the reference groupids are set to 1. Which doesn't many any sense at all.

I also tried updating item.dbc and that did nothing. I also tried changing the name of each of the items to be different but that also did nothing.

[Amaroth]

My reference chances total 100 not 26.

That means absolutely nothing when you use group 0, as in that case, every single item is handled as, in fact, its own group.

[Kobiesan]

My reference chances total 100 not 26.

That means absolutely nothing when you use group 0, as in that case, every single item is handled as, in fact, its own group.

okay so i put the references in group 2 and the loot_template tables in group 1. The container still drops two items sometimes.

I also tried making everything have a group id of 1. Same problem. I've tried every combination and it doesn't work.