Game Server Support Ticket: Send Evidence That Helps

A useful game server support ticket makes the problem reproducible. “The server is broken” tells support that help is needed, but not where to start.

Collect a small, relevant evidence set before changing the environment again.

Describe the incident

Include the game, server identifier, affected players, and exact error text. Give the time and timezone. State whether the issue happens during startup, joining, or a particular in-game action.

List recent changes such as updates, new mods, plan changes, or a migration. Distinguish facts from your current theory about the cause.

Attach the right evidence

Provide the relevant log excerpt or report through the support channel's accepted method. Preserve enough surrounding context to show the first failure, not only the final shutdown line.

Remove passwords, tokens, and unnecessary personal information. Keep an unmodified private copy if support needs a more complete review later.

Explain what you tested

List each attempted fix and its result. Include a minimal set of steps support can follow to reproduce the issue.

If the problem is intermittent, say how often it occurs and what conditions seem related. Avoid claiming a fix failed if it was never tested under the original conditions.

Should I reinstall before opening a ticket?

Not automatically. Reinstallation can remove evidence or alter the state support needs to inspect. Preserve data and describe the issue first.

See Minecraft crash-log triage and Palworld timeout diagnosis for game-specific evidence collection.

Choose your next step

Compare EZ Game Host plans against your game, expected workload, and backup needs. Start with a plan you can measure, and revisit it after a representative busy session.