sage steppe
Hi all, I'm not sure if this fits more as a design question or a scripting question. If it seems more appropriate elsewhere I'll delete and remake the thread there.
I have a puzzle game with a level editor. The level editor saves the level the user is working on as a json.
The idea is that if the user really wants to for whatever reason, they can edit the .json directly instead of using the in game editor.
Now, I'd like to make it so that a user's level cannot be "published" before they have solved it themselves. I was thinking of doing this by having a "solved" state also being saved in the json, but the user could then edit this solved state if they really wanted to.
Ultimately I think this means I either save the entire level in a way where it cannot be modified by the user outside of the application, or I track the "solved" state separately. Any idea on how I should go about doing this, or any resources that talk about this general topic?
Note, I have not implemented any sort of "publishing" system yet, I'm only beginning to think about it now. So I haven't really thought about how sharing levels between players would go.