How can I optimize my entity system?

[dthecoolest]

@Lua_Moose

local CurrentWaypoint = map.Waypoints:FindFirstChild(data.Waypoint) 

My only advice so far is to reduce the number of indexing, and also cache the results of FindFirstChild as it is slower than direct indexing.

@TheNexusAvenger

3. Reduce Indexing Of Tables
A while ago, AxisAngle talked about how he could cast thousands of rays per second with no performance hit, and this is a massive helper for that. There is a more complex explanation about that involving MetaTables, but let’s keep it simple.

for i = 1, 10 do game.Workspace:FindPartOnRay(Ray.new(Vector3.new(0,0,0),Vector3.new(0,i,0)) end 

This may seem simple, but it is a lot more complex once you see all the steps it requies.
For 10 times…

1. Call __index (a MetaTable function) in game to get Workspace, and calling functions like this is fast but can stack if it called a lot to be slow.
2. Call __index in Workspace to get FindPartOnRay. Now to get the Ray.
3. Call __index for the global value new in Ray. Now to get the Vector3s.
4. Call __index for the global value new in Vector3.
5. Create the first vector from the function returned from 3 to create a Vector3 with the coordinates of 0,0,0.
6. Call __index for the global value new in Vector3.
7. Create the second vector from the function returned from 6 to create a Vector3 with the coordinates of 0,i,0.
8. Pass those arguments into the function returned in step 3 with the Vector3s from 5 and 7 to get the Ray
9. Pass those arguments into the function returned in step 8 into FIndPartOnRay

Long list, right? Now to use local values to lower the amount of times everything is indexed.

local Workspace = game.Workspace local FindPartOnRay = Workspace.FindPartOnRay --This is how you index a function without calling it. local Raynew,Vector3new = Ray.new,Vector3.new local Center = Vector3new(0,0,0) for i = 1, 10 do	--For a function indexed by :, you have to pass the table it is part of first before the rest of the arguments. FindPartOnRay(Workspace,Raynew(Center,Vector3new(0,i,0)) end 

A. Call __index in game to get Workspace
B. Call __index in Workspace to get FindPartOnRay
C. Call __index for the global value new in Ray.
D. Call __index for the global value new in Vector3.
E. Create a Vector with the function returned from D to create a blank Vector
For 10 times…

1. Create the second vector from the function stored in D to create a Vector3 with the coordinates of 0,i,0.
2. Reference the first vector from E and create the Ray from function stored in C
3. Pass the table the FindPartOnRay function is from (Workspace, so A) into the stored function in B with the Ray from 3.