The All Important Player IDs

Community Made Guides
1

I’ve used player ID’s in 2 of my guides, and I think it is now time to make a guide on it.

Concept
Player ID’s are a way to numerically identify players. I have 2 types: iterative and unique. Iterative ones are a bit more “expensive” in that they use slightly more memory. This uses the order that the players joined to use player ID’s. It needs a closed spawn area to work properly. Iterative player ID’s can be used to go scroll or iterate through the entire server to see who to act on. However, unique player ID’s just gives each person a unique one. These don’t care about order. Now, these can be used for the computer to recognize players that have done actions to other players. Basically, iterative ones are for players to use, and unique ones are for the computer to recognize.

3 days later: Player ID’s are the most important concept for peaceful interactions. I can not stress this enough!

Implementations

Iterative

Make a lifecycle that listens for game start. It should broadcast on “Start Game Start” (since its only for the game host). Make a relay that relays to everyone when receiving on “Start Game Start”. It should broadcast on “Game Start”. Make a “Num Players” global scoped number property, with a default value of 0. Make a “Player ID” player-scoped number property, with no default. Make a trigger triggered when receiving on “Game Start”. In the blocks, it should increment “Num Players” by one, and set “Player ID” to “Num Players”.

image

Here is the trigger’s blocks:

image
image730×195 27.3 KB

Unique

Gimkit already has a type of unique ID: names. These are pretty versatile as ID’s, but they can’t do everything that number ID’s can do. I won’t show you how to make them because unique number ID’s are useless because of names and iterative player IDs.

Difficulty
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
0 voters

Off Topic:
Let’s go! I got TL2!
3n+1 is one of the most interesting sequences ever!

25 Likes
2

Nice guide! Maybe delete the off-topic part, because it’s, well, off-topic. Nice guide overall! Congrats on @trust_level_2!

13 Likes
3

You can avoid off topic with:

Some examples of player IDs might be: 3, 10, 5, or 16.

3 Likes
4

Wait that’s confusing, you go from 1 thing to another?

2 Likes
5

It’s a chunk from the sequence 3, 10, 5, 16, 8, 4, 2, 1

1 Like
6

Also, is the “lets welcome _______ to our community” part of TL2?

1 Like
7

Oh!! I get it.

1 Like
8

Who did the 10? I know someone did it because it went from 5 all the way to 5.8 with one vote! Maybe @VALUEX?

1 Like
9

Thank you for the guide! Is it okay if I refer to this as iterative psuedo teaming?

1 Like
10

No, I don’t think its pseudo-teaming.

1 Like
11

Think about it. You’re putting each player on a separate team, with each team being a different amount of an item, and using that to do stuff to players.

3 Likes
12

No, I never mentioned teams.

13

If every player is on a different team, then their team acts like an ID.

15

Good idea! I never thought of that before!

16

Pseudo-teaming with items should work well since you know, properties take more memory to deal with, HOWEVER items can be dropped and if you don’t like that, then…

1 Like
17

Back to this pfp?

1 Like
18

Well it is only 2 properties… Also, unique number IDs are rendered obsolete by the other 2…

19

Place a zone that disables item dropping.

20

That’s not exactly affordable, since some games like among us needs item drop to work.

21

I was waiting until we got conflicting tech. Just pick a item that no one uses, give everyone one, then turn off notifications and psuedo team with one item as the default instead of zero. Add in some lore that the Gims need it to breathe, and have a checker check every 0.5 seconds if the amount of item is equal to zero for all players. If true, respawn player, and give them one of the item again.

5 Likes