Script Optimizations

[Yarik_superpro (The_GrandOptimizer)]

Just learn bytecode LOL
See in dissasembler what code gets compiled into

Luau Bytecode EXPLAINED - How to Read, Debug, and Optimize Like a Hacker

Understanding Bytecode - The Hidden Language of Luau Hello to all developers brave (or crazy ) enough to look behind the curtain and learn how Luau actually works [image] Is it worth learning Bytecode? Reasons to learn Bytecode Why Most Optimizations Fail The main reason optimizations flop is simple: most devs don’t actually know what Luau is doing under the hood. Luau (Roblox’s language) is made up of four key parts: . Bytecode - The low-l…

[2112Jay]

Them spaced lines would mess me up too. Try to keep the all related chucks within a screens view as best you can.

[haydengamingdo (Screwed)]

I mean like how would you organize the folders and modules and rigs and stuff?

[TimeFrenzied (xand)]

@haydengamingdo

HOW DO I ORGANIZE MODULES AND SCRIPTS EFFECTIVELY??

i like to have a utility folder in both replicatedstorage and serverscriptservice for client/server only scripts

It’s optional, but you can also have a folder for data modules exclusively, but if the data module is only used in a specific script (e.g. a datastore template) just parent it under the script in question

@haydengamingdo

how would you organize the folders and modules and rigs and stuff?

for assets, an asset folder in both ReplicatedStorage and ServerStorage, since the client will not need to access every asset

then you can have subfolders for models, characters and stuff, pretty much preference

P.S. For code snippets, paste them into in a temporary script and auto format them or something, 99% chance you’ll be ignored if you send a code block and it has a ton of spaces at the start

about the code, your spacing is wildly inconsistent, and even if it is for readability i dont see the point of spacing ends, that just makes it harder to read

from my understanding, a lot of things happen only if touch is enabled, so you’re better off
A. using a combined if statement
B. changing the TouchEnabled check to the outermost condition (this may not be ideal if touch somehow gets disabled)

this probably doesn’t matter but i’d change button text and things before making it visible

if abilityFound:FindFirstChild("Charge") then
	button.Charge.Visible = true
else
	button.Charge.Visible = false
end

you can improve a lot of your code that looks like this

button.Charge.Visible = abilityFound:FindFirstChild("Charge")

it’s hard to get into, but try to think of conditions more as booleans and you’ll cut down on unnecessary if-statements

[2112Jay]

I like to use a top-down approach. Define everything I can up top, helper functions next, work functions after that, and then the main loop. Always the same.. always know where to look for problems.

[haydengamingdo (Screwed)]

May I have an image on an example hierarchy for folders?

Another thing, this snippet of code I made roughly months ago so I decided to try to optimize it now.

[ChiDj123 (xHeptc)]

I suggest you not to even try, whatever he coded there is a complete abomination and horrible piece of code, that’s all from me, thank you

[1kaelen1 (IMoggedOOP)]

Hater

[Niklantis05 (Nik)]

Very good organization This just proves that you are a good scripter.

[ChiDj123 (xHeptc)]

1. Loops
   It is really important to not use pairs AT all now, and ipairs when not needed, they are both old, you should switch to either generalized iterator, or next variant.

for Key, Value in myTable do --// Gen iteration
for Key, Value in next, myTable --// next variant, also faster than Gen iteration

2. Less polling and depend on Event Driven structure as much as you can

RunService.Heartbeat:Connect(function()
   if player.Health <= 0 then
      killPlayer(player)
   end
end)

--// Above is a bad, useless polling, consider switching to Events like .HealthChanged
--// so your code only runs when something changes

3. Memory Management and Object Pooling
   In a horror game, you might be spawning effects, blood, or projectiles. Creating (Instance.new) and destroying (:Destroy()) parts repeatedly causes lag spikes.

• The Solution: Object Pooling. Create 50 blood parts at the start of the game and hide them. When needed, move them to the correct position. When done, hide them again. Do not destroy them.

Now, since Yarik is not here, I will be the first one to mention that you can switch to ECS, since I assume you will have monsters, and other entities, but of course, your game might not require ECS at all, but you can begin switching to ECS once your OOP is starting to get messy

Also understand, that thousands of lines does NOT mean a bad game, a big game can easily have thousands of lines, tens of modules.

[1kaelen1 (IMoggedOOP)]

fact check this @yarik_superpro

[ChiDj123 (xHeptc)]

Yarik is my student, he does NOT fact check me buddy
It’s even crazy that you need someone else to fact check the basics of game optimization, wild.

[1kaelen1 (IMoggedOOP)]

@ChiDj123

It’s even crazy that you need someone else to fact check the basics of game optimization, wild.

im too lazy to check the bytecode ngl

[BonesIsUseless (Bones)]

@ChiDj123

Loops
It is really important to not use pairs AT all now, and ipairs when not needed, they are both old, you should switch to either generalized iterator, or next variant.

i’m glad someone mentioned this

[ChiDj123 (xHeptc)]

??? all 3 methods I’ve summarized are common sense, how are you going to benchmark object pooling by direct bytecode, bytecode does not have Instance.new nor :Destroy(), even if you were to replicate the class, you cant replicate what the engine does when these functions get called. The only way to benchmark this is within studio.

[TimeFrenzied (xand)]

I’d probably set it up something like this:

Summary

Workspace

• Map (Folder) (very important if you don’t have multiple maps and instead have a world map, this will contain folders for sub areas such as islands)

ReplicatedStorage

• Assets (Folder)
  • VFX (Only client really needs access)
• Utility (Folder)
• Data (Folder)
  • CharacterInfo (Data ModuleScript)

ServerScriptService

• Scripts (Folder)
  • Data (Script)
    • Template (Data ModuleScript)
• Utility (Folder)

ServerStorage

• Assets (Folder)
  • Models (a majority of models will be accessed from the server)
  • Maps (Round-based game)

Template is a theoretical data module that only the data script would need access to. Ideally, you should just put it in the script itself, but it’s mainly preference.

[Yarik_superpro (The_GrandOptimizer)]

The next variant being “faster” is one of those myths that has survived purely through word-of-mouth and cargo-cult programming. At optimization level 2, pairs literally compiles down into the same sequence. You’re not gaining cycles - you’re gaining placebo.

Generalized iteration is the only pathway endorsed by the Ministry of Performance.
Everything else is legacy coping mechanisms.

As for the ECS part:

@ChiDj123

Now, since Yarik is not here, I will be the first one to mention that you can switch to ECS, since I assume you will have monsters, and other entities, but of course, your game might not require ECS at all, but you can begin switching to ECS once your OOP is starting to get messy

The New Luau Order has reviewed your statement and determined that encouraging ECS “just because OOP might get messy someday” is a Level-4 Abstraction Hazard.
ECS is a tool, not a prophecy. Use it when needed - not as a ritual.

This reply has been officially approved by the Command Council.

[ChiDj123 (xHeptc)]

i was wondering why it took you long to reply you were spending hours on that logo

[TimeFrenzied (xand)]

what the heck am i reading right now

[Yarik_superpro (The_GrandOptimizer)]

You are witnessing the next evolutionary stage of Luau development.
To proceed, please surrender all unnecessary abstractions and report to your nearest Optimization Center for cognitive recalibration.
This is completely normal.