Introducing Package Version Notes

[Master3395]

Having them in-game would help with making changelog in a better way, instead of content creators having to make their in-game text labels or similar for their changelog.
This way, we can load the changelog for older versions in-game, in a bigger way, using api.

[itsFrank17]

You can make your own

Introducing in-experience Mesh & Image APIs [Studio Beta]

TL;DR EditableMesh and EditableImage are now available in Studio-beta and give you direct Luau access to Mesh and Image data at runtime. Important Caveats: Publishing edited Meshes / Images from within your experience is not available in this beta but is coming soon. Real-time replication, moderation, and collaborative editing support for meshes / images is not available in this beta but is on the roadmap. During the Studio beta, you can load & edit any Mesh or Image asset using t…

[777PerfectPlayer777 (NightPlayer)]

It’s not mesh editor. Mesh editor is when you can edit meshpart by moving every dot in studio not in the game. Like in blender for example.

[itsFrank17]

Yes I understood your question, the new editable mesh API makes it possible for anyone to write their own studio plugin that can do exactly that. It is available both in-experience and in Studio plugins.

While Roblox currently has no plans to build such a mesh editor, it is now possible for anyone to build one as a Studio plugin thanks to this API

[0Tenth (Lychee)]

MeshCreator - Edit meshes easily with free plugin

[Mesh Creator500x500, 50%] Plugin link: MeshCreator About Mesh Creator is a plugin that allows you to modify MeshParts using Editable Mesh, a new feature added to Roblox. About Editable Mesh: Introducing in-experience Mesh & Image APIs [Studio Beta] Caution Please turn on EditableImage and EditableMesh in the beta features. How to use You must have the “EditableImage and EditableMesh” beta feature enabled Click on the Mesh Creator plugin button and select the desire…

This might help you!

[777PerfectPlayer777 (NightPlayer)]

Then for what Roblox made this API mesh if they not give any interface to work with it? Where is the logic? Now random user create plugin but Roblox workers with soruce code cannot make it, even if it would be much easier?

[vrs2210]

This is a genuine godsent, now we’re just missing place history version notes.

[Hayden_Almeida]

That would be awesome!! This would improve a lot the “change log” control of our games.

[ForeverHD (Ben)]

+2 to all the posts about comments on publishing and open cloud, but overall a really welcome change and it’s awesome to see all the love going into packages.

Packages are currently locked to team environments. Are we likely to see distributable packages on the Creator Store available soon?

I’d love to start moving over my projects to packages as they’ll make it that much easier for our users to view and install updates.

[Fluffmiceter]

I have a problem with Packages:

PackageLink.Status is not scriptable (cannot be read). This is a problem for me, because I have built a plugin revolving around managing Packages, and being able to detect which packages are out of date or have changes is very important for a lot of my plugin’s functionality.

I see no reason why a plugin-level security should not be able to read this value.

Also: it would be very nice if more aspects of Packages could become plugin-friendly. Things like being able to set the AutoUpdate property, request the latest version for a selected package, or even publish new changes to a package automatically, would open up lots of potential for Package-based workflows and automation. If security is a concern, you could always require the user to grant the plugin permission to modify Packages, similar to how plugins need permission to access Http requests or modify scripts.

[Riesegarder]

@SoCalifornian

I really don’t like this workflow. It should mirror the way commit comments are done.

The first use action for adding notes to package versions should be upon publish (with a potential option for seeing this every time or hiding this prompt forever).

The same for updating packages manually, we should see a history of all the updates that have happened since the last update alongside their comments.

I have to second this. I use packages a lot – mostly for my own modules and frameworks, so I usually just put dated comments within scripts to indicate what’s changed. For the first time, I found myself making a package for a model, so I remembered this feature was a thing and I could add comments like commit comments.

Please make it mirror commit comments. It’s so unintuitive having to add the comments afterwards, then not being able to see what’s changed recently for the package kinda just confuses me.