Preset Manager Plugin - Bulk apply properties, attributes, tags, and collisions

[boatbomber (Zack_Ovits)]

I was reading @PeZsmistic’s feature request for a Preset Manager to be added to Studio, and I decided to make that into a plugin while we wait for that feature to (maybe?) get made.

Preset Manager for organizing and bulk-applying Properties, Attributes, Tags, and CollisionGroups to instances

As a Roblox developer, it is currently too hard to keep track of all of the tags, attributes, collision groups, and commonly used property-sets in my game, as well as all of the ways these things can be combined and how code can expect them to be combined. A Preset Manager would be a window that allows developers to organize all of these things, even presets with only single things changed (e.g. tags like the tag editor, or attributes), and would satisfy a great deal of use-cases all at once, i…

This plugin ended up being a bit over 2,800 lines of code, and took me quite a while to make. It was a really fun challenge!

Special thanks to @Elttob for letting me use the wonderful Vanilla icons for this plugin!
Special thanks to @Maximum_ADHD for his wonderful API Dump!
Special thanks to @1waffle1 for their LZW text compression I used to store the serialized Presets more efficiently!

Get it here!

---

What is this plugin’s purpose?

Honestly, I don’t think I can explain it better than PeZsmistic did in the feature request, so I’ll quote that here.

@PeZsmistic

As a Roblox developer, it is currently too hard to keep track of all of the tags, attributes, collision groups, and commonly used property-sets in my game, as well as all of the ways these things can be combined and how code can expect them to be combined.

A Preset Manager would be a window that allows developers to organize all of these things, even presets with only single things changed (e.g. tags like the tag editor, or attributes), and would satisfy a great deal of use-cases all at once, including the use-cases satisfied by the tag editor.

Some example use cases, explained by PeZsmistic in their request:

@PeZsmistic

For example, a common use-case for tags is to tag many similar instances in your game, and then have some manager script register these tagged instances to apply some effect to them (e.g. applying an animation, making them hazardous like lava, defining possible interaction). It’s difficult to remember what the names of these tags are without using some third-party plugin to organize them.

With the recent release of attributes also, now it’s possible to have the code managing tagged instances also expect a specific arrangement of attributes on instances with that tag. For example, models tagged “Breakable” could expect attributes that define how much damage it takes, whether or not it’s flammable, etc. I would have to manually remember to add all of these attributes for every breakable model I create, or have to hunt existing ones down in my game hierarchy to clone them, or else my code will break.

Additionally, perhaps I have a 3D skybox made of parts with a specific collision group and certain properties, such as CastShadow disabled. To work on this skybox, I would need to remember to set the collision group and disable CastShadow, or gameplay mistakes could happen or I could hurt performance. If I haven’t touched this skybox for a long time and decide I need to use a new instance type (e.g. ball, meshpart), I will likely forget to do this.

Finally, while working with UI, I often need to apply a common set of properties (e.g. background transparency, text color) to UI elements while getting design and layout sorted out. It’s difficult for me to remember the precise background color I used for the majority of my UI, or the consistent font sizes I’ve chosen to use in my game, and it’s annoying to have to click between instances all the time to copy and paste properties one at a time. Further, if I’ve designed a UI system that uses tagged instances to create or style components, I need to remember the tag names to be able to use that system.

---

What can it do?

Well, for this initial MVP release I did the majority of what PeZ requested:

• The ability to create “Presets”. (A Preset is a collection of properties, attributes, tags, and a collision group)
• The ability to apply Presets to instances in the selection.
  • Presets can be applied to any instance type. Property names that are not valid are simply ignored.
  • These presets could be applied additively or as a complete overwrite to an instance.
  • If I “add” a preset to an instance, only properties defined in the preset will be changed, missing tags and attributes will be added, and the collision group will be changed
  • If I “set” a preset on an instance, all properties will be reset to default, all tags and attributes will be deleted, and the Preset will then be added as above.
• The ability to name Presets.
• The ability to quickly find a preset by searching by name.
• The ability to duplicate Presets for quicker variant creation.
• Autofill suggestions for Properties and Collision Group.
• Automatic datatypes for Properties from API Dump.
• Settable datatypes for Attributes.
• The presets are serialized and saved, so your Presets do persist between sessions.
• Preset summary when the GUI is collapsed.
• Export Preset as standalone module for runtime preset application.
• Select all Instances that match the Preset.

(More features are planned, just not needed for this initial release.)

Here’s a quick demonstration of some of the features in use.

Preset Manager Demonstration

---

Roadmap

• Folders and Sorting
• Recently Used Tab
• Create Preset from Selection
• Supporting more property types (eg: CFrame, Axes, PhysicalProperties, Instance)

---

Get it here!

[CJ_Nelson01 (CJ_Nelson)]

I mean…

This is epic. Its the enhanced, faster properties window of the future. This one I’m definitely installing. Thank you for creating this!

[PeZsmistic]

This is super cool and the properties suggestions are on point. Thanks for doing this!

[RuizuKun_Dev (Kitsune)]

@boatbomber this is genuinely awesome, great work!

I have a suggestion, could you possibly make an option to export a preset as a modulescript?

Use case:

• Lightning presets
• Particle Effects presets
  etc

using Presets at run time

[boatbomber (Zack_Ovits)]

What would you expect this export to be?
I’m thinking something like this, but I want to make sure it’s what you meant.

local Preset = require(Path.To.Exported.Module)

Preset:Add(Object) -- Adds that preset to the given object

[RuizuKun_Dev (Kitsune)]

I think that would work great or something like this could work too

— Exported Preset Module
return function(Instance)
— set preset
end

— Preset Manager (this is something devs would write on their own)
function ApplyPreset(presetName, Instance)

end

[boatbomber (Zack_Ovits)]

That doesn’t work, because presets can have two functions- Add and Set, so returning a single function isn’t enough.

[RuizuKun_Dev (Kitsune)]

Ohhhh, I see then what you suggested before would work great!

either that or we create our own preset setter / adder function but the exported module would contain Preset information so developers can fully customize the behavior they want.

---

@boatbomber forgot to mention.

Does this plugin have the ability to extract Properties / Tags / etc as Presets from exiting Instances?
(I read through the OP quickly but didn’t seem to find anything on that)

[boatbomber (Zack_Ovits)]

Not yet, no. That’s definitely something I’d like to add in the future. I’ll add my roadmap to OP shortly.
Edit: Added roadmap

[boatbomber (Zack_Ovits)]

Update: Preset Export

Suggested by @RuizuKun_Dev

There is now a new Preset action button: Export.
This button creates a ModuleScript that can be used to Add/Set the Preset at runtime, in-game!

You require the module, and then you can use :Add(Instance) or :Set(Instance) just like the plugin’s primary buttons.

local Preset = require(script.Preset) -- Require the exported module
Preset:Add(workspace.Part) -- Apply the preset to a part

Note that this module will not update if you alter your Preset- you’ll need to export the new version.

[boatbomber (Zack_Ovits)]

Update: Select Objects

Suggested by @PeZsmistic in the original request as a “nice to have”

Another new Preset action button! This selection button will automatically select all Instances in the workspace that match the Preset exactly- object must have all the properties, attributes, tags, and (if a basepart) collision group.

It’s pretty expensive to check against every object in the workspace, so use this sparingly.

[ElementedHero]

Needed something just like this. Really amazing plugin. Cuts down time and annoyance with common attributes that are used. Highly recommended.

[AstroCode (Ella)]

Would you consider allowing setting/adding for services? My use case is I want to modify Lighting settings so I can jot them down in a script and then reset them when I am done.

[PolyAxt]

Can presets be tweened? That would be extremely useful.

[fhiwora (Erica)]

Been having an issue where every time I apply a preset, it sets the part’s position to the Origin, even though there is not Position property set for the part.

[boatbomber (Zack_Ovits)]

Use add, not set. That’s the documented behavior.
Set makes all non preset properties into the default, setting only the preset.

@boatbomber

• If I “add” a preset to an instance, only properties defined in the preset will be changed, missing tags and attributes will be added, and the collision group will be changed
• If I “set” a preset on an instance, all properties will be reset to default, all tags and attributes will be deleted, and the Preset will then be added as above.

[fhiwora (Erica)]

That’s completely my bad, for some reason I was mistaking the “Add” button as for creating a new preset;
much appreciated.

[Clueless_Dev]

I was literally about to create my own tool for this; thanks God I saw this post, gonna try it out. Thanks for the contribution mate