Coding things you probably didn't know (part 1)

Resources Community Resources
#10

hehe no worries i meant no offence
my words don’t contain any sarcasm
sorry it confused you
i am not sad no worries

1 Like
#11

The things that helped me were continue.

_G is especially for global functions, where you can access things from other scripts if you set them.

and & or can be used like this:

animator = script.Parent:FindFirstChild("Humanoid") or script.Parent:FindFirstChild("AnimationController")
3 Likes
#12

and & or can also be used to make a type of if statements

local randomBool = math.random(1, 2)==1 and true or false
1 Like
#13

Fun fact there is also the global table “shared” that even less people know of. Also I reccomend you fix some spelling errors. Also don’t use for I,v in next, table, don’t do that.

3 Likes
#14

i didnt know that mind if i can use it in my tutorial and sorry for my spelling

1 Like
#15

Great tutorial but I have some critiques:

  • Your code uses properties that don’t exist, such as Player.team, where it should be Player.Team.
  • You don’t really explain how next operates and what’s happening in the code sample.
  • You’re not using proper English that people can understand. (You’re using slang like “peps”).
  • In the “to long” section, for your second code example, you didn’t explain why what you did was better other than it was “short.”
  • Mainly, there’s a lack of explanations.

Majority of my critiques are just nitpicks so don’t take them personally.

6 Likes
#16

This is not true. The table does not replicate from client-server, but can be used on client.

3 Likes
#17

guess my resources are wrong woops gonna fix that

#18

i removed the _G what do you think now @HugeCoolboy2007

#19

Please use commas and grammar, it is extremely difficult to read this.

5 Likes
#20

wow thank you, never knew shared existed :sweat_smile:

1 Like
#21

i tried my best to fix it but i am no grammar dude its my least favorite subject

1 Like
#22

me either i didn’t know till today but please… use modules

1 Like
#24

it was actually was the original tittle for number

#25

Aahhh this is soo cool tysm, i want more things like that

2 Likes
#26

i might make a part two lol when i learn more uncommon stuff

1 Like
#28

I wonder why does shared exist, if _G already did…

But hey, here’s more coding things that you probably didn’t know about, with good grammar as well!

Roblox Globals
Lua Globals (roblox.com)

2 Likes
#29

sorry that my grammar sucks its not my best subject

2 Likes
#31

next

Please don’t write loops this way, it’s unreadable. I know that pairs implements next (unless it doesn’t in Luau) but you should just use one of the proper generators when iterating; ipairs for contiguous arrays where ordering might be important and pairs for dictionaries.

Fake ternary (and & or)

Same as the above: be careful when you’re using this. There are some cases where developers may get “unexpected results” but that’s just a case of using this wrong. Luau doesn’t have a ternary operator so this is the closest that can be done without being actual ternary, this is just taking advantage of the way operators evaluate.

shared (or _G)

Good call: please never use either of these, opt for ModuleScripts. There are very exceptional cases where you need to use the global table otherwise try not to use it.

Dictionaries (“too long…”)

Each of these code samples has a minor problem.

  • Please use PascalCase when referring to properties. Team and Name should have a capital T and N respectively. The lowercase variants are deprecated aliases.

  • The second sample doesn’t work the way you think it does. You’ve created an array of teams but the indices of these are all numerical. You’re attempting to access this table via the indice of the player’s team name which will be nil. For this to work, the indices need to be strings and the value needs to be non-nil. See example [1] for a fixed version.

  • The third sample also will not work the way you intend because “White” is not a property of “Name”. You’d need to use the == operator (is equal to) for this instead. See example [2].

[1]:

local onlyTeams = {
    ["Green"] = true,
    -- same for the rest of the teams
}

if onlyTeams[player.Team.Name] then
    -- Commit action
end

* table.find is acceptable as well, but you need to be aware of what value types you’re including in the table. The original organisation of the table is invalid since a player cannot be on multiple teams at once.

[2]:

if not (player.Team.Name == "White") then
    -- Commit action
end

* The parenthesis are required to define what you’re checking which then the not operator flips the result of the evaluation in the parenthesis. Alternatively, you can use the ~= (not equal to) operator and avoid using not. A common mistake is not to include these in parenthesis; the not would only act on the left-hand operand not the whole evaluation.

if player.Team.Name ~= "White" then
    -- Commit action
end
9 Likes
#32

whoops agree on the last one gonna fix it also thx for feedback and what is