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
Hi, i just came up with an idea to make /unloadinv better to use in storage rooms.
Currently a chest needs to have at least 1 item of the itemtype you want to unload in a chest to be able to unload it.
So if you empty the entire chest for a project, you need to find the right chest manually again before /unloadinv is going to work again for that itemtype.
Maybe a good solution for this issue may be to check if a chest has an itemframe on it, with the itemtype on it?
Not sure if it would take up a lot of cpu cycles (causing lag). If you have 200 double chests which have 10 possible item frame locations each, then there will be 2000 positions to check.
It could be made configurable so server admins can turn it off if it takes too much cpu usage.
What you think about this idea?
The text was updated successfully, but these errors were encountered:
It is of course also possible to check to what a block a block/entity is attached in 1.12, but the API lacks some features that make it very convenient. That means I would have to code the same logic twice and always check what version the server is using, and I really dont like that. Adding that feature for 1.13+ and 1.12 and below would mean 3 times as much as trouble as adding it only for 1.13.
Hi, i just came up with an idea to make /unloadinv better to use in storage rooms.
Currently a chest needs to have at least 1 item of the itemtype you want to unload in a chest to be able to unload it.
So if you empty the entire chest for a project, you need to find the right chest manually again before /unloadinv is going to work again for that itemtype.
Maybe a good solution for this issue may be to check if a chest has an itemframe on it, with the itemtype on it?
Not sure if it would take up a lot of cpu cycles (causing lag). If you have 200 double chests which have 10 possible item frame locations each, then there will be 2000 positions to check.
It could be made configurable so server admins can turn it off if it takes too much cpu usage.
What you think about this idea?
The text was updated successfully, but these errors were encountered: