Logs & Diagnostics: Difference between revisions
Created page with " == Logs & Diagnostics == This page explains the diagnostic information used to troubleshoot Lumiose Online. Diagnostic logs can help identify installation failures, launcher errors, game crashes, multiplayer connection problems, and other technical issues. The available logs and their locations may differ depending on your platform. == Supported Platforms == Lumiose Online supports four platforms: * Windows standalone launcher (ZA Recomp) * macOS (MonZaMac) * PC e..." |
No edit summary |
||
| Line 1: | Line 1: | ||
{{ArticleNav | |||
|section=Main Page | |||
|page=Logs & Diagnostics | |||
}} | |||
== Logs & Diagnostics == | == Logs & Diagnostics == | ||
Revision as of 21:57, 13 November 2026
Logs & Diagnostics
This page explains the diagnostic information used to troubleshoot Lumiose Online.
Diagnostic logs can help identify installation failures, launcher errors, game crashes, multiplayer connection problems, and other technical issues.
The available logs and their locations may differ depending on your platform.
Supported Platforms
Lumiose Online supports four platforms:
- Windows standalone launcher (ZA Recomp)
- macOS (MonZaMac)
- PC emulation (Eden)
- Nintendo Switch (Atmosphère)
The diagnostic information available on each platform may differ.
Common Diagnostic Logs
play.log
The play.log file records information about game execution.
It may contain:
- Game and launcher version information
- System and hardware information
- Game initialization events
- Runtime errors and warnings
This log is useful when investigating startup failures and gameplay problems.
crash.log
The crash.log file may be generated when the game encounters a crash.
Depending on the failure, it may contain:
- Exception information
- Memory access errors
- Stack traces
- Crash-related diagnostic details
This log can help developers investigate crashes and identify where a failure occurred.
Installation and Update Logs
Installation and update operations may produce additional diagnostic logs.
These can help investigate:
- Game file import failures
- Update preparation errors
- Compilation failures
- Missing or incompatible dependencies
The relevant files depend on the installation method and the stage at which the failure occurred.
Collecting Logs
When troubleshooting an issue:
- Reproduce the problem, if possible.
- Close the game or launcher after the issue occurs.
- Locate the relevant diagnostic files for your platform.
- Preserve the original log contents.
- Provide the logs when requesting technical support.
Avoid modifying log contents before submitting them, except when necessary to remove sensitive information.
Reporting an Issue
When requesting assistance, include:
- Platform and operating system
- Game version
- Lumiose Online version
- Description of the problem
- Steps required to reproduce the issue
- Exact error message, if available
- Relevant diagnostic logs
Before sharing logs publicly, review them for sensitive information such as usernames, local file paths, IP addresses, or authentication information.