Hello! So, recently I thought, what's the use of Vector3 over CFrame? Could someone explain? Also, one last note, I know there is a use of Vector3 to teleport using CFrames, but what if I don't use vector3 here?
parent.Humanoid.Torso.CFrame = CFrame.new(Vector3.new(395, 1.5, -1699))
Just want to know :) Thanks!
The only reason why I'd use Vector3 over CFrame is that some things like Model:MoveTo() or Humanoid:MoveTo() use it. You could always use use parent.Humanoid.Torso.CFrame.Position which gets the Vector3 of the CFrame.
For beginners, Vector3 is simpler for them.
But still, I'd use CFrame for pretty much everything as things like Camera use it instead of Vector3.
Also, CFrames work like this:
CFrame.new(395, 1.5, -1699)
Not this.
CFrame.new(Vector3.new(395, 1.5, -1699))
You don't need to put a Vector3 inside CFrame.new().
I know, but I do
This discussion is preserved as it was. New answers, comments, and votes are closed.
1 comment
I think vector3 is more for bricks and CFRAME just teleports them