All Roblox Studio Services within a module. Good or Bad Idea?

Help and Feedback Creations Feedback
, , ,
#1

Context:

Around a Year ago I made a Module Script that Contained (almost) all of the services in roblox studio.

Use:

The way it worked was you would Insert the Module into the workspace and then in any other Script or Local Script you would wright this:

local Services = require(workspace.Services)

and then after you could use any of the services within the script (except for “NetworkClient” and “NetworkServer”) to do what you need to within any script by typing afterwards:

Services.Teams --For Example

Even though some of the services are Outdated and Unusable such as “AdService”, you still have the ability to use any of the current working services from any script.

My Question to Developers:

Even though you could manually write:

local [SERVICE_NAME] = game:GetService("[SERVICE_NAME]")

I am wondering if anyone would find this Module helpful or unnecessary to use.

Do you find this Module helpful? (as a programmer)
  • Yes
  • No
  • It heavily depends on what I’m coding

0 voters

If there are any ways to improve it, then you can let me know. I personally haven’t used it that much since I almost forgot about its existence :skull:

#2

I voted no. My reason isn’t because of the quality or content of the module, but because of my experience with other languages. Generally, when writing clean and efficient code that compiles well, you don’t want to include anything you don’t need. If I only need workspace and lighting, I don’t want a reference for players, server storage, etc. In practice it won’t make much difference on Roblox but it’s a habit I maintain. You do whatever you prefer. I can see the benefit of this module but it’s not for me.

3 Likes
#3

Sorry but I don’t see it of any help. Doing Services.Teams can be done with game:GetService("Teams") so your module just imports useless services that won’t be used.