A plugin with many small tools for developers to use! Watch the video below for a demonstration of the plugin.
The icons displayed below no longer are the ones displayed in blisstools. I bothered to use icons from auroraSuite version 1.5 or earlier to make them seem less outdated.
Make your own day and night cycle with blisstools! Just input a start time in minutes (e.g. 300 to start at 5am), and input how many seconds you would like a minute to take (e.g. 1 second).
Have you ever wanted to create teleport points in your experience? Now you can with ease. Simply select what parts you would like to teleport to, like this:
Why do people keep making plugins that basically amount to game:GetService('InsertService'):LoadAsset(whatever).Parent = workspace? Half the functionality of this plugin (day/night cycle, shift to sprint) is just pasting free models into your game.
You can publish your day/night cycle and shift to sprint as free models and it’ll be just as usable as the plugin. Any customizable functionality can be offered via Attributes on that script. For example on an experimental wheel of mine, there is this:
The plugin does use attributes for some stuff (e.g. view button in the plugin), but people are likely to just click on something, rather than customising values
The types of people who can’t change attributes aren’t going to download a tiny plugin and click through its interface to insert a free model, they’re going to use the toolbox.
You have 1 tool and 2 models. I would recommend publishing the models as models instead of as a plugin. Either that or stop advertising the models as separate tools and combine all the models into one “common model inserter” tool.
I’m not trying to escalate things. I’m giving you constructive criticism (or attempting to, anyway) on how you can improve the plugin. It doesn’t make sense that you advertise each model as its own tool. Inserting models is only 1 tool, configuration options for the model should probably be customized after insertion.
At no point did I say that the models aren’t useful, just that the act of inserting one shouldn’t make up an entire tool. If you make a tool with many many models, the feature of the tool is that it has tons of models to choose from. But if you have 2 tools and each one only inserts 1 model each, it just feels like you’re trying to inflate the number of tools you offer (even though you only offer a very small number right now).
Yeah… I don’t really see any purpose to this plugin, it just inserts free models into your game, and creates things a person who knows little about scripting can do. The only useful feature is the texture tool. You should observe more about what the community wants, not what you want, this way people will think your object is useful.
I’m not against you, I understand your scripting skills are way beyond that, but it’s tedious to fork as Everytime I wanna add something, I need to edit the code. Just imagine an average developer doing this, he would burn out in minutes.
This is…amazing, firstly: being able to create useful pieces of code in like 2 clicks of a button! Secondly: Easily configureable, and thirdly: the look of it!
• blisstools
• blisstools
