# Matchmaker requires game server process registration

> A scenario in which a Matchmaker requires a game server process to register themselves with the matchmaker, and the matchmaker decides which `GameServer` players are sent to.

---

LLMS index: [llms.txt](/site/llms.txt)

---

In this scenario, the `GameServer` process will need to self Allocate when informed by the matchmaker that players 
are being sent to them.

![Reserved Lifecycle Sequence Diagram](../../../diagrams/gameserver-reserved.puml.png)

<div class="alert alert-warning" role="alert"><div class="h4 alert-heading" role="heading">Warning</div>


This does relinquish control over how `GameServers` are packed across the cluster to the external matchmaker. It is likely
it will not do as good a job at packing and scaling as Agones.
</div>


## Next Steps:

- Read the various references, including the
  [GameServer](/site/docs/reference/gameserver/) and [Fleet](/site/docs/reference/fleet/)
  reference materials.
- Review the specifics of [Health Checking](/site/docs/guides/health-checking/).
- See all the commands the [Client SDK](/site/docs/guides/client-sdks/) provides - we only show a
  few here!
- If you aren't familiar with the term [Pod](https://kubernetes.io/docs/concepts/workloads/pods/pod/), this should
  provide a reference.