# Match id gets always gets a period at the end

**URL:** <https://forum.heroiclabs.com/t/match-id-gets-always-gets-a-period-at-the-end/6539>\
**Category:** Runtime Framework\
**Created:** [March 24, 2026, 3:59pm UTC](https://forum.heroiclabs.com/t/match-id-gets-always-gets-a-period-at-the-end/6539 "2026-03-24T15:59:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![AllenPDX](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/allenpdx/32/2444_2.png) [@AllenPDX](https://forum.heroiclabs.com/u/AllenPDX)\
**Post date:** [March 24, 2026, 3:59pm UTC](https://forum.heroiclabs.com/t/match-id-gets-always-gets-a-period-at-the-end/6539/1 "2026-03-24T15:59:49Z")

</div>

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).

---

<div class="post-metadata">

**Author:** ![sesposito](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/sesposito/32/2594_2.png) [@sesposito](https://forum.heroiclabs.com/u/sesposito)\
**Post date:** [March 30, 2026, 10:18am UTC](https://forum.heroiclabs.com/t/match-id-gets-always-gets-a-period-at-the-end/6539/2 "2026-03-30T10:18:20Z")

</div>

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.