And yes sorry it's me the annoying noob.
If not how can you tell the ModuleScript where it's been require()d from?
I cant say
local model = script.Parent
Since I use the require(assetId) method
Update, this is what I have tried
print("Initiating")
local env=getfenv(2).script.Parent
print(env)
Errors Below this line
Initiating 16:51:32.074 - Workspace.Part.SurfaceGui.Updates.MainModule:10: bad argument #1 to 'getfenv' (invalid level) 16:51:32.075 - Script 'Workspace.Part.SurfaceGui.Start.MainModule', Line 10 16:51:32.076 - Stack End 16:51:32.077 - Requested module experienced an error while loading 16:51:32.078 - Script 'Workspace.Part.SurfaceGui.Start.Script', Line 1 16:51:32.079 - Stack End
8 comments
You can try passing the script to the module as a variable.
I've seen EISS having this feature. I'm not trying to make any form of admin script if you wonder.
My suggestion has nothing to do with admin scripts.
Yeah im not trying to make one, well thanks for the tip ill try it.
Ok it doesn't really work since I will use that ModuleScript at multiple locations.... And therefore I want the correct settings to be loaded. Any other ideas? Meanwhile im waiting for answers(not like panicing take your time) ill try to see how eiss does it.
Actually nvm it will work, ill just have one settings script.
Holy inactivity, Batman. Use it in a function, not in the module body.
I know, how to use it require(assetId)(script.Parent.Settings)