Hi. Thanks for reporting! Trying to understand the case here. Did you make any edits to the experience before publishing? One known behavior is if studio goes through consecutive publish or save and publish without edits in between, the second publish does not create a new place version.
Edits were applied, parts were moved. If you do print(game.Version it will say the PlaceVersion number of the place.
After publishing and printing again, it will still be the same PlaceVersion number. In my case, I was logged into the session and it printed “26”. After publishing a new version, it still said “26”.
I found a work-around. Going to the Game Settings after publishing, you can see the accurately published number under Places. So the functionality is there.
Sorry for the bump, but I am having the same issue! Working on a fighting game and the place is stuck on version 2450. Nothing I am doing seems to be fixing it. Everything is fine in studio, but when I go to play the game in the regular game client, it is not there. Has any real solution to this problem been discovered?
Hi! We spent some time evaluating this field and found it to be conceptually problematic in edit sessions. The reason is that when editing, the place is newer than the latest saved version, but not the latest saved version + 1 yet until the next save returns success. In other words, this field cannot be made consistent with the backend when there are edits in studio. This issue however does not exist in play mode as we are loading an immutable place version to game server and we are serving this field accurately in that case. The conclusion we reached was we will keep this field in the data model, and it will be accurate in game sessions, but we will leave the current state in edit sessions. Sorry for the confusion.