> For the complete documentation index, see [llms.txt](https://gamelauncher.cloud/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gamelauncher.cloud/help/changelog/2026/july-05-2026.md).

# July 5, 2026

## CDN Mirror

{% hint style="success" %}
**NEW FEATURE:** Launchers can now use a custom CDN as a **download mirror**, giving you control over bandwidth costs and better reachability in restricted regions.
{% endhint %}

A new **CDN Mirror** tab is available in each launcher's settings.

<figure><img src="/files/N8Z1dfu0ZBBcDQuO6Ygy" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/S3uv2BhloKieC4hUwstT" alt=""><figcaption><p>CDN Mirror</p></figcaption></figure>

### Bring Your Own CDN (BYOC)

* **Enable Custom CDN Mirror** — Point your launcher at your own CDN Pull Zone. Once enabled, the desktop launcher prefers your CDN URL when downloading builds.
* **Provider presets** — Quick setup for Custom S3-Compatible, Amazon CloudFront, BunnyCDN, Google Cloud CDN, Cloudflare R2, DigitalOcean Spaces, Backblaze B2, and Wasabi.
* **Public CDN URL** — The public host your CDN serves files from — this is the URL your players actually download from.
* **Mirror Status panel** — Test your CDN connection on demand and see the last validation timestamp and last error at a glance.

### Automatic Mirror Failover

The desktop launcher walks an ordered list of mirror URLs per file and transparently falls through to the next one on failure (network errors, server errors, timeouts) — with no player-facing interruption. For countries with known connectivity restrictions to our primary CDN, your custom mirror is automatically prioritized first.

***

## Support Ticket System

{% hint style="success" %}
**NEW FEATURE:** Subscribers can now open and track **Support Tickets** right from the dashboard.
{% endhint %}

A new **Support Tickets** section is available from the profile dropdown, giving you a proper support channel alongside our Discord community.

### Creating & Tracking Tickets

* **New Ticket** — Open a ticket with a subject, category (**General**, **Technical**, **Billing**, or **Bug Report**), a message, and optional file attachments (screenshots, logs).
* **Ticket List** — See all your tickets with status and category filters, last-activity timestamps, and at-a-glance status badges.
* **Ticket Thread** — Each ticket opens as a message thread between you and the support team. Image attachments render as inline previews (capped to a maximum size) instead of requiring a download, and every message shows the sender's avatar.

### Ticket Status

| Status                  | Meaning                                  |
| ----------------------- | ---------------------------------------- |
| **Open**                | Newly created, awaiting a first response |
| **In Progress**         | Support is actively working on it        |
| **Waiting on Customer** | Support is waiting on more info from you |
| **Resolved**            | Support considers the issue fixed        |
| **Closed**              | Ticket is closed and read-only           |

* Replying to a **Resolved** or **Closed** ticket automatically reopens it.
* Tickets are **automatically closed after 30 days** of no customer reply, keeping the queue clean.
* Only the support team can close a ticket — you can reply anytime, but closing is staff-only.

### Notifications

* You'll get an email confirmation when your ticket is created, and another whenever support replies.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://gamelauncher.cloud/help/changelog/2026/july-05-2026.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.