Match id gets always gets a period at the end

Runtime Framework
1

I had a quick question regarding the server implementation of match IDs.

It appears whenever a match ID is created, it’s using a deterministic UUIDv5 approach, but the UUID string always has a period appended to it. So for example:

_match = await _socket.CreateMatchAsync(“testmatch“);
Debug.Log(_match.Id);

// prints: 8fd22679-7227-5516-9b36-9244b38ec410.

Is there a reason for the period at the end?

Just curious. It’s not breaking anything, but it also doesn’t make it a valid UUID string (that I’m aware of).

2

Hi @AllenPDX,

Usually after the . there would be some metadata pertaining the node that’s running the match, this is used for routing purposes in Nakama Enterprise, but it is not needed in Nakama OSS so it’s empty.

Hope this clarifies.

1 Like