This is why you shouldn’t let dev’s play with a feature like this
@InYo22 I just joined the group for that game, please grant me edit privileges, it will help me diagnose the issue
Will do.
Outside of the replication issues with terrain, I haven’t had issues replication wise. Camera scrolling is weird though.
It could be cool to have different selections for each different user, e.g. every editing user would get a random colour that is used for selection boxes. Additionally it could be made so that your own selection is always blue and the colors of the others are different.
Also, could we have some sort of refresh option/hotkey for scripts, so that you can let the script update for others without having to close and re-open it? Or are you planning to implement a whole collaborative text editor eventually?
If you are getting errors in the output window that mention PlaceLauncher.ashx, then try checking to see if you have an HTTP proxy running on your computer, it may interfere with joining.
There should be a confirmation dialog when you click cloud edit. I just accidentally cloud edited a live game and then it started auto publishing what I was working on.
Would be nice if the animation editor worked.
Yeahhhh
The smooth terrain tools are pretty laggy, other then that everything seemed perfect
Really enjoying this feature!
After creating a union and rejoining it becomes impossible to separate the union.
It would probably be better indeed if we have to save manually.
(There can be auto-save on the client’s pc though, just in case)
Sometimes you derp and want to restart studio without saving.
With the could edit that would mean reverting versions…
[quote="einsteinK, post:76, topic:20432"] (There can be auto-save on the client's pc though, just in case) [/quote] It already autosaves -- same as any other place. As for manual saving, I think OP said they were thinking about manual saving in-game, but don't quote me on that.
I’m pretty sure game:SavePlace() works fine.
The autosave is also done by the GameServer.ashx, so it’s very easy to remove.
Actually, they could easily hook into chat that allows players to save by saying “save” or something like that.
(Using an event RobloxReplicatedStorage the client can receive a success/error a notification or a message in chat)
So a few first impressions from me:
Are the player icons in studio temporary?
It looks kinda pixelated and ugly.
Maybe you guys should use the headshot icon (with at least a 32x32 resolution, if possible)
Also, the NetworkClient should probably become an invisible service. I can see & change the Ticket property, which is kinda weird.
Will anything be implemented to prevent others from deleting players through the explorer, or malicious code that could allow them to disconnect clients, or do we have to manage that on our own?
@VetexGames and I tested and it seems you can’t delete or kick other players through the command bar or explorer
Does it throw an error, or does it simply not do anything?