Help understanding parameters

Help and Feedback Scripting Support
#1

I’ve seen a few topics explaining parameters and I’ve read about them on developer.roblox.com, but I don’t fully understand them.

I have experience using them for example:

local function keyPressed (input, isTyping)
 if input.KeyCode == Enum.KeyCode.Q and not isTyping then
  SomeEvent:FireServer(mouse.Hit.p)
end

To further specify, I get how to use parameters like player, and how to call a function and send and receive parameters like I did above, but I’m just confused on whether parameters are already set in stone like the parameters “player” and “char” and how Roblox Studio can use both “char” and “character”.

An example of what confuses me:

function damage(hit)
 if hit.Parent ~= char then
  if hit.Parent:FindFirstChild("Humanoid") then
   etc.
end

Part.Touched:Connect(damage)

I guess what I want to find out is if the function above would work if I changed “hit” to “touch” or some other variable, as well as if there is a list of parameters.

4 Likes
#2

The parameter name could be whatever your heart desires.

3 Likes
#3

If that’s the case, then how do parameters like “player” or “char” work, is it in relevance to what the statement before was?
Ex:

game.Players.PlayerAdded:Connect(function(player)
end)
4 Likes
#4

In the PlayerAdded event the first parameter is always the player who joined

But on the urplayerparameter.CharacterAdded the first parameter is always the player’s character

4 Likes
#5

“I’m just confused on whether parameters are already set in stone like the parameters “player” and “char” and how Roblox Studio can use both char and character”

Not every parameter / argument is set in stone only some are. You can pass parameters through functions.

e.g

A custom function you can make with no “Set in Stone” parameters.

function joe(JoeSays) -- This is a custom function, which doesn't have "Set in stone" parameters.
print(JoeSays) -- Will print "Hello"
end
joe("Hello") -- We pass through what we want joe to say

A function Roblox provides, because it needs specific parameters for you to find who triggered the function

game.Players.PlayerAdded:Connect(function(Player) -- Player can be named anything, but will always be your player
print(Player) -- Will print your player's name
end)

I hope this solved your confusion. If you have any more questions, please be sure to reply.

4 Likes
#6

They are objects, strings, numbers, tables, etc being named as a variables. They are thrown in order and stay in the same order when you name them. ROBLOX has built in functions that always return a argument. You can name this arg whatever you want. Also, I should mention everything that is inside the parameters are considered arguments.

4 Likes
#7

This will print nil, not the players name. This is because the Player is an object, not a string value.

2 Likes
#8

Actually from my experience it will print the player object which is your name. I’ve tested this before, it works.

1 Like
#9

Events pass things through parameters automatically (in terms of a custom event it’s your choice) and the name is entirely up to you as @JustNylo said, but the information cannot be changed based on what you enter.

For example:

game.Players.PlayerAdded:Connect(function(Player)
print(typeof(Player)) -- will print player
Player:Kick("you got kicked")
end)

This code will work.

game.Players.PlayerAdded:Connect(function(robux)
print(typeof(robux)) -- will print player
robux:Kick("you got kicked")
end)

This code will also work. It’s pretty much identical to a variable, you can name it whatever you want, but the name doesn’t change the object listed in the variable, much like what’s passed through in an event, or what you choose to pass through in a custom event of your own (RemoteEvent, BindableEvent etc.)

A further example could be:

randomevent:FireServer(game.Players.LocalPlayer)

randomevent.OnServerEvent:Connect(function(jeffbezos)
jeffbezos:Kick("kick message!")
end)

Object sent doesn’t change, name of object being recieved can be changed, but not the object by it’s core. Basically, it won’t change the object on the sending end regardless of the name put in on the recieving end. i used to think it was just magic

2 Likes
#10

I’m not too sure, I would have to test it. From my experience whenever I did that, it printed nil. I always had to do Player.Name

1 Like
#11

Weird… Anyways here’s some proof to help eradicate the confusion:

1 Like
#12

Thank you! This clears up all the confusion I had. It did used to seem like magic before you and a few others helped explain that to me.

2 Likes