| Player ID Research |

Devices
,
87

Wait, I checked, this uses a UTC (Coordinated Universal Time).
You generate ObjectIds in two different time zones — say:

  • One in New York (UTC-4)
  • One in Tokyo (UTC+9)
  • Both at “May 2, 2025, 12:00 PM local time”

These would not produce the same ObjectId timestamp portion because:

  • New York 12:00 PM = 16:00 UTC
  • Tokyo 12:00 PM = 03:00 UTC

So their ObjectIds would have different timestamps, even though the local time was the same.

4 Likes
88

So the beginning is local, but the objectid function returns it utc

1 Like
89

that would mean that if you were to play internationally, even if the local time is the same, they IDs would be different? (I sound like I’m rambling for no reason lol, I just need to make sure I’m not misunderstanding your point here)

3 Likes
90

Even I don’t fully understand. I’m not rocket scientists on this. I’m just using ChatGPT to understand.

91

Yeah they’d be unique cause processing section and objectid function

92

Valid, lol.

So, let’s break it down further. Taking a look at the charts you provided, the ObjectId is the PlayerId, so in order to be able to create mechanics with this, we need to understand ObjectId. Studying time!

1 Like
93

So Ids will never be the same, which makes sense. Correct?

2 Likes
94

So…more ChatGPT.

Apparently, based on where you make it, they’ll grab the local time and find the UTC of it. For example the New York one. Then using the UTC they’ll make an id. So if I traveled to Moscow which has a different timezone, the time of creation will be that of New York. In short, this means that YOUR ID should match YOUR time. (I think)

95

THE LAWS OF THE PLAYER ID:

LAW I: No player ID shall be identical [T]

or like

THE PLAYER ID AMENDMENTS:

1st AMENDMENT: No player ID shall be identical [T]

yeah

rules for this device so we can further understand it but I just put a fun twist because why not

6 Likes
96

Intresting. Here, lemme transcribe all the ID’s into text that we can copy paste:
6814c39a5fea7a4d9c6bbbf9
6814c574cdcae9f0ce61e8dd
6814d30d5e4163cb82b394f3
6814d994cc870cb30dab96e3
6814da939ed42b5f92db09fb
6814da7251e94f69401a82d0
6814d9c640a60a402c85a27c
6814ddf53194731e937eea86
6814dde26c7d7784e0818a1f
681505045e4163cb82d0ca87

3 Likes
97

For convenience I sorted them in chronological order

6814c39a5fea7a4d9c6bbbf9
6814c574cdcae9f0ce61e8dd
6814d30d5e4163cb82b394f3
6814d9c640a60a402c85a27c
6814d994cc870cb30dab96e3
6814da7251e94f69401a82d0
6814da939ed42b5f92db09fb
6814dde26c7d7784e0818a1f
6814ddf53194731e937eea86
681505045e4163cb82d0ca87

3 Likes
98

So for each of these consecutively,

  1. 8:07 AM. May 2
  2. 8:15 AM. May 2
  3. 9:13 AM. May 2
  4. 9:41 AM. May 2
  5. 9:45 AM. May 2
  6. Again 9:45. May 2. Seconds are different, 5 was at 33 and 6 was at 6 sec or smt.
  7. 9: 42. May 2
  8. 10:00. May 2. 5 sec past tho, sadly. Could have been 10 on the dot.
  9. 9:59. May 2. 49 seconds in. Also so close.
  10. 12:46. May 2.

Going off for a bit.

4 Likes
99

In short: Every second (literally) counts.

Okay, so what do we know so far? Let’s recap, make a wiki reply or something so we can stay organized with this (ocd aurgh)

4 Likes
100

right-o, we’ll catch you up when you return.

As I was saying, recap?

4 Likes
101

Ok let’s see
Id has timestamp with seconds since unix epoch
Each id contains the local and utc time
Time based games are possible
Some type of device address in ID

Repost image
Image

Gotta go - cyall

102

yeah, I’m gonna get off too. Though, that’s some good progress for, what, 3 hours? nice.

5 Likes
103

No Problem!

We have identified that in fact, the first string of the hex value (first 8 hex char) is the date using UTC.

Next, the 6 chars behind it are the machine ID, (not sure what this is. Host resolution?)

Next 4 are the Process ID for the gimkit servers (I hope yall will know what this is. If not, a process id is a name fore this “process” in short tersms)

Next 6 should be the random “id” part of it.
The ones that are truly unique to the player

2 Likes
104

This is prob like the device id or smth

105

Soooooooo… This won’t work for save codes because of the time? Oof.

1 Like
106

Not sure. If this is true tho. if it is a hardware id:

  1. it should remain constant, but is not.
  2. GKC servers should not be able to fetch our hardware signiture…

No, im pretty sure it will

3 Likes