Should I be turning these into single modules?
#is what i'm doing with my modules stupid?
ornate sky
This too
all of these do stuff with the camera
tilt camera adds Z roll to the camera which is dependant on a camera part welded to the players head
the rest is pretty self explanatory i'd say
bitter marlin
There is technically no right or wrong way to organize so I cannot say yes or no
dusty grove
There is technically no right or wrong way to organize so I cannot say yes or no
is there any best practices?
bitter marlin
I would check out videos on ways you can organize your Roblox game
There is also stuff like this which is just organization when inside a script https://roblox.github.io/lua-style-guide/
flint cobalt
is there any best practices?
no
its upto u if u like single script architecture or if u like ooping or not opping u choose
oops
rocky marten
Should I be turning these into single modules?
no
there's nothing wrong tho plus it help your brain remember script code location
maybe
unreal sequoia
is there any best practices?
No
Depends on exactly what you’re making but in general no
ornate sky
Alrighty, huge thanks to all of you :))
vivid magnet
Should I be turning these into single modules?
Yes and no.
The positive is that you can use it for other projects and that it separates code for their intended purposes. Allowing for easy bugfixes.
The downside is issues relying with looped require in 2 modules, or in case you need a variable from a parent module without being able to send it over without requiring. But most of the time doing stuff like that shouldnt cause you to find this issue.
Ultimately its fine to do either or as long as its readable to the people who work on the project. If its just you, go ham.
ornate sky
Will keep in mind