Describe the Suggestion

Recently I've encountered issues with packets being too big for Minecraft's standard and Create's cart contraptions.

If I understood correctly, said data is stored directly in the NBT of the item.
With some contraptions this can cause too big packets, to a point a player could effectively ban themself because of it, stuck in a kick loop.

So let's discuss a possible change to fix this issue with a fundamental rework of the technical side of it.
Let's take a prior art in the matter: Vanilla's Map Item.

Map items are simple if you look at their NBT: they only store an ID. Said ID refers to a stored NBT file on the server, there's also packets to send data separately to the client.

So here's the idea, what about applying the same technique to the cart contraption? I'm not seeing any need in syncing that data to the client too right now so maybe the custom packet can be discarded.

I hope this can be taken into consideration for any future refactors, as this could help reduce any issues of the same kind.

Screenshots and Videos

No response

Additional Context

No response

Contraption's data is stored directly in the NBT of the item. With that, they can be easily shared between worlds and players; you can copy / paste the code and create the same contraption easily; you can treat them as a "starting gear" or duplicate them using creative tools (Storage Drawer's "Creative Vending" upgrade)

Maybe make it configurable.