A service where you can put guis in to preview and build them and not have to worry about cleaning them up when your place runs. I’m tired of running ClearAllChildren on all of my gui containers when the game starts.
1 Like
Honestly I think this is just creating an service because we can… I think that a property for a ScreenGui instance would be a more reasonable request. Like ‘PreviewMode’ or ‘StudioOnly’
Just make a plugin that creates a Gui named “MockupGui” in the StarterGui and then removes it from the player every time you Play Solo.
Just use StarterGui and set Archivable to false?
When Archivable is false, that instance won’t be saved when you publish.
This is what I’m trying to avoid
And then my mockups will disappear if I ever close studio
You can have a plugin that saves a copy somewhere in ServerStorage or somewhere idk.
Then whenever you reopen the place, it just recopies it from SS to StarterGui and sets Archivable to false.
That’s a ridiculous minefield. Just because there is a workaround doesn’t mean there shouldn’t be a feature.
1 Like
Once I’m done with my current task, I’ll quickly write the plugin because I’ll probably be bored.
It would be better to put it in an archivable=true item hidden from the explorer (e.g. Geometry) so you’re not littering the explorer with a backup instance that’s irrelevant to the end-user. Either way, I agree with Ethan. Clean and expected behavior shouldn’t be turned down because there’s a workaround, especially considering that most people aren’t going to find your plugin like they will the feature.
ServerStorage was just a quick example, I’m not keeping track of hidden services that save.
I never have this problem, since all my GUIs have localscripts, which “reset” the GUIs when they run.
I don’t think you understand. That is the problem. The production GUI container should not also be used for making designs and mockups. There is no point in overlapping those two roles and it just makes mockups more annoying to make.
1 Like
Isn’t that like saying there should be an alternative to building models in the workspace, because it’s hard to experiment with new building styles if the workspace is also cluttered with maps for production? If you don’t want to give your experimental GUI’s scripts that remove them when a player spawns, it’s probably just better to put those GUI’s in the ServerStorage before publishing. It only takes a few clicks.
3 Likes
I’d just build in a new place and I do the exact same when designing GUIs.
Gui creation needs an overhaul. I think Gui’s should be created by an auto-generated script, and it should be possible to use custom lua forms, similar to visual studio.
2 Likes
No. You can build in the workspace away from your map. Working in the StarterGui directly interferes with finished UI and can be seen by players when it shouldn’t (not finished yet).
1 Like
I was bored…
If you open a place where you didn’t save any GUIs yet, you’ll have to press the EditGUI button.
It’ll create a folder “EditGUI” in the StarterGui.
You can put GUIs in there, edit them, have fun, …
When you publish the place (or save it to file), the EditGUI folder won’t be in the StarterGui.
If you reopen the place, the plugin will readd the EditGUI folder.
You can always press the button to show/hide the EditGUI.
(In case you want to hide the GUIs temporary or destroyed the folder by accident)
(Destroying the folder (by accident?) isn’t a problem, you won’t lose any GUIs that were in it)