I am having an issue regarding player state.
I am the builder of a world that is used by students elsewhere. My workflow is that I build and code in Minecraft: Education Edition and then export the world file and send that to educators who host the world for students to play in.
My team are the only ones to have entered the world at the point it is exported, so any player data included in the export should only be attributed with our player IDs which never enter the hosted version played by students. Likewise, every student who joins should be--as far as the world file is concerned--joining for the first time.
And yet, I am getting reports of players (joining for the first time) spawning in outside of the cordoned areas, in creative mode, and with objects in their inventories. After a little while I have figured out that these reports coincide with my player state when I logged out before export. These players are inheriting _my_ player state, when they should be inheriting the default state (spawn at spawn point, map default game mode, empty inventory).
I have taken to returning to spawn, reverting my gamemode and emptying my inventory before I log out and export the world, but I would prefer a more technical solution. And I have reason to believe students are then occasionally still inheriting each other's player states (journals missing, weird spawn locations, etc.). I'm about at the point where I'm going to need to install a Windows VM with Microsoft Access to poke around in internals of the world file and see if I can scrub my player data or something.
Is there a better way to reset the player data associated with an exported world, or ensure they don't get crossed over between player IDs?
Post is closed for comments.