Jump to content

Workaround for Crock Storage Issues


jakecool19
 Share

Recommended Posts

TL;DR: Do not hold right click, or right click more than once when using any pot on a crock

 

Hi guys, I've seen a lot of people, myself included, having problems with crocks having zero servings or less servings than what they put in with a pot. I've found that you can still use the crocks, albeit very carefully. First, to get food into the crock properly when you have your pot of food do a quick tap of the right click button to transfer the correct amount to the crock. Do not hold right click or right click more than once! This will cause servings to disappear losing valuable saturation. Likewise if you want to put the max amount of servings in a crock(4 servings), then make sure you put that amount in there to begin with. Say if you make 6 servings in a pot, and put 4 in one crock and 2 in the other. If you make more servings and try to fill the half empty crock, it will just reduce your crock servings AND your pot servings. The math is really funky. Finally if you use exactly 4 servings in a pot and transfer them to a crock you will be left with zero servings in the pot making it unusable. To fix this get a bowl, place the pot on the ground and take the imaginary serving in the bowl and enjoy an imaginary meal and your reusable pot. Hope this helps someone prepare for winter!

Link to comment
Share on other sites

  • 2 weeks later...
  • 1 month later...

Another way to make sure you don't lose any meals due to this bug is to not do things in a way that even has the possibility of triggering it.

It is triggered by POURING meals FROM the clay pot INTO crocks or bowls.

The way to completely avoid it is to TAKE meals OUT of the clay pot WITH crocks and bowls. You never even have to remove the clay pot from the fire, as meals can be gotten out of it directly while it is still sitting on the firepit. And even if you do remove it from the firepit, all you have to do is set it down and it is ready to have meals removed from it. Voila!

Problem solved, nice and easy.

Also, Tyron has stated that this issue should be fixed in 1.14. So, hopefully after that nobody will even have the possibility of triggering it anymore.

Edited by Robert Johnson
Link to comment
Share on other sites

  • 2 weeks later...
  • 3 weeks later...
 Share

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.