Hooray, another post from me..

 

Anyway, I've worked with bukkit quite a bit, and using its storage methods (I.E. config files, txt files, sql, etc..). Obviously some are better than others depending on the circumstances.

 

For forge however, I haven't looked into data storage too much just yet, and I was wondering what sort of options there are, and what the best options are in a case of just storing pure data, where the structure doesn't need to be changed but the data does.

 

EDIT: For reference, assume the data is all being stored purely as text (Strings)

It does not need to be edited externally, it's used purely for mod storage.

 

This being in terms of reliability, stability, efficiency, and usability.

Feel free to post opinions and such.

Interesting topic.

 

You'll have to be a bit more specific about the kind of data, access and modification you require, though.

 

There is no catch-all storage method.

Edited post, thanks

 

 

You've mentioned the kind of data (basically your description is "random data" so far, which is the worst kind of data to store), but not the access and modification you require.

 

Without this info, anyone would be hard pressed to make suggestions for a storage model.

What is it you're trying to store data about? Players? World? Also, do you want to be able to manually edit the data through config files, or do you want it to be stored in the world?

The data being stored is just pure text, basically (Assume the amount could be arbitrarily large, or potentially small)

Data does not need to be edited manually, just by a mod. It should be stored outside the world though.

 

I'm using NBT

 

https://gist.github.com/9e322275b48c317eacab

Any specific reasons for that

Easy to use + all minecraft data stores in NBT.

NBT is Minecraft's in built storage system. Need I say more?

But if you want to store data directly to a player you probably want to use IExtendedEntityProperties!

@Kriki98 That's NBT... All it is is a wrapper for it really.