I am new here. I apologize if this is out of line, or has been hashed out. I've seen some posts about it, but I don't think they went into the depth this post is intended to.
The current way loot is picked out of lootdrop is very hard to predict. The
spreadsheet I am linking here shows how the code behaves, and I use it as a tool to get the chance entries in the db to actually produce what I want. As you'll see, for the list of 4 items in this lootdrop table, items I want to drop 50%, I have to make 91% in the table, because of the way the software runs.
Full explanation is inside the
spreadsheet.
So my question is. Do we not want eqemu software to reflect the percentages we type into these lootdrop entries? I think we do, which means we'd have to change the code. I have read and reread the code, and I understand the logic of it, but the very nature of how it works makes each entry depend on the others, which makes it hard to enter.
I ran tests on my server using the table linked to here. The numbers run pretty close to dead on with what my spreadsheet says, except that the random number of where to start seems to lean a bit toward starting at the top of the list. It starts there 8% more than it should. Not sure why.
Comments? I can share the data collection as well if you like. I used log messages to document every dropped item from these lootdrop entries along with where in the list it started and ran the numbers.
Loot Tables
Threaded Mode
