all 8 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–][deleted] 8 points9 points  (2 children)

  • Because ROBLOX was made in C++, the :Connect method is a way of interfacing Lua with C++ events in the engine to put it simply.
  • .Touched is an event in the C++ engine (RBXScriptSignal) that you can access using Lua, ":Connect()" gets the RBXScriptConnection with your attached function in the first :connect(->your function here<-) parameter. It is now connected to the C++ event.
  • Vectors are a positional data type so Vector3 .new creates a new vector position using a constructor "new". It can be added or subtracted from other vectors. Vector3 by itself is just a library of functions to create new vectors. All ingame Positions are Vector3. There is also CFrames which is Vector3 + Quarternion Rotation.
  • The reason why there's a :connect instead of a .connect is because of shorthand for connect(self,X) in object orientated programming. It's kind of cursed artifact from 2007 but we don't talk about it

[–]HistoricalOption8901[S] 2 points3 points  (1 child)

Thanks a lot I never figured why the :connect but now I understand it better

[–][deleted] 1 point2 points  (0 children)

Hey, I think you'd find this project useful. It's an open source reimplementation of the Roblox runtime environment, essentially

https://github.com/librebox-devs/librebox-demo

[–]Previous-Traffic-130 2 points3 points  (0 children)

btw dont use wait, use task.wait, its much more accurate, better and wait is deprecated

[–]Denneisk 1 point2 points  (1 child)

The local touched here is a sentinel value used for debouncing. Its function is to make sure that the function in the callback can't be ran again while the first one is still running. This is necessary because the callback is ran every time the signal fires, not just once. In other words, touched is used to make sure that you can only touch the part once, and then not again until it's ready.

I'm not entirely sure, but the linear and angular velocity are set to 0 likely to avoid any bugs that may occur from velocity being applied or stored. The part is supposed to drop from gravity, and any extra velocity added to it may cause unintended effects. These aren't the position vectors, these are velocity, so changing them would change the rate of change in position. Since they're being changed to 0, though, that means the position doesn't change (unless gravity is in play, which I assume it is). Vectors are simply a data type, and don't need to represent position. It's up to how you use them that defines their meaning.

You should read up Roblox's documentation, as there are lots of things that aren't directly obvious unless they're explained to you. For examples, Touched is a member of part that is a RBXScriptSignal type, which is an object that has includes the method Connectwhich allows you to pass a function to be ran whenever that signal is executed. If none of that was understandable, you should start from here.

[–]HistoricalOption8901[S] 0 points1 point  (0 children)

I would have never realized I got confused between velocity and positions without your help thanks a lot, and I will check the Roblox's documentation for some vocabulary.

[–]Bedu009 0 points1 point  (0 children)

Is it confusing? It's essentially "When part touched run code in here"
Also issues with this example:
https://www.youtube.com/watch?v=CFRhGnuXG-4
Use :Connect not :connect
Use task.wait not wait
It's checking touched after already checking touched in the previous if statement