Require() doesn't require half of the modulescripts

Help and Feedback Scripting Support
,
#1

So I made a script that requires all modulescripts and runs their function.

But for some reason, it doesn’t require all the modulescripts and only requires half of the stuffs in the script.

all modulescripts:
image

code:
image

this is what I get when I print the required modulescripts.
image

#2

Try using ipairs instead of pairs. ipairs is for arrays, pairs is for dictionaries.

#3

Put the require(v)() in its own thread. You are running each module and its ending on one that has a loop or something.

#4

not like it will fix the problem, pairs can also be used on arrays

#5

There could be something yielding the load process, try to wrap the require in a spawn?
Ex:

for i, v in pairs(script:GetChildren()) do
      task.spawn(function()
            require(v)()
      end)
      print(v.Name)
end
#6

It’s probably that the modules haven’t loaded in, so you could add a ChildAdded event then require and print in that.

script.ChildAdded:Connect(function(child)
    require(child)()
    print(child.Name)
end)
#7

The modules are a child of the script. If the script exists, so would the modules. Also im pretty sure require() has a built-in wait so something like this won’t be needed. At least I think ive read that somewhere before.

#8

I don’t get why there is such a fuss.
The module process stops at Teleport, so Time Cycle might have a while loop or some sort of wait that blocks the for loop from minding it’s own business.

The easiest workaround to this is to wrap whatever’s causing the issue in the time cycle script in a different thread, or to just wrap the require in a different thread. (which I just demonstrated)

#9

Couldn’t it be the other way around, since children are based on the parent, but parent isn’t based on the children existing?

@swatj1an But it’s about loading the modules right? So getting the children at a time when not all of the children are there would mean that it wouldn’t load in ones that got loaded in after. But what you said is right, if there is a yielding statement that would stop the execution of the other modules.

#10

So I was in a rush wasn’t thinking straight after putting the while true do loop time cycle thing (that I just copied in the toolbox) into the modulescripts and I tried wrapping it and it works fine now

return function()
	task.spawn(function()
		while true do
			game.Lighting:SetMinutesAfterMidnight(game.Lighting:GetMinutesAfterMidnight()+0.25) 
			wait(.2)
		end
	end)
end
1 Like
#11

Scripts in ServerScriptService don’t “Load in” as they are already there at run-time, because it’s the server, not the client. Stuff loads on the client, which is why you use WaitForChild a lot for client stuff. Server stuff should already instantly have access to things in its Storage locations.

#12

Oh ok, I didn’t know that, thank you.

1 Like