Issue:
Currently there is no way to add pre-existing lootdrop tables to the loottable_entries of a global loottable. It only allows you to create new ones. This feature request is to provide the options for searching by name or entering an existing lootdrop ID
Discussion:
When we want to add a lootdrop to a loottable for a single NPC, we do the following:
- Click the yellow + icon next to the label that reads, Lootdrops associated with this loottable:
- Decide an option from one of the following:
- Search for a Lootdrop by Name
- Enter a Lootdrop ID
- Create a New Lootdrop
.
For Global Loot, when we want to add a lootdrop to a loottable, we do the following:
-
Click the yellow + icon next to the label that reads, Lootdrops associated with this loottable:
-
It assumes "Create a New Lootdrop", and takes us straight to the template for "Add New Lootdrop".
Doing this, allows me to run a database query to add existing lootdrop tables:
INSERT INTO loottable_entries (loottable_id, lootdrop_id, multiplier, droplimit, mindrop, probability)
VALUES ('110562', '7638633', '1', '1', '0', '10');using the peqphpeditor interface instead of switching to a SQL client.
I intend to work on this feature myself, but adding this issue here for transparency/feedback. Am I not considering a limitation in how global drops are supposed to work?
Issue:
Currently there is no way to add pre-existing
lootdroptables to theloottable_entriesof a global loottable. It only allows you to create new ones. This feature request is to provide the options for searching by name or entering an existing lootdrop IDDiscussion:
When we want to add a lootdrop to a loottable for a single NPC, we do the following:
For Global Loot, when we want to add a lootdrop to a loottable, we do the following:
Click the yellow + icon next to the label that reads, Lootdrops associated with this loottable:
It assumes "Create a New Lootdrop", and takes us straight to the template for "Add New Lootdrop".
Doing this, allows me to run a database query to add existing lootdrop tables:
using the peqphpeditor interface instead of switching to a SQL client.
I intend to work on this feature myself, but adding this issue here for transparency/feedback. Am I not considering a limitation in how global drops are supposed to work?