Truth is, every instance has the ability to do this. In fact, anything that can be called as a method can be indexed as a regular variable, or property. Methods alone, are an abstract way of demonstrating that the function being called, is operating on that specific object (without passing it as an argument).
Tables (aka, Objects)
This ultimately brings us to tables. All of these instances we refer to, are all fundamentally tables. Don't believe me? Try executing this code in studio:
1 | print(getmetatable(Instance.new("Part"))) |
You should see a result that reads: "The metatable is locked" - Implying we're working with tables.
Anyway, the reason I'm bringing all this up is because we can simulate the exact same thing with tables (or objects), and their methods.
How methods really work
You've probably seen the correlation between using : and . to create (or call) functions in a table before. Either way you write it, you can still call it the same way. So why are there two ways to write it in the first place? Well, it's all in the "self" variable.
A somewhat hidden feature of methods (calling a function on a table (object), by using a colon), is the fact that the object you're calling the method on, is actually being passed as an argument to the function.
For example, say I had a table called "t", and a method attached to it called "GetSelf", here's what it'd look like:
So, as we can see, calling it as a method (since that's what we assigned it to be) with the :, gives it the ability to reference itself with a built-in variable that we can't otherwise use if we call it using a .
That's the first part to understanding this. The second part, is realizing it's parameter is actually required if you're going to call it with a . instead of :
Sounds confusing, but practice it enough, and you'll understand it faster than you think. Here's an example:
The reason the t.GetSelf(t) example returned anything at all, is because we didn't call it as a method. So by default, it's first argument is expected to be the 'self' variable.
Applying this to your question
Applying all this information to your question, will work the exact same way! If we were to say something like:
1 | workspace.Part:Destroy() |
If we said something like this, however...
1 | workspace.Part.Destroy() |
So we could easily fix it like:
1 | workspace.Part.Destroy(workspace.Part) |
4 | Instance.new("Part").Destroy(workspace.Part) |
Anyway, hope this wasn't too confusing. If you have any questions just let me know, and I'll get back to it as soon as possible.
0