I’m excited to announce the latest update to PathProRenamer you can choose which instance types you don’t want to rename using the brand new checkboxes feature !
What is the use of the checkboxes feature :
Selective Renaming : Now, you have full control over which instance types (e.g., Folders, Parts, MeshParts, UnionOperations, Models) to exclude from renaming. This allows for more precise and efficient workflows.
Ease of Use : Simply check or uncheck the boxes to include/excludes instance types from the renaming process. This is especially helpful when working on large projects with mixed instance types.
Example :
Let’s say you only want to rename UnionOperation instances while leaving others untouched. With the new update it’s as easy as selecting the checkbox for UnionOperation ! Here’s how it looks
Now no more renaming of parts or models, only the instance in which you enabled on the checkbox. Just clean, efficient workflows tailored to your needs !
Feedback
I’m always open to feed back from the community. If you have any ideas or suggestions on how to make PathProRenamer even better, I’d love to hear them ! My goal is to continuously improve the plugin to meet your needs and provide the most value possible.
Thank you for your support, and happy developing everyone !
All functions of this plugin can be achieved with 5 lines of script (1 of command bar)
for Index, Part in ipairs(game:GetService("Selection"):Get()[1]:GetChildren()) do
if Part:IsA("BasePart") then
Part.Name = "DesiredName" .. tostring(Index)
end
end
For above code to work, paste it into command line, select Instance? which childs you want to rename, and press Enter.
While I understand that minimum price of plugin now is 4.99$, there’s also “FREE” price allowed. Such functionality just shouldn’t cost any money.
Also, why you think that people need rename only Folderss, Models, Parts and Unions? I often rename Attachments, GuiElements, Value instances, and many others.
And last: use widgets instead of consuming world viewport space.
Because there could be scenario in which when you are debugging instance you want to check which one are causing problem like collision in Roblox and sometimes you smell that unions are the problem so you then look an eye on it
Also note : if I could put 0.99 $ on the plugin I would definitely do it. It’s just that it’s something that is totally out of my control and Roblox decision so I can’t do anything about it.
MMM interesting and how could that be put if sometimes you have a big project and multiple parts to rename at the same time when modeling ?
Maybe I could find a way to generate logic name if you select a model like a door in the future and the name it generate would be Hinge and Door if for example you have a tycoon with multiple buttons I could find a way to rename the button fast suggestion up to you. I’m trying to understand market proposition and need hence the communication very important.
!
