> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qomicex.top/llms.txt
> Use this file to discover all available pages before exploring further.

# Running

## Running

After you launch the game, the **Running** page monitors and manages the game instances that are currently active.

## Instance status

Click **Running** in the sidebar (you can also get there from the home page or an instance page while a game is running):

* See which instances are running and how long they've been up
* End the game process directly

## Live log window

On the **instance details** page, open the dropdown next to the launch button and choose **Test game** to open the **live game log** window:

* The log scrolls in real time; there is no separate pause button — **scrolling away from the bottom stops following**, and scrolling back to the bottom resumes it automatically
* Color-coded filtering by level: INFO / WARN / ERROR / DEBUG / FATAL / Other
* **Keyword search** to jump straight to an anomaly
* **Stop game**: ends the process after confirmation (unsaved world progress is lost)

> The network request logging switch is not in the log window; it lives in the **Debug** panel (for diagnosing multiplayer or download problems).

When the game fails to start or hangs on the loading screen, the live log usually shows the last block of output. Copy it into [Log analysis](https://docs.qomicex.top/en/guide/log-analysis.md) to get a diagnosis.

## Crash handling

When the game crashes:

* The Running page or the log window reports **the game exited unexpectedly**
* Crash analysis takes over: the launcher parses the crash report and gives you a diagnosis (common causes: mod conflicts, out of memory, version mismatch)
* When you need help, generate an mclo.gs link to share (see [Log analysis](https://docs.qomicex.top/en/guide/log-analysis.md))


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.