Containers do not network the correct component data for the entities inside them.

[Princess-Cheeseballs]

Title.

I've encountered this twice now so I'm pretty confident this is an engine issue with container networking, and is a pretty big blocker for status effect and storage prediction in content.

To reproduce on content:

• Use Meth
• Check the status effect in the clientside container.
• Check the MovementModStatusEffectComponent on the status effect entity
• The numbers are wrong

I also ran into it when trying to fix the item resizing bug in bags, and predict item resizing as well as other parts of item storage. When the bag would be updated, the container would have the incorrect size of the welding torch on client, causing the client to think it's taking up more or less space than it should be. I.e. if it was activated, it the client would think it's a 1x2 Small but if it was deactived, it would think it's a 4x2 Large.

The sprite would be correct in the inventory though which means the client does have the correct data, and it does update properly, just not when dealing with containers.

Despite the welder being turned off, the slot is red because the last server state told the client that actually the welder is large and is filling up the slots to the right of it. This is purely a clientside misprediction.

The above prevents us from fixing the bug where welders and energy swords can be resized even when they shouldn't fit.