sorry for bumping this post too, but i think i found a better solution that is perfect and doesnt take alot of code if anybody out there have the same problem.
Sooo, after alot of years as i can see this still wasn’t fixed and maybe it will not, and i have this problem right now, and what i did is that instead of sending tween info i just make tween info when signal is recivied.
instead of sending this
TweenInfo.new(1, Enum.EasingStyle.Sine, Enum.EasingDirection.InOut)
I just do:
{1, Enum.EasingStyle.Sine, Enum.EasingDirection.InOut}
Yeah, i just send an table of same arguments instead of putting it in tween info
why table? cuz getting few or more arguments is just taking alot of time, or maybe not alot but it’s still not organazied (which is what i’m trying right now, make organazied code cuz before i were writing the code and after a week i couldn’t find needed things cuz of amount of unorganized text), so i just put everything in the table so we will need only 1 output variable (and it IS neccessary to put arguments in the table in right order just as you would make tween info).
to recieve signal i just do:
Event.OnClientEvent:Connect(info_table)
local tween_info = TweenInfo.new(table.unpack(info_table))
end)
instead of going through every thing in the table that i would do when i didn’t know this, i just do table.unpack() which literally just unpacks the table with all arguments in right order, which is very helpful.
also this is what would you do if you won’t use table:
Event.OnClientEvent:Connect(tween_time, style, direction, repeat, do_reverse)
local tween_info = TweenInfo.new(tween_time, style, direction, repeat, do_reverse)
end)
Yeah it’s still readable, but still the other way is much easier and organazied, so i recommend using tables in case you didn’t
I hope it will help somebody out there!