[quote] Just putting another alternative I was thinking of, saves a trip to the site to manually adjust settings: (default is ticked, and just a quick example of course)
[/quote]
What happens when you forget you unchecked that and accidentally save to an uncopylocked place? What happens when someone has that box checked and “omg where’s my place?!” only to find out minutes (or hours if they didn’t know it existed in the first place) later that “oops that box was checked”?
I take it you’re referring to having to go to the site to lock or unlock the place. That just means we need a better game explorer – it’s not something that you’ll be changing constantly on publishing it. The only reason for the overlay is to warn you that you’ll be uploading to an uncopylocked place, and that’s something that’s relevant each time you publish the place. The check box isn’t very intuitive already – I couldn’t tell if you meant “show only copylocked” or “copylock it when published if this is checked”. You’d also have to spam that back and forth if you were updating an uncopylocked place and copylocked place simultaneously. A place being copylocked is related to the place and not publishing – it belongs on the place’s configuration page.
This is live on production.
I’m not too bothered when I find out my place is uncopylocked, because people will still know that I am the original developer, cause I’ll have the version with the most visits. Also remember that this happens to nearly all developers, you’re not the only one. It happened to me years ago, and it absolutely destroyed me, shortly after though I realised that actually, stuff like this happens all the time, there’s no need to lose sleep over it.
Can we get some sort of hint while trying to publish it too? In the past I’ve tried to re-use places and accidentally published over uncopylocked places – multiple times at that.
Can we get some sort of hint while trying to publish it too? In the past I’ve tried to re-use places and accidentally published over uncopylocked places – multiple times at that.[/quote]
Reusing place slots is generally a bad idea, so I don’t think it’s worthwhile to add a check for people who follow this practice.
If people are accidentally publishing to the wrong place slots, that’s a different matter.
[quote] Reusing place slots is generally a bad idea, so I don’t think it’s worthwhile to add a check for people who follow this practice.
If people are accidentally publishing to the wrong place slots, that’s a different matter. [/quote]
I blame the inability to archive places. “Oh let me find that one project I worked on a while ago” scrolls through 100s of places If we just keep creating places our places just become unmanageable. It feels much nicer to reuse places and keep your place count down. If we could archive places I’m sure pretty much everyone who reuses places to prevent an unmanageable inventory of places would create new places instead of reusing them.
