Hello,

 

It's been a long time since I've posted here and I've come across a hitch in my mod. I was designing a forced-progression type mod for my server and I was wondering how I'd store the player data of the mods he is allowed to access. I've ultimately decided to use the player NBT but have a few questions. Should I store the nbt tag using the EntityPlayer.getEntityData() or use a separate data file like I've seen Thaumcraft use.

You should use IExtendedEntityProperties. It has many advantages over getEntityData, not the least of which is that it performs better because you are not constantly reading and writing to NBT.

So... Is there anything easier than that? Like I know thaumcraft has <my uuid>.thaum in the playerdata folder.

What about having a data watcher? Do I need that?

That would be more complicated. Because you have to write all the I/O stuff yourself.

Seriously, IExtendedEntityProperties is really simple. One class that implements a very straightforward interface and one event handler. Done.

 

The data I/O isn't that bad, if you really, really need it.  All depends on what you're trying to do.

The data I/O isn't that bad, if you really, really need it.

Why are people always so eager about re-inventing the wheel?

 

Because then the wheel is yours.

And as I said, only if you really really need it.  It's highly likely you don't, but I had one use-case where there wasn't a more appropriate place to put data.  I probably could have used

worldSaveData

, but due to the size it probably wouldn't have been a good idea.  It was also good experience reading and writing my own NBT files, I learned a lot about some particulars of the Minecraft internals.