Off of a quick glance, what was initially a project to just be a one function, one module script, at least in your v2, has turned into something somewhat more complicated. This is a nice addition and I will link it in the OP but rather than switch my development to adding onto this module, I will probably continue work on the original version. This isn’t to say yours is poorly coded, not at all,
but code that looks like this >
local Function = function()
print("foo")
end
--// Note, function not necessary
local UiTransition= require(game.ReplicatedStorage.UiTransitions)
UiTransition.Transition("CircleGrow", 1, 1, Color3.new(255,255,255), Function)
turns into >
local sg = game:GetService('StarterGui')
local Transitions = sg.Transitions
local tm = require(Transitions)
local goals = {
Position = Vector3.new(100,20,100)
}
local dur = tm.Settings.Default.Duration
local transition = tm.Settings.Default.transition
local waitTime = tm.Settings.Default.waitTime
local color = tm.Settings.Default.color
--local plr = game.Players.LocalPlayer
local plr = 'FondInstinct'
function check(message,number,bool)
print(message,number,bool)
end
local func = {
[1] = {functionExample = check, args = {plr,3,false}}
}
tm.Transition(transition,dur,waitTime,color,nil,func,plr)
Which just isn’t the reason I made this module. This module is made to be a singular function with one optional variable that can be used by literally anyone after reading the documentation.
I really do hate to say that I don’t want to switch my priority to something you quire obviously put a lot of effort into. One thing I will be directly referencing for a newer release of UiTransition is the functions with arguments, provided you are alright with it.
Additionally, we are 2 different people, which means we code differently, which means that it’d be hard for me just to start working on this.