Alright, I'm trying to figure out how to handle data storage for information that needs to be accessible from the world.

It's essentially information about a player entity, but needs to be accessible from a tile entity while the player is offline, hence I can't use extended player data, I need to save it to either its own NBT file or to the main world data file.

 

Having trouble implementing this.

 

I found one solution that extends WorldSavedData, but there were a few errors (such as no providing a proper constructor) that I am not sure how to solve.

 

Eg. the constructor used was one that takes no parameters, but WorldSavedData doesn't have a matching constructor, as its only constructor takes a string paramter, but I am not sure what I should be passing.

 

I also am not sure if I should be instancing this class once for my entire mod and storing each player's info in it, or if I should be using one instance per player (and what the differences in construction would be; that is not the read and write NBT parts).

 

Help?

I know diesieben07 has done something similar. Here is his code on this matter:

https://github.com/diesieben07/Questology/blob/master/source/demonmodders/questology/QuestologyWorldData.java

 

Don't ask me how he does it.. As you know I am trying to figure this out but with Player data

Each WorldSavedData has a unique identifier (for maps this is map_0, map_1 and so on).

That is the parameter the constructor takes.

Also think about if you want actual per World (=per dimension) storage or just a per map (= per save) storage.

For per world use world.perWorldStorage and for per map use world.mapStorage.

Then to create a new data use

YourAwesomeData data = new YourAwesomeData("IDENTIFIER");
world.perWorldStorage.setData("IDENTIFIER", data); // or world.mapStorage

To get that data back any time use

YourAwesomeData data = (YourAwesomeData)world.perWorldStorage.loadData("IDENTIFIER");

loadData will return null if the data has not been created yet.

Thats it. Just be sure to always call markDirty() on your data when you change a value, otherwise MC will not save it.

If you want an example look at the link Mew posted.

 

Ah ha.  Thanks.

 

I definitely don't need it per dimension, just per save.