The New Self Assigning Super Bulk 

I'm glad you like it, the wiring of each slice looks so much better now, previously it was very... spagetti redstone.

@@cubicmetre agreed the design is way cleaner than the previous one

Yeah that makes sense, I generally run with optifine because of connected glass, I thought maybe it was something to do with rails on noteblocks or something but the light updates makes a lot more sense, especially if it was locational.

@@cubicmetre I think there's something in Fabric you can do for connected glass as well, let me check when I get back home later

@@cubicmetre Could be the 3D rails resource pack, I’ve noticed they are quite laggy for the client when a lot of them are flashing

@@softie4645 Yes, continuity

@@baumichkeit I use "Continuity" for connected glass. Keep in mind that it also requires "Indium" to be installed. After you have both mods, you'll find a few new resourse packs installed, just enable them and that's it!

same

under rated redstoner ig

He’s a literal robot

Yes I'd like to hear if putting an opaque block above every column that is affected by a piston in the instant line helps.

If a slice is full the boxes get redirected into an overflow hopper line. But it would take a LOT of resources to fill each slice which has a capacity of 3M items.

you can pbbly rewire the overflow protection into the shulker sorters and add a empty slice detector that locks the interface item sorter

Technical legends.

Just request 27 then return 18, the problem is that if you reduce the batch size then you need to reduce the counter for each slice and then each item in the interface represents only 9 boxes instead of 27 and you would need to reduce the storage capacity by 66%

I actually locks the item call input, so you can throw items into the call system but it won't trigger until the assignement is complete.

The problem is if we let the slice overflow then boxes will jam the hopper locking mechanism into the open state. So we need to detect when it is full and lock the input to prevent it from overflowing. The piston and the redstone block do this by moving the redstone block into the space where the moss block is, which locks the hopper.

See kaniol's 1.17+ 1728 furnace array for one possible design. Or did you want something smaller than cubic's usual projects? Hoppers self-lock, perfect fuel efficiency, burn shulker boxes to speed up and simplify item distribution. Surprisingly simple for the scale. Destroying boxes shouldn't be a huge problem with a tree and a shulker farm, whether cubic's scaleable 2D farm or a 1D shulker reactor setup.

This is an activate from anywhere instant dropper line, the problem with using those kinds of instant wires is that they can be triggered at weird intervals that break segments of the wire. I've experienced too many situations of wires fragmenting and oscillating in ways that break mechanisms attatched to them.

Please don't make me do this, it was difficult enough to make it assignable in the first place.

You cannot request boxes until the first 27 are sorted. If you are only ever operating on less than 27 boxes of an item then this bulk probably isn't the place for it.

@@cubicmetre Thanks for your answer! I did figure it out by myself looking at the world download, but I do appreciate you answering

The thing is, Bedrock redstone is straight up inferior in mechanics to Java redstone because someone had the dumb decision to make it non-deterministic. For example in Java edition you can precisely control the order in which things happen whilst in bedrock it is deliberately randomized. This greatly reduces the potential of Bedrock redstone in a way that makes it less challenging and more prohibitive to do marvellous engineering feats. For example instant dropper lines would not be possible in Becrock edition because the firing of the droppers would always be randomized. This means the time it would take for a storage like this to deliver items would be sporadic and random and likely cause a lot of pain and frustration.

The thing is, each item represents 27 boxes of that item, meaning with a full slice of 1728 boxes you get 64 items each representing 27 boxes each. This means at full capacity each slice occupies only a single slot of the interface chest. If you were to decrease the amount of boxes attatched to each item to say, 1 shulkerbox per item. Then a full slice would be 1728 or 27 slots of the interface. Meaning to present all items you'd need a chest for each item type, which for the current design that can hold 108 different item types is 54 double chests needed for any interface. Meaning you'd need to search 54 double chests to find the item type you want. I'd say it's easier just to request 27 boxes and send 26 back to the storage than try to represent each box with its own item.

the self assignment will work regardless of how many boxes you input. The assignment will first cache the box in the box sorter, then the second box of that item to enter the slice will push the first one into the hopper below the box/item recombination. Then once the third box comes the first box will enter the slice and get re-directed to the item call system for stocking.

Sending 27 boxes per request is kinda required because of the way the interface works. Each item represents 27 boxes and each slice can store 1728 boxes of that item. So it's all perfectly balanced to allow each item type to be easily accessible from the interface chest. If you don't want 27 boxes then simply request 27 boxes and return 23 to the storage.

@@cubicmetre But i dont have 27 boxes of each resource, at least at the beggining of the storage operation... So I made something close to 1 item per 2 SB but it sometimes fails and sends 1 extra, but it is possible i think

did you ever find out a way to do this?

The input system instantly rejects any box that is not completely full, if a box is full and contains mixed items then the item in the first slot is used to sort the box. If the item in the first slot is not something you want to store in the bulk then you're screwed. But keep in mind that everything that enters this storage has to go through the players inventory first. So as a player you must be diligent in what you throw into the input.

In theory you should be able to input any amount you want

If you remove a 3-counter, you add them in amounts of 9.

@@caspermadlener4191 Where is the 3 counter may I ask?

You can request the items indefinitely, well, until you run out of that item in the storage.

I'm not sure if the concept of a call based bulk will work very well on bedrock edition simply due to the random subtick mechanics. Instant dropper lines would randomly distribute the firing order giving and indeterminant time interval between requesting and recieiving your items.

Time to build the farms so you can generate the items for this.

A storage like that would contain so much data in each chunk it would crash your game if you tried to save it to memory.

@@cubicmetre let the 12-year-old flex his knowledge of big numbers.

No.

😔 3am

@@natimorta_ ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-zcOBFiqqh9Y.html bedtiiiiiime