You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The configuration, patchItemSave, clears all items from the world on either manual save (i.e. pausing the world on the client, or running /save-all on the server), or periodically by the auto-save timer.
Steps to reproduce.
/save-all, pause the game (client only), or wait for the auto-save timer. This may also apply when you stop and start the world on the client due to the potential of two save rounds occurring, one for pause, and one for server shutdown.
Notice how all items and inventories that stayed after the save round has disappeared, or has been emptied.
Disable patchItemSave by setting the value in the config to false.
Possible fixes
Call the alternative save function when the inventory is known to be destroyed right after. This would include going through a portal or going into unloaded chunks.
The text was updated successfully, but these errors were encountered:
I'm pretty sure I meant to implement this as if inventory would be destroyed afterwards, as you've mentioned in Possible fixes. I'll release a version without this as it's clearly not the intended thing
Description
The configuration,
patchItemSave
, clears all items from the world on either manual save (i.e. pausing the world on the client, or running/save-all
on the server), or periodically by the auto-save timer.Steps to reproduce.
/save-all
, pause the game (client only), or wait for the auto-save timer. This may also apply when you stop and start the world on the client due to the potential of two save rounds occurring, one for pause, and one for server shutdown.Cause
Line 26,
this.setCount(0)
GolfIV/src/main/java/org/samo_lego/golfiv/mixin/duplication/ItemStackMixin_SavePatch.java
Lines 22 to 37 in 354e9bf
Current Workarounds
Disable
patchItemSave
by setting the value in the config tofalse
.Possible fixes
The text was updated successfully, but these errors were encountered: