You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I really like the way that containers are just stashes assigned to specified item. However I would really love to have opportunity to open the container while not having it equipped by passing its id. It’s gamechanger.
Describe the solution you'd like
Allow containers to be opened while not in eq by their id.
Describe alternatives you've considered
I was thinking about making actually new inventory type and assign stash to item
Additional context
🤝
The text was updated successfully, but these errors were encountered:
Just a note that this is not simple as it sounds, because the container is bound to a unique id that exists only on the item and that item exists only within an inventory. We can't determine what kind of container it is (what item) to set weight, slots, etc.
It is possible to query that information, but that cannot be achieved efficiently because
we will need to perform full table-reads (there is no indexing available for inventory items)
we will need to use inefficient json_extract (or similar) functions to find an item with that metadata
If you have one inventory containing 6 items this isn't a big deal... if you have 1000 inventories containing up to 500 items each, we might as well set a bomb off in the server room.
Is your feature request related to a problem? Please describe.
I really like the way that containers are just stashes assigned to specified item. However I would really love to have opportunity to open the container while not having it equipped by passing its id. It’s gamechanger.
Describe the solution you'd like
Allow containers to be opened while not in eq by their id.
Describe alternatives you've considered
I was thinking about making actually new inventory type and assign stash to item
Additional context
🤝
The text was updated successfully, but these errors were encountered: