Skip to content
Gameye Docs

Changelogs

::ChangelogItem{type="added" description="Smarthost predicts how many players will need a session and then preloads sessions to create a buffer, although still in BETA to learn more about this new feature please refer to the relevant documentation."}

::ChangelogItem{type="improved" description="Gameye documentation has been updated to include how to integrate Photon Fusion and better information about implementing Dockerhub as part of the integration process"}

::ChangelogItem{type="fixed" description="Fixed a session-locking bug.
In rare cases, some servers were misbehaving and not going into a lock state, which meant they could overload themselves. We’ve fixed this now."}

::ChangelogItem{type="improved" description="Updated how labels work.
Just a small quality-of-life update. We’ve separated out Gameye-specific tags from other tags in the code. There are now three label types: tags (what you’ve defined), env, and Gameye."}

Before

{
  "labels": {
    "env": "<ENV_VARS_HERE>",
    "tags": "<ALL_USER_DEFINED_TAGS_AND_ALL_GAMEYE_TAGS>"
  }
}

After

{
  "labels": {
    "env": "<ENV_VARS_HERE>",
    "tags": "<ALL_USER_DEFINED_TAGS>"
    "gameye": "<ALL_GAMEYE_TAGS>"
  }
}

::ChangelogItem{type="added" description="You can now create a custom environment variable that points to a Gameye environment variable to query it."}

As an example, you can setup a custom environment variable called MY_SPECIAL_ENV_VAR and point it to a Gameye variable like below:

{
  "id": "my-super-nginx-test-session-1",
  "location": "europe",
  "image": "nginx",
  "env": {
      "MY_SPECIAL_ENV_VAR": "$GAMEYE_PORT_TCP_80",
      "MY_NOT_SO_SPECIAL_ENV_VAR": "CAKE"
  },
  "args": [],
  "restart": false
}

::ChangelogItem{type="improved" description="The focus of this release is to make the API endpoints more consistent and easier to work with."}

::ChangelogItem{type="improved" description="Server responses now reflect better what the issue is to help you troubleshoot the problem better."}

::ChangelogItem{type="added" description="[DELETE: /session] endpoint created so you can stop a specific session. This is replacing an old API endpoint &#xA;[/command/stop-match]. The old endpoint is currently marked for deprecation and will be removed in future versions."}

::ChangelogItem{type="added" description="[GET: /session] endpoint created so you can query current running sessions on the server. This is replacing an old API endpoint [/query/match]. The old endpoint is currently marked for deprecation and will be removed in future versions."}

::ChangelogItem{type="added" description="New examples to each of the endpoints to showcase how they can be used."}

::ChangelogItem{type="broken" description="Removed [/command/start-match]. This was a deprecated endpoint and is no longer available for use. "}

::ChangelogItem{type="broken" description="Removed [/action/start-match]. This was a deprecated endpoint and is no longer available for use. "}

::ChangelogItem{type="broken" description="Removed [/action/stop-match]. This was a deprecated endpoint and is no longer available for use. "}

▶️ Note that all endpoints are using the [match] keyword are currently deprecated and will be removed in future versions. This includes [/query/get-match] and [/command/stop-match]

▶️ You can access our latest APIs using this link.

::ChangelogItem{type="added" description="Port Forwarding feature has been added to docker images. If this feature is enabled in your server image, when Docker randomly allocates ports we pass those ports to the environment variables. A bridge network is created and we port forward the allocated ports to the container's underlying ports. This also means ports are known upfront. &#xA;&#xA;To take leverage of this option, please contact us through Discord requesting this feature."}

::ChangelogItem{type="fixed" description="Fixed an issue with integration to Google Cloud hosted servers."}

::ChangelogItem{type="improved" description="Improved stability and robustness of our internal database."}

::ChangelogItem{type="improved" description="Error messages received when sending an improper request to the server. Previously you'd get &#x22;socket hang-up&#x22;. Now, you will get standard error codes such as 404, 409, 420 or 422 depending on the issue."}

::ChangelogItem{type="added" description="Support for user-defined tags. You are able to add a tag to the sessions you create. This is included in the [labels] property of the APIs."}

::ChangelogItem{type="added" description="Support to filter queried sessions using the tags. For example, if you provide a tag [&#x22;my-example&#x22; : &#x22;1&#x22;] to the session, you can then later filter queried session using https://api.gameye.com/query/match?filter[my-example]=1. &#xA;Note you can chain multiple filters together."}

▶️ You can access our latest APIs using this link.

::ChangelogItem{type="fixed" description="Fixed an issue with one of our background services shutting down due to an internal error. "}

::ChangelogItem{type="added" description="Real time logs are now available for any active session. You can access this using the new API endpoints. "}

::ChangelogItem{type="improved" description="We've enhanced the stability of our internal systems considerably."}

::ChangelogItem{type="improved" description="We've enhanced how sessions are handled and distributed over the requested regions."}

▶️ You can access our latest APIs using this link.