bug in multiplayer, appears to be clientside.
Terraria v1.3.5.3
tModLoader v0.11.8.9
modlist:
Shaggy's Addon Race v1.4.3
Thorium Mod v1.6.5.5
VamnKuma's Races v1.1
MrPlague's Authentic Races v1.13.7.3
Magic Storage - Extra v0.5.5.10
when Storage Heart is opened, capacity at bottom left is inconsistent between players. one player shows 264/280 (correct amount on both), while others may show 160/160. for the players showing 160/160, recently deposited items are not viewable and seem to not exist; they also cannot be used for crafting via the Storage Crafting Interface. no changes in our Magic Storage layout have changed in this time.
this bug has appeared and disappeared multiple times over the past day. seemingly occurs at random. restarting the server did not seem to affect it, and certain players leaving/joining fixed it one time, but did not fix it another time. screenshots below are from me and another player, both of whom the bug has affected on and off.
one player's view:
another's player's view:
my client log. NullReferenceException in get_Capacity() seems of particular note:
client_2022-06-01-2.log
bug in multiplayer, appears to be clientside. Terraria v1.3.5.3 tModLoader v0.11.8.9
modlist:
when Storage Heart is opened, capacity at bottom left is inconsistent between players. one player shows 264/280 (correct amount on both), while others may show 160/160. for the players showing 160/160, recently deposited items are not viewable and seem to not exist; they also cannot be used for crafting via the Storage Crafting Interface. no changes in our Magic Storage layout have changed in this time.
this bug has appeared and disappeared multiple times over the past day. seemingly occurs at random. restarting the server did not seem to affect it, and certain players leaving/joining fixed it one time, but did not fix it another time. screenshots below are from me and another player, both of whom the bug has affected on and off.
one player's view:
another's player's view:
my client log. NullReferenceException in get_Capacity() seems of particular note: client_2022-06-01-2.log
server log from same session: server_2022-06-01.log