Found an issue: can not have multiple Tweens created on a single Instance at a time
Use case: in a case where one might want to save multiple Tweens instead of creating new ones every time upon usage
Code
local part = script.Part; part.Parent = workspace
local TweenS = require(script.BoatTween)
local tween1 = TweenS:Create(part,{
Goal = {
Position = Vector3.new(0,10,0)
}
})
local tween2 = TweenS:Create(part,{
Goal = {
Position = Vector3.new(0,0,0)
}
})
local DB;
part.ClickDetector.MouseClick:Connect(function()
if not DB then
DB = true
tween1:Play()
wait(2)
tween2:Play()
wait(1)
DB = false
end
end)
A little more than that actually. To be more specific, it’s a CIELUV lerp, which is much more accurate and better than the RGB lerp that Color3::Lerp uses.
What exactly are you trying to do here? Why are you trying to destroy the object that you are tweeting after completing it? Plus, since :Destroy passes self as the first parameter (hence the “:”), you would need to pass that as the first parameter. So if you wanted to destroy the instance you are tweening (assuming it is an instance) after it is done, here is what it would look like:
Tween.Completed:Connect(function()
Tween:Destroy()
— or Instance:Destroy() if you have the instance readily available.
end)
There’s no need to go in all caps (i.e. yelling) at someone over code. We’re all hear to learn.
@p49p0 is correct about trying to destroy the Tween after use. From what I understand, they aren’t trying to stop the Tween after completion, they are trying to destroy it. So there’s a disconnect between what you both are talking about. Try and address that, clarify whatever isn’t being understood, and ensure they get what’s going on (if you’re confident that you have the better method) versus yelling.
Please stop picking fights. We can all see that WarriorAnt was replying to deleted posts of yours (if you click the arrow nothing will pop up because they are deleted posts)
Moreover, you’re sidetracking the thread. This is supposed to be a thread about the BoatTween module, and at this point you’re deviating it by picking fights.
This may be a bug or it may be a error on my end, but I have noticed when you try to tween a frame using negative coordinates on the Y axis instead of tweening it, it’s position is just set to the requested position not tweened.
Edit:
The tween works when you request it to come down but not back up.
Found a bug when trying to use BoatTween to make UI changes.
Basically BoatTween gets weird when trying to tween the TextTransparency of a TextLabel (to create a fading effect). Not sure if this occurs with other instances, but this definitely seems like unintended behavior.
Here’s a test place to run the code (one version with BoatTween and the other with regular TweenService) which should illustrate the issue!
It has been a long while since this project was created, sorry for reviving. I understand this project isn’t being maintained actively, but is this module still better to use in place of TweenService? Also, do you know where I could find graphs or some other visual representation of how your additional easing styles look?