Important - Shutting down TC servers was broken again

Bug Reports Website Bugs
19

Thanks! I will provide as much as I can on my end.

Main:

The most critical piece of feedback is that whatever ROBLOX is trying, it’s not working. It doesn’t matter what the intent was – the effect is that the bugs haven’t been resolved and developer experience has worsened because there’s no workaround. ROBLOX is actively pursuing a course of action that has failed to improve developer experience and only worsened it.

There is currently a partial fix for the TerrainRegion bug on the way, but at what cost? Developers have been being locked out of Team Create with the disabled workaround. Fixing the bugs doesn’t require there to be no workaround, so as far as we know, we’ve actively been ruining developer experiences for some trivial design ideal. If the workaround was to be disabled, it should have been done after the bugs were resolved for the most part – it was a mistake to disable it when it was most critically needed. Again, it doesn’t matter what the intent was – the effect has been disaster.

If the workaround was disabled for a reason other than a design ideal, that needs to be communicated to us. The lack of a workaround is severely impacting developer experience, and we need to be able to convince you it’s needed temporarily until issues are largely resolved.

Addendum:

This thread leads me to believe that one of the potential issues is “Users complain that TC is unstable/unreliable, but we don’t get enough bug reports to fix these issues. Maybe if we disable workarounds it will encourage more bug reports”

Response:

As a living devforum encyclopedia, I have read nearly every topic/post on the developer forums – there is not an issue of lack of TC bug reports. Here are the reasons why TC is reputed for instability:

Team Create did not autosave open scripts:

This was an issue upon release. We would work on scripts for hours without closing them, and then we’d disconnect due to our network connection or crash ourselves accidentally in Play Solo. Since the opened scripts weren’t autosaved, we lost hours of work. This really didn’t help Team Create’s first impression. It has since been resolved with the TC script recovery feature.

Bug Reports/Feature Requests:

Team Create did not publish open scripts:

This was a major issue upon release. I assume the reasoning was something like “Don’t want to publish an unfinished script and break the game”, but once in the hands of users, we ran into issues where our work was mysteriously not saving. Since we didn’t understand why yet, we though TC was unreliable and didn’t save work. Even when we knew the reason, when we forgot to close our scripts and ran into the issue we’d experience an eye-cringe reaction best pictured as:

https://gfycat.com/ColorfulPlushGarpike

which didn’t help improve our opinion of TC. This has since been resolved.

Bug Reports/Feature Requests:

Team Create “Request publish” did/does not work

When TC was released, requesting to publish the game manually didn’t work. It said “requested server to publish” in the output, and then nothing happened. This was not an issue with us testing before the publishing finished or joining an old server – requesting publish legitimately didn’t work. In my TC game, I resorted to changing the spawn color every time I wanted to publish so I knew if it had updated or not. These three huge data loss bugs in a row for TC established its reputation as unstable.

I do not know if this is resolved. The output message is still the same, and nothing has been done to reassure me that requesting publish works. I still wait a few minutes before testing any changes in online mode because I have no idea if my changes saved or not. I requested that it be changed so it doesn’t ask the server to publish, but it actually publishes and doesn’t return until it’s finished, but nothing ever came of that.

Bug Reports/Feature Requests:

ROBLOX’s backend server issues cripple Team Create

This issue is more recent. We get a wave of TC bug reports about every week because backend services are under stress. This has been going on for months with bug reports not being addressed.

1 Like