Collaborate with Comments in Studio!

Hello Creators,

We’re excited to introduce commenting to your collaborative workflows in Studio with Team Create! You can now pinpoint an object in the 3D view to start a discussion with your collaborators or leave to-dos and notes. Communicate with your team, track tasks, and discuss changes directly where you create. This feature is rolling out gradually over the next few weeks, and all Studio users will have access by 05/30/25. Learn more in our official documentation.

ezgif-17ecb60a605072

Create a comment

Team Create must be on to enable commenting. In the upper right corner of Studio, you will see a Comment button.

Screenshot 2025-05-01 at 10.30.34 AM

If you are in Next Gen Studio beta:

Screenshot 2025-05-01 at 10.31.56 AM

Click on the Comment button to activate the comment cursor, then click any object in the 3D viewport to attach a comment. Whether you’re reviewing a design element or map arrangement, your comments will be tied to exactly what you’re working on, making them easy to find and act on. Type your comment and press “Submit.”

​​The comment cursor can also be enabled by pressing the keyboard shortcut ‘C’ or clicking the Comment button within the Comments widget.

NOTE: On Roblox, we believe safety is a top priority. To help maintain a safe and positive environment, comments are checked against the Roblox Community Standards. If a comment includes text that doesn’t align with these standards, it won’t be posted, ensuring a respectful experience for everyone.

Tag collaborators in comments

You can tag fellow collaborators in your comment by using the @username format.

When viewing comments in the List View (details below), collaborators are able to filter comments to prioritize those they are tagged in. In the future, collaborators will be notified through email, Studio and Creator Hub notifications.

Studio Comments update in real-time, enabling you and your team to see and respond to feedback as you work. This keeps everyone on the same page without disrupting your workflow. You can also resolve comment threads once decisions are made, and keep your workspace focused and organized.

Locate comments in the List View

You’ll see the list of all comments inside a place sorted by chronological order when you open the Comments widget. You can find the widget under View > Comments.

If you are enrolled in the Next Gen Studio Beta, you will find it under Window > Collaboration > Comments.

“Single-click” on a comment in the list to view the full thread. “Double-click” to fly to the instance in the 3D viewport that the thread is attached to.

In the Comments widget, you’ll also be able to filter the comments to make searching easier. You can currently filter for resolved comments or comments that you’re tagged in. Resolved comments can be unresolved from this view.

What’s next

We are just getting started! Soon, get comment notifications with one-click access, advanced search, and expanded commenting across more object types in Studio. Here’s what we have planned next:

  • Notifications for comments
    Stay up to date on new threads and comments you’re tagged in with notifications through email and the Studio/Creator Dashboard notification trays. These notifications will offer convenient one-click access to the relevant experience in Studio.

  • Easily find and filter comments
    Filter your comments based on a range of attributes to find exactly what you’re looking for. You can filter by the original author, or use the search bar to find comments by typing a relevant word or phrase.

  • Ease-of-use improvements
    We’re improving how you attach comments! Currently, comments can only attach to BaseParts or points in the terrain. Soon, you’ll be able to link your comments to other object types like models and packages. In addition, we’ll add additional entry-points to conveniently leave comments, such as through right-click context menus in the Explorer and the 3D viewport.

Please try out the feature and tell us how else we can continue to improve commenting inside Studio! Your feedback matters in shaping how we evolve collaboration in Studio.

Many thanks to @kresselia1, @shibaxixi, @PixelPlumber, @muddyoink, @desserts_yumyum, @vreddym, @LunaFlare2024, @yipiokay, @cafelucid, @iriszh, @wengawenga, @moodymandymeow for making this happen!

115 Likes

This topic was automatically opened after 11 minutes.

What about studios that could potentially find use for this feature but do not use team create for our development? It would be awesome to be able to put notes down on structures, but it requiring Team Create and not being serialized in place files is a non-starter for us.

I’d also like to use this in my personal projects, but again, I work in local places. There’s no reason to turn on Team Create if I’m a solo dev.

Nether me nor my team can use this if you don’t support it in local files.

31 Likes

Thanks for sharing your thoughts @Dekkonot. Just curious — could you share a little more about why your studio prefers not to use Team Create for development? It would help us better understand your workflow and needs.

2 Likes

In other words: the comments are always going to be filtered making the feature unusable…

because there’s not a single filter on roblox that works properly

but, this is a good thing for teams :man_shrugging:

6 Likes

Lowkey… this is very good and amazing

4 Likes

I second this!

I don’t actively work with other people at the moment, but being able to place comments in a 3D scene would be great QoL regardless, since it would more easily help me remember (and keep track of) what it is I might want to do later compared to just using a notepad.

1 Like

This honestly seems like a great update

2 Likes

Is this the AnnotationService?

a ton of super cool updates at once it looks like, good on you Roblox.

4 Likes

Not to be rude, but this… doesn’t seem efficient. In fact, it seems less convenient than Team Chat was, even with all the tagging.

I’ll stick to my goat TextLabel or a studio Team Chat plugin for now.

3 Likes

Oh, cool! Looks like something I’d use in the future.

Are you able to make comments on UI elements? I think this could also be very useful for when working with UI.

1 Like

This is really neat and I have been using a plugin to do something similar for a while. It’s a shame that it’s for team create only.

Seconding this – even though I do use team create (I like the drafts feature for staging script changes), I regularly make backup place files and reference older versions, and sometimes I publish the place file to a new experience. In both these cases I’d like comments to remain.

I don’t like it when stuff is prone to disappearing. Another annoying example of this is script commit history being accessible only in team create and not in local place files or places to published to a new experience. Kinda defeats the purpose, means I can’t rely on script history being there. So if I actually want guaranteed script history I have to use local backups (which is at a lower granularity than commits unfortunately).

2 Likes

We only support comments on BaseParts (including Terrain) at the moment, so UI isn’t covered in this release.
We have lots more planned for this feature though, so we can definitely look into supporting this if creators would find it helpful.

Obvious disclaimer that I speak for myself and not any company.

We have around a dozen engineers working on the game at any given time. Some of them are working on bug fixes, some of them are working on weekly releases, and some of them are working on neither or both at the same time. All of this work is split into different branches, which should hopefully be a familiar workflow. We also have all of our models on the disk as .rbxm files so that we can build them into a .rbxl and upload it as part of a CI/CD process. This lends itself well to having a workflow that is essentially “build the place file and then open it in Studio to start working on it” since we have that capability already. The only real complication is getting .rbxm files back out onto the disk to be checked back into git, which we have a tool for.

While we could just add “upload it to a remote place and open that place” to the workflow, it’d be really inconvenient. We’d need to track what branch owned what remote place, so that switching branches didn’t ruin things. We could always just make a new place on Roblox every time it was deployed but I’ll be honest: that sounds awful. We’d want to reuse them when we could.

While we could solve these problems and start using Team Create, we don’t want to because it wouldn’t improve our productivity at all. We use Git for version control and to merge changes from different engineers, and we have Slack for communicating with one another. For getting code and assets that other people made into the game, we have a workflow built using Rojo and Lune (I can elaborate on this if you’d like). Unless I am missing a killer feature of Team Create, all that using it would provide for us is the ability to collaborate while writing code, which is something that VSCode LiveShare offers already.

Even if we were using Team Create I’d have concerns: Comments are presumably stored per-place. If a branch were deployed to a place that had already been used, it might have comments in it that were now out of sync with the DataModel, which would get weird. It’d also be weird if I copied someone’s branch and comments weren’t carried with, since it’d mean that artists couldn’t leave comments and then pass it off to engineers (or vice versa) because they’d be lost.

Let me know if you have questions, because I’ve glossed over a lot here in favor of not leaving a total wall of text.

16 Likes

Can I ask why this is released in a gradual rollout over a studio beta?

The ever powerful TextLabel Instance parented to StarterGui: :sunglasses:

4 Likes

Sorry to hear that, I’ve reached out in DMs to see if we can resolve this for you :thinking:

EDIT: We’ve fixed the issue :tada:
For anyone else who runs into trouble adding comments, please try updating to the latest version of Roblox Studio (671) and restarting your TC session (by having all collaborators leave, then rejoin).

3 Likes