28.01.2017, 18:46
I can't help you here more as I can't see the code, however here is the main debugging test I want you to try.
Make a command called "/SaveMyAccount", run the command DON'T quit. Does it still contain 0, 0, 0, for the player position?
If yes, your saving is bugged post your code.
If no, your getting the position too late in your save procedure... fix it yourself or show code.
Also position should be one of the high priority things to save, therefore get this information and store it first or atleast format it into a string first. I suggest this as if it's one of the last things saved it could be the player has gone already and getting a position from a player that's gone... well it's 0, 0, 0.. A.K.A NULL.
Make a command called "/SaveMyAccount", run the command DON'T quit. Does it still contain 0, 0, 0, for the player position?
If yes, your saving is bugged post your code.
If no, your getting the position too late in your save procedure... fix it yourself or show code.
Also position should be one of the high priority things to save, therefore get this information and store it first or atleast format it into a string first. I suggest this as if it's one of the last things saved it could be the player has gone already and getting a position from a player that's gone... well it's 0, 0, 0.. A.K.A NULL.