Should I put everything into one Module?

[Hyules (librium)]

To put it simple, I’m wondering if it would be better for me to put everything inside of one module, so things like camera shakes, attacks, everything. Or, should I have separate Modules for different things? I’m asking this for further knowledge on organization.

[Noobruhdude (Waluigi309)]

You should keep everything that are not related to each other in separate modules. Camera shakes, attacks, etc. should be kept separate since they are not associated with each other.

[dthecoolest]

I believe I saw this quote somewhere on the dev forum but I can’t quite remember it but it goes somewhat like this:

If you have to use “and” to explain what your code/script does you might want to rethink about that code.

So yeah if you put everything in one module it kinda defeats the purpose of making code modular. I believe the proper name for this design philosophy is the single responsibility principle which you can see around the dev forum and the post below and what @Noobruhdude has talked about:

In what situations should i use ModuleScripts?

I use ModuleScripts for pretty much everything: [image] Why? ModuleScripts are absolutely brilliant for making your code more clean, modular and easy to use. You can precisely control when your code will run since you have to require() modules to run them. I usually have one or two scripts which require some of the modules, and those modules will, in turn, require all the other modules they need, and so on. This lets you make more guarantees about what your scripts have access to (especiall…

[LyingYouLou]

Remember that when you pass the require() function, the script gets a copy of the required module script. For this reason, you should have several distinct modules, each handling a different mechanic in your game.