Share a behavior through a ModuleScript

local Labels = {}
function Labels.describe(name) return "Workshop: " .. name end
return Labels

The returned table is the interface. A caller explicitly invokes Labels.describe.

New syntax: modules, require

• cooldowns
• cleanup
• prompt-validation

ModuleScript exports apply.

local LampStyle = {}
function LampStyle.apply(part)
    assert(part:IsA("BasePart"), "LampStyle requires a BasePart")
    part.Anchored = true
    part.Color = Color3.fromRGB(234,120,40)
    print("Styled", part.Name)
end
return LampStyle

Server controller calls the interface for two props.

local LampStyle = require(script.Parent.LampStyle)
local Workspace = game:GetService("Workspace")
LampStyle.apply(Workspace:WaitForChild("LampA"))
LampStyle.apply(Workspace:WaitForChild("LampB"))

require expects a ModuleScript Instance, not an ordinary Script.

Circular module dependencies can stall loading; keep this interface independent.

This is a bounded learning lab. It has not been executed in an approved Roblox Studio environment by this website.

A checked checklist records your own review, not automated project competence or a community verification.

A ModuleScript returns a value, commonly a table of functions. require loads that value in the caller’s environment. Loading a module does not automatically call every exported function.

Keep the module in ServerScriptService when only the server needs it. A module placed in ReplicatedStorage can be read by clients, so it must not contain secrets.

Within one Luau environment, repeated require calls reuse the returned module value. That makes shared module state a deliberate design choice; this module keeps its work in the supplied object instead.