Is there a way to make a local function fires when another local functions is called?

[danthemanroblox192]

So I have 2 functions, the 1st function has no wait in it, and the 2nd function has a wait in it. The reason I don’t want to call the 2nd function after the 1st function ran is because the wait will also be transferred to the first function
3. What solutions have you tried so far? Did you look for solutions on the Developer Hub?
I tried while true do, but it no work since I can’t call the 2nd function

local function npcMaker()
	local npcChooser = npcs[math.random(1, #npcs)]
	local npc = npcChooser:Clone()
	npc.HumanoidRootPart.CFrame = spawner.CFrame
	npc.Parent = workspace.NPCs
	local humanoid = npc.Humanoid
	--Where NPC move to before reaching the line
	humanoid:MoveTo(workspace.ConnerPath.Position)
	humanoid.MoveToFinished:Wait()  -- The reason why the wait is needed
	humanoid:MoveTo(workspace.DoorPath.Position)
	humanoid.MoveToFinished:Wait()
	if #PizzaLineNpcs == 0 then
		humanoid:MoveTo(PizzaLine.Position)
	else
		humanoid:MoveTo(PizzaLineNpcs[#PizzaLineNpcs].HumanoidRootPart.Position + DistanceBetweenNPC)
	end
	table.insert(PizzaLineNpcs, npc)
end

local function npcToRegister(path)
	-- Make NPC move to a Cashier
        npcMaker()   -- I don't want to call this here, because it will wait and there are multiple registers
end

[ArtFoundation]

Spawn the function. coroutine.wrap works well for this.

coroutine.wrap( your function )() -- the () is to call it

Thus you could do:

coroutine.wrap(npcMaker)()

as a replacement to npcMaker() where your function npcToRegister is.

[serverIess]

Sounds like you’re wanting to call a function without it yielding for the function to complete. To do this you want to run this on a separate thread. You can do this with spawn or coroutines.

However, do consider the following, as issues can apply to both spawn (which can yield) and coroutines:

@Crazyman32

Error handing with coroutines is a huge pain. I highly recommend using spawn or delay to avoid having to deal with this. Alternatively, use @Quenty’s fastSpawn , which allows spawning immediately, without the delay @Wingz_P mentioned.

The reason for spawn delaying is that it’s queuing up the function to run the next step in the task scheduler (which is essentially 1 frame). Using Quenty’s fastSpawn uses a fun “hack” by using a BindableEvent to execute the new thread immediately and get the correct error handling / stack traces.

fastSpawn is essentially just the following, using your example to execute that function on a separate thread:

local bindable = Instance.new("BindableEvent")
bindable.Event:Connect(function()
	npcMaker()
end)

bindable:Fire()
bindable:Destroy()

[danthemanroblox192]

Thank you, it’s worked perfectly