Quick-Parent bugs fixed:
Presets going off-list
Presets not saving sometimes
Make sure to update quick-parent to get these updates!
Quick-Parent bugs fixed:
Presets going off-list
Presets not saving sometimes
Make sure to update quick-parent to get these updates!
There’s an issue with the plugin that I just noticed. Every time the plugin reloads it says it cannot find the preset and the preset is removed from the list.
So, there is no preset in the list, and it is saying cannot find the non-existing preset?
If this was the case this issue has been fixed!
The list had a preset before and it appears to save the preset, but it doesn’t appear to correctly save. The preset data does not persist after studio closes or a new file is opened, in which there was an error in the output saying that there was no preset data, but it appears to have saved it.
Okay, just incase I fixed it already can you update the plugin?
The plugin being updated, it does not save the presets, nor does it warn about the preset being nonexistent.
Yes, I currently removed all prompts in output to fix bugs. Currently on a tight schedule going to try to fix them asap.
Hello, does this issue persist when you’re on a published file?
The issue appears to happen only on non-published places or files.
Yes, that is your issue. Just how you can’t use DataStoreService (plugin data or whatever) without a published place file you can’t store plugin data as well.
no offense but this is just useless. You could probably parent lots of objects way easier into another object without this plugin.
There’s actually another way to do this without data stores, which is via Plugin.SetSetting
and Plugin.GetSetting
. More information can be found here:
Plugin | Roblox Creator Documentation
Yes, I actually used those 2 functions.
Thanks for the feedback. I created this plugin because I made a post about me helping other’s make their life on studio easier. This plugin is not meant to absolutely be helpful to everyone since they have their own methods and such.
I feel like this doesn’t have too much of a use, though I appreciate the idea.
Maybe if this function was part of like a pack of a few functions, such as a pack that adds a bunch of new ways to improve the explorer??
Definitely can be helpful to new people I bet! It’s still a smart way and a great way to learn about making plugins!!
It has been a while that I have not updated this plugin so I decided to clean up a few things…
I made the questionable UI design to be more professional and cleaner.
As you can see here:
Comparing this UI to befores UI is a massive upgrade If I do say so myself.
Hopefully this plugin is still helpful to all of you and happy parenting!
(Worst catchphrase ever)
Did you add the SetSetting
instead of relying on data stores yet?
Yes, I always have been using this function to save plugin data.