Clientnbts stored in the wrong place
TheKaratCake opened this issue · 8 comments
I'm no expert on this but apparently in the fabric version certain nbts are stored in playerdata, not having that breaks just, so much and is making me do a lot extra work, please can you fix this
What exactly do you mean by this?
If you're saying that ForgeCaps and cardinal_components should be the same, unfortunately that's something that shouldn't be fixed because we should be using standardised Forge things when possible to ensure compat, even if there is a minor difference.
Well, my example is that the mod figura cannot communicate with origins on forge but can with origins on fabric due to where something is stored, some form of data, the quote from the person who was explaining this to me is as follows: "figura cannot access random data. The only reason this works is because official origins graciously puts all it's data into a common data area: player nbt"
Yeah sorry I don't now what else to tell you other than it doesn't work with forge origins
Well, my example is that the mod figura cannot communicate with origins on forge but can with origins on fabric due to where something is stored, some form of data, the quote from the person who was explaining this to me is as follows: "figura cannot access random data. The only reason this works is because official origins graciously puts all it's data into a common data area: player nbt"
Origins Forge should too. I don't have access to my pc atm, but search through the ForgeCaps nbt tag.
The location won't be changed because of loader differences, but, Origins are stored in player nbt here too.
I hope so, can you make sure theres a 1.19.2 version with it fixed, that's really important for my like, everything
