Mining Robots and Chest Problem Solving

Very good idea

I agree. It's very inconvenient when you're doing something and have to run to clear the minerals.

It annoys me that I have to clean the chests every hour :D

I think it would help the players, a good ode

Great idea

I support 100%

I agree

It is impossible to implement. Almost everything you wrote would create an incalculable number of unsolvable item duplication problems.

1. It is impossible to have larger chests without visual or duplication problems.
   1. Having a chest with more than 6 rows is not supported by Java textures, meaning textures will start overlapping each other, creating very ugly visual problems
   2. The Bedrock version does not support such a thing at all, and I would not be surprised at all if because of such a thing Bedrock players could no longer play on the server at all
   3. If such a thing is created with pagination - item duplication problems are guaranteed, and tracking all of them is physically impossible. We need to anticipate literally over a thousand special Minecraft cases regarding chests, and for that we have neither the time nor the resources. No one will finance 5,000 - 10,000 euros worth of hours for such functionality.
2. That "Upgrade" is meaningless. You don't mine resources faster because it doesn't depend on the robot. It already uses a netherite pickaxe for resource mining. The inventory space definitely won't be larger due to the reasons listed above. So what exactly will it "improve"?
3. This point is unsuitable just because of the number of items and future maintenance. The robots currently collect absolutely all items, and there are (in version 1.20) 1,643 of them. With each version, their number increases significantly. This means:
   1. For auto-compression, I would have to have an insanely massive Map of arrays, which with each version I would have to redo from scratch. This would consume several days of my life, meaning it would cost 700-2,000 euros to do. It could be reduced to some very specific items, but with every player complaint you go and look at everything all over again, you literally waste an incalculable amount of time.
   2. The toggle would have to cover all 1,643+ items. Are you saying now that the player will have to go through 37 pages of items (and with each version it will keep increasing) to enable which items will be sold or not sold? And that's not even counting the fact that such functionality is currently not possible at all. A complete rewrite of 2 large systems, so even if approved, such a thing can be expected at the earliest next year.
   3. The filter is easier because it doesn't require rewriting the selling system. But the same problem remains - at least 37 pages of all Minecraft items, which the player will have to enable/disable one by one. For the player themselves, clicking the mouse button 1600 times will become more tedious than selling the items in the chest from time to time.
   4. And finally, one of the biggest problems with this idea - space. I already had a problem with the amount of data stored in the PDC storage. Storing a few bits per block in a single chunk is not so bad, the loading there is fast, disk usage is low, the possibility of corrupting the entire chunk's PDC is small. You want an entire array with thousands of blocks to be stored per one block, and there can be up to 98,304 blocks in a chunk. This not only significantly affects the chunk size (which makes the entire loading process slower, thus putting a very heavy load on the whole server), but also greatly increases the possibility of data corruption. It wouldn't be very fun to come in one day and see that all the chests in one chunk are empty, all the robots are no longer working and the robots are gone, everything is empty, or maybe even the entire chunk is gone. After all, everyone saw what happened with enderchests when I stored them in PDC - they kept disappearing, players lost countless items.

And this is not even counting the fact that it would require a rewrite of very large systems, which would again cause a lot of problems, leading to player complaints. We don't have a very large team, we don't have the time and resources to implement the very complex things suggested here. Unfortunately, we will have to suggest something down to earth. Something feasible.

It is impossible to implement. Almost everything you wrote would create an uncountable number of unsolvable item duplication problems.
It is impossible to have larger chests without visual or duplication problems.

Having a chest with more than 6 rows is not supported by Java texture, meaning textures will start overlapping each other, creating very ugly visual problems
The Bedrock version doesn't support such a thing at all, and I wouldn't be surprised at all if because of such a thing Bedrock players couldn't play on the server at all
If such a thing is created with pagination - guaranteed item duplication problems, and tracking all of them is physically impossible. It is necessary to anticipate literally over a thousand Minecraft special cases regarding chests, and for that we have neither the time nor the resources. No one will finance 5,000 - 10,000 euros per hour for such functionality.

That "Upgrade" is meaningless. Resources are mined faster not because of the robot. They already use a netherite pickaxe for resource mining. The space in the chest definitely won't be more in any way due to the reasons listed above. So what exactly would it "improve"?
This point is unsuitable just because of the item quantity and future maintenance. Robots currently collect absolutely all items, and there are (in version 1.20) 1,643 of them. With each version, their number increases significantly. This means:

For auto-compression, I would have to have an insanely massive Map of arrays, which with each version I would have to redo from scratch. This would consume several days of my life, meaning it would cost 700-2,000 euros to do. It could be reduced to some very specific items, but with every player complaint you go and look at everything again from scratch, literally wasting an uncountable amount of time.
The toggle would have to cover all 1,643+ items. Are you now saying that the player would have to go through 37 pages of items (and with each version it will keep increasing) to enable which items to sell or not sell? And this is not even counting the fact that such functionality is currently not possible at all. A complete rewrite of 2 major systems, so even if approved, such a thing can be expected at the earliest next year.
Filter is easier because it doesn't require rewriting the selling system. But the same problem remains - at least 37 pages of all Minecraft items that the player would have to enable/disable one by one. For the player themselves, clicking the mouse button 1600 times would become more tedious than selling the items in the chest from time to time.
And finally, one of the biggest problems with this idea - space. I already had a problem with the amount of data stored in the PDC storage. Storing a few bits per block in one chunk is not so bad, the loading there is fast, disk usage is low, the possibility of corrupting the entire chunk PDC is small. You want an entire array with thousands of blocks per one block to be stored, and in a chunk there can be up to 98,304 of those blocks. This not only strongly affects the chunk size (which makes the entire loading slower, thus heavily burdening the whole server), but also greatly increases the possibility of data corruption. It wouldn't be very fun to come in one day and see that all chests in one chunk are empty, all robots are no longer working and there are no robots, everything is empty, or maybe even the entire chunk is gone. After all, everyone saw what happened with enderchests when I stored them in PDC - they kept disappearing, players lost countless items.

And this is not even counting that it would require a rewrite of very major systems, which would again cause a lot of problems, because of which players would complain. We don't have a very large team, we don't have the time and resources to implement the very complex things suggested here. Sorry, but something down to earth will have to be suggested. Something possible.

Thanks for the answer, well I tried, I don't know those other subtleties from the inside:) but I just don't understand, why does the miner need those 1643 items, it doesn't mine them, can't it somehow distinguish from the inside? because that fact as you say 37 pages doesn't sound positive :)