I had this problem also when working with my friend on a game. The solution was to commit edits to all of the scripts that were edited.
I did this by clicking Publish To Roblox, then I was prompted with an option to Commit All Edits, once I did that my friend could see my progress on the game when in team create.
I tried to recreate your issue but was unable to. Here’s what I did:
Create a new game called “MainGame”, turn on TeamCreate
Add a new place to this game via AssetManager called “ExperimentGame”
Open “ExperimentGame” and turn on TeamCreate, close “MainGame”
File → Publish to Roblox As, select MainGame (Experience) then select “MainGame” (Place) within and click Publish
Go to the Configure Place, Version History page on roblox.com for “MainGame” (Place)
Observations:
Within Version History page, there is a recent version that marked as published reflecting the publish action I took in step 4 above
The contents of “MainGame” place were successfully overwritten with contents of “ExperimentalGame”
This may have been fixed since the time you originally posted this report. Could you please check again when you can?
You should also notice a recent update we made that fixes and clarifies a lot of output messages like the one you noticed in your original report. See Improved Save Messages & More for more information.
Please don’t hesitate to reach out if you are still seeing this issue, or have any questions. Thanks!
Could you please clearly describe the actions you’re taking to reproduce the issue, similar to how I outlined steps 1-5 above? I want to ensure we are both aligned on how the issue is produced.
Something else to try: could you please follow steps 1-5 in my post above to see if you are able to reproduce the issue with a new place? I see the version number is very high in your screenshot so I’m assuming you are trying this with an existing place. This will help determine the scope of the issue.
Were these steps completed with a brand new place or were you still testing with your existing place? If the latter, could you please try reproducing with a brand new place? I would also suggest trying without people in the same place to eliminate other variables that may be causing this bug. Thanks.