ExtraFuncs - Universal Utility Module for Roblox Developers

[FishyLua (FishLua)]

Overview

ExtraFuncs is a modular, lightweight, and developer-friendly utility library for Roblox that provides dozens of handy helper functions for working with instances, tables, math, colors, CFrames, players, arrays, and more all in one place.

Designed to save time and make your code cleaner.

---

Installation

1. Place the ModuleScript in ReplicatedStorage and name it ExtraFuncs
2. In your scripts: (Local or Server)

local ExtraFuncs = require(game.ReplicatedStorage.ExtraFuncs)

Example Usage

local part = workspace.Part
print(ExtraFuncs.ToPath(part)) -- "Workspace.Part"

local color = ExtraFuncs.HexToColor3("#FF5733")
workspace.Part.Color = color

local newTable = ExtraFuncs.DeepCopy({a = 1, b = {2,3}})

---

Features

Instance Utilities

• ToPath(obj) – Get readable path for an instance
• WaitForPath(path) – Wait for a path to exist
• GetDescendantsOfClass(parent, className)

Table Utilities

• DeepCopy, MergeTables, PrintTable

Math, Tween, Player, Color, Array, String, Time, Random, Vector, CFrame, Signal, and Misc Utilities

(Full list is inside the module’s header comment.)

---

Model

Here

---

Free to use, modify, and redistribute.

Feedback

Suggestions, feedbacks, and contributions are welcome — feel free to fork, expand, or improve it!

[SaleMales]

ExtraFuncs.ToPath = :GetFullName()

[FishyLua (FishLua)]

Pretty much, yeah. it works the same way, but ToPath() is just a friendlier, customizable version.
Roblox’s built-in :GetFullName() is faster, but it’ll error if you call it on nil or a destroyed instance.

My ToPath() checks the type first, warns if it’s not an Instance, and still returns a readable path. So you can safely call it without worrying about runtime errors.

Its meant more for consistency and convenience across scripts

[Hzodx]

holy ai generated module

ToPath - Instance:GetFullName()
Clamp - math.clamp()
Tween - literally tween service
GetPlayerFromCharacter - Players:GetPlayerFromCharacter()
GetCharacter - Player.Character
RGBToColor3 - Color3.fromRGB()
HexToColor3 - Color3.fromHex()
LerpColor - Color3.new():Lerp()
Shuffle - Random.new():Shuffle()
Split - string.split()
LerpCFrame - CFrame.new():Lerp()

the rest i considered atleast somewhat useful
however this topic is horrible, it repurposes already made snippets of code and packs it into one big ai slop module. Not only was no effort put behind it, it doesnt solve anything

[EzraPalo (ezra)]

all these functions seem to be integrated into Roblox already, jows urs different?

[FishyLua (FishLua)]

Yeah, all (or most) of these are basically wrappers around Roblox’s built-in methods. The main point of ExtraFuncs is convenience, and consistency even if it’s technically “reinventing” the wheel

[FishyLua (FishLua)]

For example, GetCharacter(player) automatically waits for CharacterAdded, which raw player.Character doesn’t do
Clamp(num, min, max) is just math.clamp() but keeps all utility functions in one namespace
and like I said ToPath(obj) wraps :GetFullName() but won’t error if obj is nil and adds a clear warning

[Microwave_Toothpaste (spork)]

@FishyLua

but keeps all utility functions in one namespace

Personally, I like my monstrously huge block of imports. It makes the actual logic more readable, given that each thing comes from its own module. Why should I use this over that?

[DrakorAlt_O (guywithalemon)]

OK module, but around 80% of the functions here are pretty redundant (no offense). first, GetCharacter() is just a name around player.Character or player.CharacterAdded:Wait(), the former has no significant benefit and can also introduce ambiguity with its name.

Clamp() one namespace, what? isn’t it good to practice separation of concerns in a codebase? there’s 0 good reason to use it over math.clamp, which is already available globally with no need for a require().

ToPath(), the benefits you stated comes with it, in my opinion, are the opposite. you should error if obj is nil, not warn. since the code that calls the method expects a string, it will be working with incorrect data; which will result in an error anyways, or worse a silent error.

[kolakolaki6663 (ImSoKolako)]

This is useful… for people with no knowledge of programming and algorithmic.

Not only people with at least some experience keep track of data types they’re using (which makes type() and typeof() useless waste of time), but this just… wraps things and ensures things roblox already ensures… (type check in CFrame).

What was the point of this..? I don’t see much use cases or these use cases are already overceeded by Signal:Wait() method.

This is overceeded by HTTPService:GenerateGUID().

Have you known that you can do just ExtraFuncs.Clamp = math.clamp ??? (because your way is peak inefficiency)

If I parse any non-Player instance in GetCharacter function, it’ll error.

Also there’s literally no types written for each function parameters and returning values, this makes code give unknown type value, which is disaster for --!strict

yeah…

and what if a or b is not PVInstance or an Instance that does not have Position property?

Why you ensure type safety in one thing, but forget to ensure it in the other one? This is very strange. The code looks to much of an AI one.

Anyway… Most of these functions are way easier to write in imperative way.. Only few of these functions are might have some of use case.

[Microwave_Toothpaste (spork)]

@kolakolaki6663

which makes type() and typeof() useless waste of time

What about validating input in remote events? Unless I misunderstood you.

@kolakolaki6663

The code looks to much of an AI one.

Especially the x and y or z instead of if x then y else z.

[shroomi_i]

@Microwave_Toothpaste

Especially the x and y or z instead of if x then y else z.

what’s wrong with x and y or z? for me atleast, it’s easier to understand than if x then y else z

[AlreadyPro (Logan)]

Table Utilities

[kolakolaki6663 (ImSoKolako)]

What about validating input in remote events? Unless I misunderstood you.

Sorry for late response! Most programmers know which type each object they send through any type of communication. Validating input in remote events is unneeded for client side (both getting and sending), because you keep track which RemoteEvent sends what and what it gets on client side, while on server side I don’t see any strong case where typeof() or type() would’ve prevented any unneeded behavior. If you could provide any case where type() or typeof() could’ve been used, share it, I’ll be glad to think about this!

[Microwave_Toothpaste (spork)]

The client can send whatever they want to the server. The server has to make sure the client sent correct info!

[kolakolaki6663 (ImSoKolako)]

Hello!

You’re correct only if we’re talking about exploiters. If the vulnerabilities are not exploited, there’s only developer made LocalScripts, which is 100% trustable if made correctly.

And if we tell about exploiters here, every logical operator (>=,<=,==, >,<) use the strict type control. Meaning, mostly your code will output error OR give false (which is mostly what stops thread from running furthermore) if exploiter provided incorrect types (and you have if statements that check the correctness of values without involving type). And because this error will happen in different thread, it won’t cause any disfunction for others.