Dauron

I messaged you with some suggestions on Discord. Has anyone else had any issues with 1.17.6? I updated and my test world loads fine so I'm not sure what the issue is.

Thank you! I will include it in the next release.

This only adds the smaller chest sizes. I may consider making double chest ones in the future.

Yeah I have a version ready but I'd like to wait until 1.15 is stable before releasing. Sounds like maybe in the next day or so.

Posted a new version 1.4.0 for VS 1.15. Though I had no issues using the previous version on 1.15. I will update on the MOD DB once 1.15 is stable.

I'll try to update it in the next day or two. Thank you for your patience.

I made an edited version for you to allow back carrying. Just remove the version you have and use this one instead. If you're on a server it needs it too. It should cause no issues but it's recommended to make a backup of your world whenever updating mods. Download: ExtraChestsCC_v1.3.1b.zip

Any mod that changes default stack sizes is going to cause a lot of issues eventually. I can't support or really even test this because it's possibly unrelated to my mod. Ideally if you're going to use mods that change stack sizes it should be in place at the beginning of a server not after it's already been live for a while. Unfortunately I've gotten away from VS modding for a few months now and my time to fix issues is limited. I'm only going to be able to fix issues that are directly related to my mod as is and not caused by interactions with other mods. If the mod that is changing stack sizes is changing many items then it's definitely something that should be put in place from the beginning. If it's only changing a few items out of convenience then it's possible to edit/remove the patch files for the stack size changed items and change them back to default values. That's all I can really suggest for now.

I'm posting a new version now that will fix that.

Please look at Known Issue #1 in the original post. You'll need to lower your GUI scale in the game options or move the inventory windows manually for the bigger chests. The GUI issue is something that can't be fixed with a content only mod.

You need to have the mod updated to 1.2.5 before loading your world in 1.14.5 for the first time. Hopefully you have a backup of your world. Updating the mod after they're empty won't fix it.

While all of your suggestions are possible, this mod doesn't include any code. It is a content only mod, which means it relies on the vanilla code for the chest mechanics. I will think about it in the future but right now I'm heavy into development of my next mod so I can't make any promises if/when it will happen. Thank you for your input.

It sounds like you updated this mod after the issue presented itself. You need to update the mod before loading a world for the first time after updating from VS 1.14.2 to VS 1.14.3 or higher. Updating the mod after the world has loaded in and saved can't fix the problem unfortunately. If this is not the case then I'll look into it further, but I know of servers that have not had any issues with VS 1.14.5 and they're using either 1.2.4 or 1.2.5.

I think some mods need to recompile for 1.14.3 so that's what I'm doing. Posting a new version 1.2.4 shortly. Will be 1.14.3 compatible only. This won't fix an already loaded world where the crates are empty. You need to have the mod updated before loading into 1.14.3 for the first time.

Which "certain" chests? A popular server with a consistent 15+ people on it have been using this mod since 1.14 release and this is the first I've heard of this issue. Do you have other mods installed?

Are you using the latest version? I haven't heard of anyone having this issue since I fixed a while back.

You mean allow a meteoric iron plate to be used in place of an iron plate to make an Iron Chest? I guess I could add the recipe but it seems kind of wasteful. Unless someone is really having a hard time finding iron to make into steel and has lots of meteoric iron laying around.. I'll think about.

It doesn't fit my view of upgrade progression properly for these so I've decided not to include it.

Yeah, I was wondering when the question was going to be asked. Updated it just now.

I updated the mod. Server and clients will need it. Should fix the issue with the crocks. Let me know if you are still having issues.

In the mod zip file you would need to replace the 2 files under assets\extrachests\blocktypes with these two files: chests.jsonlabeledchests.json I changed these files to include the back carrying. I did not include back carrying by default because it's too powerful. If you are on a server the server needs to do the change as well. The server dictates the allowed behavior. Hope this helps!

Thanks for the report. It appears that when a crock is fresh made in the firepit it doesn't have an attribute of "sealed" set yet. Once it's placed on the ground and picked back up it then has it. This doesn't mean its actually sealed it just has the info set to either true or false. So there is basically 2 kinds of crocks that a crate should allow: one's that are fresh made and never placed down/picked up, and ones that have been placed down/picked back up. That's why they aren't combining in a crate because the vanilla "equals" method sees one crock with the "sealed" attribute and one without. I only had to place a crock down once and pick up to fix in my testing. This is a vanilla bug with the way crocks are handled, it's not noticed because you can't stack crocks in your inventory as they only stack to 1. If you could then your inventory would have 2 different empty crocks that don't stack together. To make sure they all stack properly in a crate you should only need to place it down and pick up one time if it's freshly made and then it should match all others that have been handled the same way. In my testing I also noticed something else about the crocks (and bowls) that I didn't realize was happening. I'll be working on a update to address all of this over the next day or two. Thanks again for the report. It's hard to test everything.

Sometimes if another mod has an issue either with a crafting recipe or whatever it can create a chain effect for others. The first mod that throws the errors in the log may be the culprit. It's possibly looking for an item that doesn't exist anymore. One item in particular that got changed was the sword, the code used to be "sword" and now it's "longblade". So any mod that made custom swords would have to update their recipe files to account for that. I haven't had any other reports of issues and I know of a server or two that has this mod working just fine. I've made multiple worlds to test 1.14 compatibility. If you figure out the problem let me know as I'm curious. Unfortunately there's nothing I can do with this mod to fix the issue you're having. Good luck!

Good to hear, have fun!

Thanks for reporting this. I'm not really sure what happened, but I recompiled the mod and it seems to have fixed it. Uploading version 1.2.2 now. Please try it out and let me know of any other issues. Thanks again!