# Items do not stack

**URL:** https://forum.norestforthewicked.com/t/items-do-not-stack/13610
**Category:** Wicked Bug Reporting
**Created:** [August 6, 2024, 7:23pm UTC](https://forum.norestforthewicked.com/t/items-do-not-stack/13610 "2024-08-06T19:23:28Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![damwil](https://avatars.discourse-cdn.com/v4/letter/d/ea666f/32.png) [@damwil](https://forum.norestforthewicked.com/u/damwil)
#### Post date: [August 6, 2024, 7:23pm UTC](https://forum.norestforthewicked.com/t/items-do-not-stack/13610/1 "2024-08-06T19:23:28Z")

</div>

I don’t know if it’s a bug or just an ill-considered decision, but the items don’t stack. When we have, for example, 20 dishes in one pile. If we eat one dish and have 5 dishes in the second pile, there is no way they can be combined. I thought that by clicking sort, because that’s how it should work, they would connect to each other, but that’s not the case. Am I doing something wrong or has this not been thought through? I request information.

---

<div class="post-metadata">

### Author: ![JoeAndersen](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.norestforthewicked.com/joeandersen/32/6450_2.png) [@JoeAndersen](https://forum.norestforthewicked.com/u/JoeAndersen)
#### Post date: [August 6, 2024, 10:45pm UTC](https://forum.norestforthewicked.com/t/items-do-not-stack/13610/2 "2024-08-06T22:45:35Z")

</div>

It’s not a bug, but it’s an issue that deserves feedback, and I need this feature as well.

---

<div class="post-metadata">

### Author: ![BrasilBorba1](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.norestforthewicked.com/brasilborba1/32/6124_2.png) [@BrasilBorba1](https://forum.norestforthewicked.com/u/BrasilBorba1)
#### Post date: [August 6, 2024, 11:24pm UTC](https://forum.norestforthewicked.com/t/items-do-not-stack/13610/3 "2024-08-06T23:24:33Z")

</div>

Well it is a minor one since if you run out of that pile the other food will replace the quick slot, i usually just dump everything inside a container and then they will restack.

---

<div class="post-metadata">

### Author: ![damwil](https://avatars.discourse-cdn.com/v4/letter/d/ea666f/32.png) [@damwil](https://forum.norestforthewicked.com/u/damwil)
#### Post date: [August 7, 2024, 6:26pm UTC](https://forum.norestforthewicked.com/t/items-do-not-stack/13610/4 "2024-08-07T18:26:12Z")

</div>

Yeah, but you shouldn’t bother with it so much. This should be resolved automatically. If you know what I’m talking about.

---

<div class="post-metadata">

### Author: ![Caiden\_Boulton](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.norestforthewicked.com/caiden_boulton/32/3148_2.png) [@Caiden\_Boulton](https://forum.norestforthewicked.com/u/Caiden_Boulton)
#### Post date: [August 9, 2024, 3:27pm UTC](https://forum.norestforthewicked.com/t/items-do-not-stack/13610/5 "2024-08-09T15:27:51Z")

</div>

thank you for the report. have escalated the issue internally

---

<div class="post-metadata">

### Author: ![daniel\_german](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.norestforthewicked.com/daniel_german/32/7158_2.png) [@daniel\_german](https://forum.norestforthewicked.com/u/daniel_german)
#### Post date: [October 19, 2024, 10:45am UTC](https://forum.norestforthewicked.com/t/items-do-not-stack/13610/6 "2024-10-19T10:45:52Z")

</div>

Op you are totally right and also the item consumption needs to be tweeked because I had 2 stacks of the same item a 20 stack and a 5 stack and in the cooking process it used 3 from the 20 stack. I can’t put 3 from the 5 stack to make it 20 and 2. And if I use an item it should always take from the smaller stack.

---

<div class="post-metadata">

### Author: ![Caiden\_Boulton](https://yyz1.discourse-cdn.com/flex003/user_avatar/forum.norestforthewicked.com/caiden_boulton/32/3148_2.png) [@Caiden\_Boulton](https://forum.norestforthewicked.com/u/Caiden_Boulton)
#### Post date: [October 21, 2024, 4:51pm UTC](https://forum.norestforthewicked.com/t/items-do-not-stack/13610/7 "2024-10-21T16:51:04Z")

</div>

This has been solved internally. Will be including in a hot patch. Thank you for your report.
