Cool module!
Maybe add the ability to put multiple trails, that players can receive with a gamepass? Or temporarily, with a dev product? And maybe even add effects to the trail, such as causing damage to other players.
Would love to use it if these features were added!
added that into V2 which is soon to come out
I won’t add that as it will be easy to implement that on your own
this sounds like an amazing idea, thanks so much for the suggestions 
I came up with that thinking in the mindset of somebody who knows nothing about scripting, (so myself,) if you could do a tutorial on how to add that when you release the next version?
yea sure, I would love to do that
can u add a link for a demo place?
I’ll add a demo place for V2 when it releases
0 voters
asking this because it would take a bit to implement into the module
Hey there, I just want to say that I really like the concept! I am probably going to use this feature in my game as a walking animation for my ice superhero! Thank you so much for creating this and charing it with the forum!
thanks a lot, sad that I gotta wait till the 4th of July to update it tho 
Why use this over the default Trail instance? This looks like a over-complicated version of something that already exists as a built-in instance
I made this as a way to have a more custom trail
the next version you will be able to use this with more then just the player and there will signals that the current trails don’t have
also note that this uses the trail instance
And? You can already customize trails as your heart pleases, how is this a “way to have a more custom trail”
as of right now the module doesn’t let you change the trail instance’s settings, next version will allow that which means it will let you customize the already existing trails including the customizations my module adds onto it
trust me just wait for the next version, I’ll even have trail types where you can changes how the trail moves and works
V1 is nothing compared to what V2 will have
so in terms of customization this thing will be amazing
besides like I said V2 is also going to include signals or RBXScriptSignals that trail instances don’t even have at all
even V1 is still really customizable
Aand what are those signals going to bring? I see no actual use case for signals in Trails
let me name some rq
Touched, TrailAdded, TrailRemoved, Changed, and many more
like I said I am going to make this very useful
3/4 events that you mentioned already exist so why bother
and you have yet to see what I mean, this is hilarious
you don’t understand why I said those three do you?
let’s start off with Changed, so what is different?
well Changed runs whenever an instance changes, you can’t do that with my module because the trail instance isn’t the only thing changing properties and you can’t access the trail at all unless you know where it is, there are multiple things changing at once.
why TrailAdded over ChildAdded and why TrailRemoved over ChildRemoved, well you can’t easily detect when this stuff happens, like I said less work for the scripter or anyone using this
these signals are here to make you have less code and making everything efficient and clean
I still see no use cases for those specific events, if anything they already exist in the normal Trail instance
I edited my message btw, I explain stuff
the default signals for the instances wouldn’t work well at all
also ChildAdded and ChildRemoved check if a child is added or removed from an instance and that is not the same as what TrailAdded and TrailRemoved do because they run when a trail is added to anything or removed from anything not a specific instance