Open grady404 opened 8 years ago
As a (less user-friendly) alternative you could just force the user to save the level before playtesting it. Although from what I get at you'd have to redesign the way levels are loaded/saved in order to do that.
The reason I used the temp.json
file to begin with was because the way I was storing the leveldata, in JSON, was not working with get
, but I haven't tried post
, though if I use post
then that would make transitioning between levels from other levels much more difficult.
I would actually just force them to save it before they play it. Lots of games do that already, and for good reason. If something glitches out and the game crashes, they won't lose their level.
See Issue #58; I think that once we overhaul the level editor saving system like I said in that post, that might put the final nail in the coffin for temp.json
, or .last-opened.json
, or whatever we call it now.
??? You didn't even redo the level editor yet.
It's strange, just get rid of it. Why do you need that there to be able to play unsaved levels in the editor? Can't you just pass the level in through a get/post request or whatever? Getting rid of temp.json should also fix the level editor bug, without you having to think too much about it, so I highly recommend doing so.