I think there already was this suggestion. Unfortunetaly I won't implement this. I'd have to create an entity definition for every possible combination of every possible way of creating a merged chest. If you would try to create 3x3 chests I'd have to have 1 entity for:
- 9 wooden chests
- 8 wooden and 1 iron chests
- 8 wooden and 1 steel chests
- 7 wooden, 1 iron and 1 steel chests
- ...
And if I'd added support for bob's chests there would be EVEN MORE combinations. There would be also a problem when just trying to split these chests, because I'd have to keep in memory some data about what chests were merged.
About adding support for bob's new chests: I looked into it before and decided to not implement it (i don't remember the exact reason, I'll have to check again if I was just lazy or if there was some actuall problem). I'm currently rewriting the merging logic so I'll take a look if it could be implemented.
And about your long loading time. This mod can increase your loading time a lot if you increased max area, width, height settings. If that is the case I'd suggest either lowering the limits or using the whitelist setting (if you really need large chests).
Ah, I understand the issue here. I was thinking more along line of wooden explicit merges/iron explicit/etc. and didn't realize how your mod was setup. The loading times isn't from your mod explicitly, it's just having (checking current mod count...) 119 mods installed lmao.
Thanks for the response though, and thanks for keeping this mod up to date!