Posted June 11, 20169 yr I am working on creating a Quest Book. I have all the core functionality down, but I can't find a good way to store the data. I've decided NBT is the best idea, but I have no clue what things I can attach NBT data to, and what would be the best thing to attach it to? The data can't really be added to the quest book itself because what if they loose it? Also I want to data to be the same for each player, so preferably something that the data could be saved to on the Server Side? Can somebody suggest what would be the best thing to do?
June 11, 20169 yr I answered this in your previous thread. Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.
June 11, 20169 yr Author This article mentions manual synchronisation between server side World Save Data and client side, how would I manage this? Would I just regularly have to update them all?
June 11, 20169 yr Quest progress should probably be saved using a Capability attached to the player, not using World Saved Data. Whenever a value changes that the client needs to know about, send a packet to update it. The site I linked previously also has a section on networking, including the Simple Network Implementation (which you should use). Please don't PM me to ask for help. Asking your question in a public thread preserves it for people who are having the same problem in the future.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.