Where's the best spot to keep ModuleScripts?

Here are your three primary containers for ModuleScripts:

1. ServerScriptService
   • Place module scripts here whenever they are only used by the Server.
2. StarterPlayerScripts
   • Place module scripts here whenever they are only used by the Client.
3. ReplicatedStorage
   • Place module scripts here whenever they are used by the Server and the Client.

Note:

• ModuleScripts are extensions of either Scripts or LocalScripts. Whichever type of script requires it, that is the environment it will run in.

• Objects in ReplicatedStorage are cloned to both the Server and the Client.

To answer your question, you should place ModuleScripts in a container that gives them access to only the environment they need to run in.

Most of your Modules should be going in ServerScriptService or StarterPlayerScripts, as they are specific to the Server or Client environments, respectfully. However, utility libraries can be used by both, and should be placed in ReplicatedStorage so each have a copy.

The reason you don't "throw everything into ReplicatedStorage because that is easier", is because one of the biggest reasons you use ModuleScripts, is for organization. Also, you risk compromising Server code by sharing it with the Client.

Past the initial containers, you may be asking:

• What about Folders? Do I make a Folder for all my ModuleScripts?
• Nested Folders?
• Should I just place the ModuleScripts under the Script or LocalScript that uses it the most?

This all depends on the scale of your project, how many scripts are requiring your ModuleScripts, and what else is located in your selected storage container.

In ReplicatedStorage, if you are using it, good chance you have more than ModuleScripts within it. You should make a Folder labeled "UtilityModules" or something similar, and from there you can have as many nested categorical Folders within to further organize if you are so inclined.

In ServerScriptService or StarterPlayerScripts:

• Is the ModuleScripts being required or does it have the potential to be required by more than one script?

  • Consider the option of placing it within a Folder for organization, similar to the ReplicatedStorage example. Otherwise, you will find yourself referencing crazy paths just to use a ModuleScripts embedded inside another object.

• Is the ModuleScripts being required by just one script?

  • Make it a direct child of the script which is requiring it. If one object has multiple ModuleScripts embedded under it, but also other objects, you should consider making an embedded Folder.

Finally, what about embedded ModuleScripts? Most likely you have done this or thought about it. A chain of ModuleScripts which require each other and are all nested within the children of each other.

This is something you should do if you are experienced with ModuleScripts and have a specific hierarchy structure that works for you.

You can place the ModuleScripts wherever you want, however what I've posted in this thread is my recommendation for anyone wanting to make the most out of using ModuleScripts.