Originally Posted by Agren
My guess is that a seed is assigned to a container which is used to generate the loot, and that the actual contents aren't stored unless you disturb the contents by looting something from them. Up until this point, these crates have always contained a single item in them. I intend to get my hands on some rogue lockboxes to make sure that the contents are actually saved once something is looted from the container. If it isn't that could be an interesting exploit.
|
I want to point out this is consistent with the notion that loot on mobs is viewable by GMs, once raid instances are generated. When the loot container (in that case a mob, in the case Agren experimented with various crates) it has a seed stored with it inline in the DB. Once something is looted it needs to store an indirect reference to another row somewhere with the items in the container.
Assuming the computation of the loot is cheaper than creating a new row in the DB, it makes sense to not bother storing anything but the seed unless the loot is perturbed, because the containers seed will regenerate the same loot unless the loot table is changed. In normal operation the loot tables for mobs do not change between when someone clicks the corpse and the first item is looted ;-)