Choose the symptom first
A frame-time spike and a latency spike can feel similar. Record what changes in the performance graph and whether the issue happens everywhere or in one area. For crashes, preserve the exact error. For loading problems, record whether the client is still responsive.
Use the diagnostic checklist to change one variable at a time. Keep the time, platform, area and result together so a later comparison is meaningful.
For network issues, test the actual destination
GGG’s connectivity primer explains how to find the instance address in Client.txt and trace that destination. A nearby speed-test server does not exercise the same route. When switching gateways, enter a fresh instance before comparing results.
A router that does not answer every diagnostic packet is not necessarily dropping game traffic. Check whether the apparent loss continues to the destination. Comparing wired and wireless connectivity can help isolate a local-network issue.
Prepare a useful support report
Write the exact reproduction, when it started, what you tried and what changed. For rendering issues, add hardware, renderer and driver details. Verify game files through Steam when installation damage is a plausible cause.
The tool generates a report draft locally. Review log excerpts before sharing them, and post through official support yourself. Similar forum complaints do not establish a server outage, so the tool does not display an invented live status.
Sources and further reading
Requirements derived from the dated game snapshot are separate from editorial advice. Linked player reports are not confirmations of current bugs.