shutting down all servers will result in team create session closing (unsure if this was fixed)
when roblox updates, team create will close, and not save, losing hours of progress
there needs to be constant local backups, because if roblox servers have connection issues, shut down, or any other reason. We need a guaranteed good way to keep our game progress safe.
Making code changes, and publishing without closing the script tab will not save your code progress (had this happen to me a few times)
I’ll post more once i get a response from shaylan007
I am in a dev group, and we have a place that has had TeamCreate on for a long time and has worked fine. Today, none of us were able to get into the team create session. When we clicked on the place in the start page in studio, it showed the small popup for “Requesting access”, but the Output showed no HTTP requests going out to connect, and it was just stuck. But if I joined the game as a regular player, then shut down all servers, we could get in again.
Yeah, it’s unfortunate how Team Create is managed from the session rather than the site. If you have an issue that prevents you from joining, you’re locked out of the place since you can’t join to turn Team Create off. And if you need to shut down the Team Create server, you have to shut down the entire game, booting out everyone who’s playing in addition to those in Team Create.
Sometimes this happens when I try to edit a script:
It tells me I’m already editing and reverts any changes I try to make.
This time exiting out of the script did not help, while it usually solves the problem.
I closed studio and reopened the game and all my changes to that script from the past 3 hours or so were gone. During those 3 hours I had also opened, closed, and edited the script several times.
Is there a way to shut down team create servers in the event someone was to leave for a 2 week vacation stuck in a script, or a bug causes someone to be unable to connect, etc?
A lot of the time team create bugs can be worked around because we can shut the servers down. If there’s no way to forcefully kill a TC server then a bug may render the entire feature useless for a period of time.
I assume reverting to a previous place version would shut servers down? If so you can revert to a previous version and back to shut down the servers until we get a proper way of doing it.
That’s a really roundabout way of doing something that already wasn’t ideal to begin with. Running Team Create on production games and not wanting it to be shut down is less appropriate than needing to shut down Team Create on a dev environment, so until there’s a dedicated feature for shutting down Team Create servers (e.g. disabling from the site) the old behavior should be preserved. This was already “fixed” and then later reverted in the past as well.
Yesterday we released a fix for this issue. If user is inactive for more than 5 minutes the lock can be re-acquired by other users. Also TC server dies automatically if there are no users connected to it.
This just happened again, without any sort of obvious weird script locking behavior occuring. I lost about 4 hours of progress over 3 different scripts. I don’t know what the heck is going on, but I’m not using Team Create again until stuff like this is fixed.
We’ve recently resolved an issue with users not being notified in a timely fashion when a Team Create server is shut down. This fix should be released soon.
We’re now currently working on other Team Create bugs in this thread, such as Team Create being stuck on “Requesting Access…” when opening certain places.
When you create or insert a terrain region in a team create it instantly crashes the team create, and if you have a terrain region in a place when you turn on team create it will lock the team create since it will crash when you open it, making so you can’t turn team create off.
When I make a team create I can’t get back into it! This has been happening with all forms of team create whether it be owned by a person or a group. Team create is proving to be insanely unstable lately. If I could even count all the problems I have had with team create. So far it has just been a very bad experience for me.
