Jump to content

Logs & Diagnostics: Difference between revisions

From LumiWiki
← Older edit

Guinevere (talk | contribs)

3 user groups
167 edits
VisualWikitext
No edit summary
No edit summary
 
Line 55: Line 55:
=== Diagnostic Log Reference ===
=== Diagnostic Log Reference ===


The following files have been observed in the <code>logs</code> directory of a Windows ZA Recomp installation. The precise contents and availability may vary by launcher version.
The Windows standalone installation maintains several diagnostic logs. The descriptions below are based on examined ZA Recomp and Lumiose Online logs; file availability and contents may vary by release.


{| class="wikitable"
{| class="wikitable"
! Log File
! Log File
! Likely Purpose
! Recorded Information
! Typical Use
! Recommended Use
|-
|-
| '''launcher.log'''
| '''launcher.log'''
| ZA Recomp launcher and game preparation diagnostics.
| A timestamped history of launcher runs, game import, game-code generation and compilation, update notices, and other launcher operations.
| Installation, import, and launcher startup failures
| Import failures, compilation errors, updates, and launcher startup issues
|-
|-
| '''lumiose-launch.log'''
| '''lumiose-launch.log'''
| Lumiose Online launch-related diagnostics.
| Lumiose launcher startup, initial setup requirements, game-code revision checks, preparation of bundled Lumiose builds, and update checks.
| Failures starting Lumiose Online
| Lumiose-specific setup, preparation, and launch failures
|-
|-
| '''play.log'''
| '''play.log'''
| Game execution and runtime events.
| Detailed game execution information, including ZA Recomp version, CPU, RAM, graphics device and Vulkan driver, rendering configuration, game initialization, and runtime events.
| Startup failures, gameplay problems, runtime errors
| Gameplay, startup, rendering, and performance issues
|-
|-
| '''play-anterior.log'''
| '''play-anterior.log'''
| An additional gameplay log, potentially containing earlier session output. Its exact rotation behavior has not yet been verified.
| An additional retained runtime log containing the same kinds of execution details as play.log. The exact rotation mechanism has not been verified.
| When play.log is empty or does not cover the affected session
| When play.log is empty or does not describe the affected run
|-
|-
| '''crash-YYYYMMDD-HHMMSS.log'''
| '''crash-YYYYMMDD-HHMMSS.log'''
| Timestamped crash diagnostics, when generated.
| Timestamped crash-related runtime diagnostics, which may include exception codes, fault addresses, and backtraces alongside preceding execution output.
| Application crashes, exceptions, access violations
| Unexpected termination, access violations, and crash investigation
|-
|-
| '''smoke.log'''
| '''smoke.log'''
| Diagnostic output from isolated startup or preparation checks.
| Detailed game initialization and execution output from an isolated startup check performed during Lumiose preparation.
| Isolated startup and update preparation failures
| Update preparation failures and “Isolated startup did not finish” errors
|-
|-
| '''capture.log'''
| '''capture.log'''
| Diagnostic output associated with preparation or capture operations.
| Detailed game initialization and execution output associated with an isolated capture/preparation stage.
| Update preparation and related failures
| Preparation and capture-stage failures, especially alongside smoke.log
|}
|}


The first five filename patterns above were observed in an installation's <code>logs</code> directory. The <code>smoke.log</code> and <code>capture.log</code> files may instead appear in temporary update working directories. Not every installation or failure generates every file.
The first five log patterns have been observed in the main <code>logs</code> directory. The <code>smoke.log</code> and <code>capture.log</code> examples were collected from temporary update-preparation working directories. Not every failure produces every log.


=== Finding the Main Log Directory ===
=== Finding the Main Log Directory ===


Open the folder containing '''lasrecomp.exe''', then open its '''logs''' directory.
Open the folder containing '''lasrecomp.exe''', then open '''logs'''.


'''Example:''' <code>D:\Games\Switch\ZA Recomp\logs\</code>
'''Example:''' <code>D:\Games\Switch\ZA Recomp\logs\</code>


Check file modification times to identify logs associated with the reported failure. A log may be empty, and an older log may describe a different incident.
Use file modification times to identify the logs associated with the incident. Some files contain records from multiple launches, and a log may be empty.


=== launcher.log and lumiose-launch.log ===
=== launcher.log ===


These files have been observed in the main <code>logs</code> directory. Based on their names, they are useful starting points for launcher and Lumiose Online startup failures, respectively. Their exact contents have not yet been verified.
The '''launcher.log''' file contains timestamped records of ZA Recomp launcher activity across multiple runs. Examined examples include:


'''When to collect:'''
* The ZA Recomp version, operating system, CPU, and available disk space
* Game package import and update application results
* Game-code generation and compilation, including compiled object counts and elapsed time
* Launcher update availability and other startup operations


* The launcher cannot import or prepare the game.
This is a useful first log for problems occurring '''before gameplay begins''', particularly game import and compilation failures.
* Lumiose Online fails to start.
* An error occurs before normal gameplay begins.


Collect both files when the source of a startup failure is unclear, if they are present.
'''Location:''' <code>&lt;ZA Recomp installation folder&gt;\logs\launcher.log</code>


=== play.log ===
=== lumiose-launch.log ===


The '''play.log''' file records information about game execution.
The '''lumiose-launch.log''' file records Lumiose-specific launcher preparation. Examined entries include whether initial setup or a game-code revision check is required, preparation of the bundled Lumiose build, checking active builds and updates, and completion of preparation.


Depending on the launcher version, it may contain:
Collect this file when Lumiose Online fails to prepare or launch, particularly if ZA Recomp itself otherwise starts normally. It can be helpful alongside <code>launcher.log</code>.


* ZA Recomp version information
'''Location:''' <code>&lt;ZA Recomp installation folder&gt;\logs\lumiose-launch.log</code>
* Windows version
* CPU and system information
* Game initialization events
* Launcher status messages
* Runtime warnings and errors


'''Location (Windows standalone launcher):'''
=== play.log and play-anterior.log ===


<code>&lt;ZA Recomp installation folder&gt;\logs\play.log</code>
'''play.log''' records detailed game execution. The examined logs include:


For example:
* ZA Recomp version, Windows version, CPU capabilities, and memory
* GPU identification, Vulkan API and graphics driver information
* Rendering settings, resolution, shader pipeline and cache messages
* Game-code loading, initialization, and runtime events
* Warnings and errors associated with graphics drivers or game execution


<code>D:\Games\Switch\ZA Recomp\logs\play.log</code>
For example, an examined gameplay log reported that an AMD graphics driver compiler crashed while processing certain pipelines. Such entries can be useful when investigating graphical problems, although a warning alone does not establish the cause of a reported failure.


'''How to locate play.log:'''
'''Locations:'''


# Open the folder containing '''lasrecomp.exe'''.
* <code>&lt;ZA Recomp installation folder&gt;\logs\play.log</code>
# Open the '''logs''' directory.
* <code>&lt;ZA Recomp installation folder&gt;\logs\play-anterior.log</code>
# Locate '''play.log'''.
# Attach the file when requesting technical support.


'''When to collect:'''
'''play-anterior.log''' has been observed containing substantial runtime output while <code>play.log</code> was empty. Inspect both files and compare their modification times before selecting the log to send.


* The game fails to launch.
{{Notice
* The game starts but encounters errors.
|type=info
* Gameplay behaves unexpectedly.
|title=Log Retention Not Yet Verified
* The launcher displays a runtime error.
|The examined files establish that play-anterior.log can contain retained gameplay diagnostics, but do not conclusively establish when it is created, replaced, or rotated. Do not assume it always contains the immediately preceding session.
 
}}
When possible, reproduce the issue and collect the log from the affected session. If <code>play.log</code> is empty, check <code>play-anterior.log</code> and its modification time.
 
=== play-anterior.log ===
 
The '''play-anterior.log''' file has been observed alongside <code>play.log</code> in the main <code>logs</code> directory. It may contain earlier gameplay output, but the exact file rotation behavior has not yet been verified.
 
'''When to collect:'''
 
* <code>play.log</code> is empty.
* <code>play.log</code> does not cover the session in which the issue occurred.
* Support staff request additional runtime context.
 
Check the file's modification time before assuming it contains the relevant session.


=== Timestamped crash logs ===
=== Timestamped crash logs ===


Crash diagnostic files have been observed with names such as <code>crash-20261109-153832.log</code>. The general observed pattern is:
Crash logs have been observed under the pattern:


<code>crash-YYYYMMDD-HHMMSS.log</code>
<code>crash-YYYYMMDD-HHMMSS.log</code>


Depending on the failure, these files may contain:
'''Example:''' <code>crash-20261108-164732.log</code>
 
* Exception codes
* Faulting memory addresses
* Host backtraces
* Guest function references
* Crash-related diagnostic information
 
For example, an exception code such as '''0xC0000005''' indicates an access violation. An access violation does not, by itself, establish the underlying cause of a crash.
 
'''Observed location:''' <code>&lt;ZA Recomp installation folder&gt;\logs\</code>
 
'''When to collect:'''
 
* The game closes unexpectedly.
* The launcher or game crashes during startup.
* The game crashes during gameplay.
* An exception or backtrace is generated.
 
{{Notice
|type=tip
|title=Crash Investigation
|When reporting a crash, collect the timestamped crash log matching the incident and the relevant gameplay log if available. Avoid sending unrelated crash logs from older sessions unless requested.
}}


=== smoke.log ===
These logs may contain detailed execution context as well as crash-specific information such as exception codes, memory addresses, and host backtraces. For example, <code>0xC0000005</code> denotes an access violation, but does not by itself identify its root cause.


The '''smoke.log''' file contains diagnostic information associated with isolated startup or update preparation checks.
'''Location:''' <code>&lt;ZA Recomp installation folder&gt;\logs\</code>


This log may be relevant when the launcher reports errors such as:
When reporting a crash, select the timestamped file corresponding to the incident and include the relevant gameplay log if available. Do not send unrelated historical crash logs unless requested.


* Update preparation failed
=== smoke.log and capture.log ===
* Isolated startup did not finish
* Game preparation or validation failed


'''Location (Windows standalone launcher):'''
These logs have been observed during Lumiose update preparation and isolated execution checks. Both can contain detailed game initialization traces rather than merely a short summary of the operation.


<code>&lt;ZA Recomp installation folder&gt;\lumiose\update-work\initial-*\smoke.log</code>
* '''smoke.log:''' An examined example records an isolated game startup with initialization, service calls, loaded game code, and Lumiose-related execution information.
* '''capture.log:''' An examined example records initialization and execution activity in an isolated capture/preparation environment.


The '''initial-''' directory contains a variable suffix generated during update preparation.
Both are especially useful when the launcher reports '''“Update preparation failed”''' or '''“Isolated startup did not finish”'''. Their precise division of responsibility within the preparation pipeline still requires confirmation from project source code.


For example:
'''Observed directory pattern:'''


<code>D:\ZA-Recomp-windows\ZA Recomp\lumiose\update-work\initial-_ql5vc3z\smoke.log</code>
<code>&lt;ZA Recomp installation folder&gt;\lumiose\update-work\initial-*\</code>


The exact directory name differs between preparation attempts.
The <code>initial-*</code> directory has a variable suffix. Search it for <code>smoke.log</code> and <code>capture.log</code> if present.


'''How to locate smoke.log:'''
'''How to collect temporary preparation logs:'''


# Open the folder containing '''lasrecomp.exe'''.
# Open the folder containing <code>lasrecomp.exe</code>.
# Navigate to '''lumiose → update-work'''.
# Navigate to <code>lumiose\update-work</code>.
# Look for a directory beginning with '''initial-'''.
# Look for a directory beginning with <code>initial-</code>.
# Open that directory.
# Copy <code>smoke.log</code> and <code>capture.log</code>, if present, to a safe location before retrying.
# Locate '''smoke.log'''.
# Include the exact launcher error message when submitting the files.
# Copy the file to another location before retrying the failed update.
# Attach the copied log when requesting technical support.


{{Notice
{{Notice
|type=warning
|type=warning
|title=Temporary Diagnostic Files
|title=Preserve Temporary Logs
|The initial-* working directory is normally removed after update preparation completes successfully. If an update fails and the directory remains available, collect its diagnostic files before retrying. A later successful update may remove the directory and its contents.
|Update-preparation working directories may be cleaned up after a successful attempt. Collect any available logs before retrying or reinstalling, because the relevant files may become unavailable.
}}
}}


'''When to collect:'''
=== Finding Logs with PowerShell ===


Collect this log when an installation or update preparation operation fails and the file is available.
Windows users can search their ZA Recomp installation for the relevant files. Replace the example path with the actual installation folder:
 
=== capture.log ===
 
The '''capture.log''' file contains diagnostic information associated with preparation or capture operations.
 
It may be useful when investigating:
 
* Update preparation failures
* Game preparation errors
* Failures occurring before normal gameplay begins
 
'''Location:'''
 
The exact location has not yet been verified.
 
If an update preparation failure occurs, inspect the relevant working directory under:
 
<code>&lt;ZA Recomp installation folder&gt;\lumiose\update-work\</code>
 
Look for '''capture.log''' if it is present.
 
'''When to collect:'''
 
Collect this log alongside smoke.log when investigating an update preparation failure, if both files were generated.
 
{{Notice
|type=info
|title=Diagnostic Log Availability
|Some logs are only generated during specific operations or failure conditions. A missing log file does not necessarily indicate an installation problem.
}}
 
== Finding Logs with PowerShell ==
 
Windows users can search their ZA Recomp installation for diagnostic files using PowerShell. Replace the example installation path with the location of your own ZA Recomp installation:


<pre>
<pre>
Line 280: Line 205:
</pre>
</pre>


The command searches the installation directory and its subdirectories, displays modification times and file sizes, and does not modify or delete any files. It also checks for a legacy or alternate <code>crash.log</code> filename, although timestamped crash filenames were observed in the installation documented here.
This command only lists matching files, their locations, modification times, and sizes; it does not modify them. A missing temporary log does not necessarily indicate an installation problem.
 
{{Notice
|type=tip
|title=Searching for Temporary Logs
|If smoke.log or capture.log cannot be found after a successful update, the temporary working directory may already have been removed. This is expected behavior for completed update preparation.
}}


== Which Logs Should I Collect? ==
== Which Logs Should I Collect? ==
Use the following table to identify the most relevant diagnostic files for a reported issue.


{| class="wikitable"
{| class="wikitable"
Line 296: Line 213:
! Recommended Logs
! Recommended Logs
|-
|-
| Game fails to start
| Game import or code compilation fails
| launcher.log, lumiose-launch.log, play.log (if populated), and relevant crash log if generated
| <code>launcher.log</code>, exact error message
|-
| Game crashes during gameplay
| Timestamped crash log and play.log; check play-anterior.log if needed
|-
|-
| Update preparation fails
| Lumiose preparation or launch fails
| launcher.log, lumiose-launch.log, smoke.log, capture.log if generated
| <code>lumiose-launch.log</code>, <code>launcher.log</code>, <code>play.log</code> if populated
|-
|-
| Isolated startup did not finish
| Update preparation fails or isolated startup does not finish
| smoke.log, capture.log if generated; launcher.log and lumiose-launch.log
| <code>smoke.log</code>, <code>capture.log</code> if available; <code>lumiose-launch.log</code> and <code>launcher.log</code>
|-
|-
| Game import fails
| Game crashes during startup or gameplay
| launcher.log and relevant import error messages
| Matching <code>crash-*.log</code>, <code>play.log</code> or <code>play-anterior.log</code>
|-
|-
| Multiplayer connection fails
| Graphics, driver, or performance issue
| play.log or play-anterior.log, lumiose-launch.log if relevant, and exact connection error messages
| <code>play.log</code> or <code>play-anterior.log</code>, GPU and driver information, graphics settings
|-
|-
| Performance problems
| Multiplayer connection issue
| Relevant gameplay log, hardware specifications, and graphics settings
| Relevant gameplay log, exact connection error, and <code>lumiose-launch.log</code> if startup is affected
|}
|}


These recommendations apply primarily to the Windows standalone launcher. Collect files whose timestamps correspond to the issue; file availability varies by failure and version.
These recommendations apply primarily to Windows ZA Recomp installations. Check timestamps, file contents, and whether the failure occurred before or after game initialization.


== Other Platforms ==
== Other Platforms ==

Latest revision as of 07:16, 14 November 2026


LumiWiki › Main Page › Logs & Diagnostics

Welcome to the Lumiose Online diagnostic documentation.

This page explains how to locate and collect diagnostic information when troubleshooting installation failures, launcher errors, game crashes, multiplayer connectivity problems, and other technical issues.

Diagnostic logs help the development team identify where a failure occurred and determine which components may be responsible.


Platform Differences
The diagnostic files and locations described below are primarily associated with the Windows standalone launcher (ZA Recomp). Other platforms may generate different logs or use different diagnostic methods.

Supported Platforms

Lumiose Online supports four installation methods:

Platform Installation Method Diagnostic Information
Windows ZA Recomp (Native) Launcher, gameplay, update preparation, and crash diagnostics
macOS MonZaMac (Native) Platform-specific diagnostic information
PC Eden Emulator Emulator and mod-related diagnostics
Nintendo Switch Atmosphère Platform-specific diagnostic information

The availability and location of diagnostic logs depend on the platform, application version, and type of failure.

Windows Standalone Launcher (ZA Recomp)

The Windows standalone launcher can generate diagnostic files during game preparation, update installation, and normal execution.

Some logs are stored in persistent directories, while others are generated in temporary working directories.

Diagnostic Log Reference

The Windows standalone installation maintains several diagnostic logs. The descriptions below are based on examined ZA Recomp and Lumiose Online logs; file availability and contents may vary by release.

Log File Recorded Information Recommended Use
launcher.log A timestamped history of launcher runs, game import, game-code generation and compilation, update notices, and other launcher operations. Import failures, compilation errors, updates, and launcher startup issues
lumiose-launch.log Lumiose launcher startup, initial setup requirements, game-code revision checks, preparation of bundled Lumiose builds, and update checks. Lumiose-specific setup, preparation, and launch failures
play.log Detailed game execution information, including ZA Recomp version, CPU, RAM, graphics device and Vulkan driver, rendering configuration, game initialization, and runtime events. Gameplay, startup, rendering, and performance issues
play-anterior.log An additional retained runtime log containing the same kinds of execution details as play.log. The exact rotation mechanism has not been verified. When play.log is empty or does not describe the affected run
crash-YYYYMMDD-HHMMSS.log Timestamped crash-related runtime diagnostics, which may include exception codes, fault addresses, and backtraces alongside preceding execution output. Unexpected termination, access violations, and crash investigation
smoke.log Detailed game initialization and execution output from an isolated startup check performed during Lumiose preparation. Update preparation failures and “Isolated startup did not finish” errors
capture.log Detailed game initialization and execution output associated with an isolated capture/preparation stage. Preparation and capture-stage failures, especially alongside smoke.log

The first five log patterns have been observed in the main logs directory. The smoke.log and capture.log examples were collected from temporary update-preparation working directories. Not every failure produces every log.

Finding the Main Log Directory

Open the folder containing lasrecomp.exe, then open logs.

Example: D:\Games\Switch\ZA Recomp\logs\

Use file modification times to identify the logs associated with the incident. Some files contain records from multiple launches, and a log may be empty.

launcher.log

The launcher.log file contains timestamped records of ZA Recomp launcher activity across multiple runs. Examined examples include:

  • The ZA Recomp version, operating system, CPU, and available disk space
  • Game package import and update application results
  • Game-code generation and compilation, including compiled object counts and elapsed time
  • Launcher update availability and other startup operations

This is a useful first log for problems occurring before gameplay begins, particularly game import and compilation failures.

Location: <ZA Recomp installation folder>\logs\launcher.log

lumiose-launch.log

The lumiose-launch.log file records Lumiose-specific launcher preparation. Examined entries include whether initial setup or a game-code revision check is required, preparation of the bundled Lumiose build, checking active builds and updates, and completion of preparation.

Collect this file when Lumiose Online fails to prepare or launch, particularly if ZA Recomp itself otherwise starts normally. It can be helpful alongside launcher.log.

Location: <ZA Recomp installation folder>\logs\lumiose-launch.log

play.log and play-anterior.log

play.log records detailed game execution. The examined logs include:

  • ZA Recomp version, Windows version, CPU capabilities, and memory
  • GPU identification, Vulkan API and graphics driver information
  • Rendering settings, resolution, shader pipeline and cache messages
  • Game-code loading, initialization, and runtime events
  • Warnings and errors associated with graphics drivers or game execution

For example, an examined gameplay log reported that an AMD graphics driver compiler crashed while processing certain pipelines. Such entries can be useful when investigating graphical problems, although a warning alone does not establish the cause of a reported failure.

Locations:

  • <ZA Recomp installation folder>\logs\play.log
  • <ZA Recomp installation folder>\logs\play-anterior.log

play-anterior.log has been observed containing substantial runtime output while play.log was empty. Inspect both files and compare their modification times before selecting the log to send.


Log Retention Not Yet Verified
The examined files establish that play-anterior.log can contain retained gameplay diagnostics, but do not conclusively establish when it is created, replaced, or rotated. Do not assume it always contains the immediately preceding session.

Timestamped crash logs

Crash logs have been observed under the pattern:

crash-YYYYMMDD-HHMMSS.log

Example: crash-20261108-164732.log

These logs may contain detailed execution context as well as crash-specific information such as exception codes, memory addresses, and host backtraces. For example, 0xC0000005 denotes an access violation, but does not by itself identify its root cause.

Location: <ZA Recomp installation folder>\logs\

When reporting a crash, select the timestamped file corresponding to the incident and include the relevant gameplay log if available. Do not send unrelated historical crash logs unless requested.

smoke.log and capture.log

These logs have been observed during Lumiose update preparation and isolated execution checks. Both can contain detailed game initialization traces rather than merely a short summary of the operation.

  • smoke.log: An examined example records an isolated game startup with initialization, service calls, loaded game code, and Lumiose-related execution information.
  • capture.log: An examined example records initialization and execution activity in an isolated capture/preparation environment.

Both are especially useful when the launcher reports “Update preparation failed” or “Isolated startup did not finish”. Their precise division of responsibility within the preparation pipeline still requires confirmation from project source code.

Observed directory pattern:

<ZA Recomp installation folder>\lumiose\update-work\initial-*\

The initial-* directory has a variable suffix. Search it for smoke.log and capture.log if present.

How to collect temporary preparation logs:

  1. Open the folder containing lasrecomp.exe.
  2. Navigate to lumiose\update-work.
  3. Look for a directory beginning with initial-.
  4. Copy smoke.log and capture.log, if present, to a safe location before retrying.
  5. Include the exact launcher error message when submitting the files.


Preserve Temporary Logs
Update-preparation working directories may be cleaned up after a successful attempt. Collect any available logs before retrying or reinstalling, because the relevant files may become unavailable.

Finding Logs with PowerShell

Windows users can search their ZA Recomp installation for the relevant files. Replace the example path with the actual installation folder: 

Get-ChildItem -Path "C:\Games\ZA Recomp" -Recurse -File -ErrorAction SilentlyContinue |
Where-Object {
    $_.Name -in @("launcher.log", "lumiose-launch.log", "play.log", "play-anterior.log", "smoke.log", "capture.log") -or
    $_.Name -like "crash-*.log" -or
    $_.Name -eq "crash.log"
} |
Select-Object Name, FullName, LastWriteTime, Length |
Sort-Object LastWriteTime -Descending

This command only lists matching files, their locations, modification times, and sizes; it does not modify them. A missing temporary log does not necessarily indicate an installation problem.

Which Logs Should I Collect?

Problem Recommended Logs
Game import or code compilation fails launcher.log, exact error message
Lumiose preparation or launch fails lumiose-launch.log, launcher.log, play.log if populated
Update preparation fails or isolated startup does not finish smoke.log, capture.log if available; lumiose-launch.log and launcher.log
Game crashes during startup or gameplay Matching crash-*.log, play.log or play-anterior.log
Graphics, driver, or performance issue play.log or play-anterior.log, GPU and driver information, graphics settings
Multiplayer connection issue Relevant gameplay log, exact connection error, and lumiose-launch.log if startup is affected

These recommendations apply primarily to Windows ZA Recomp installations. Check timestamps, file contents, and whether the failure occurred before or after game initialization.

Other Platforms

MonZaMac (macOS)

MonZaMac provides a native macOS implementation of Pokémon Legends: Z-A.

Diagnostic information may differ from the Windows launcher.

When reporting a problem, provide:

  • macOS version
  • Mac model and Apple Silicon chip
  • MonZaMac release version
  • Exact error messages
  • Available application logs or crash reports

Eden Emulator (PC)

Eden uses its own emulation environment and diagnostic facilities.

When reporting a Lumiose Online issue while using Eden, provide:

  • Eden version
  • Operating system
  • Pokémon Legends: Z-A game version
  • Lumiose Online mod version
  • Exact error messages
  • Relevant diagnostic information, if available


Emulator Support
Problems originating from the emulator itself may require assistance from the Eden development or support community rather than the Lumiose Online development team.

Nintendo Switch (Atmosphère)

Nintendo Switch installations use Atmosphère custom firmware.

When reporting an issue, provide:

  • Console model
  • System firmware version
  • Atmosphère version
  • Pokémon Legends: Z-A game version
  • Lumiose Online mod version
  • Exact error messages
  • Available diagnostic information

Problems originating from Atmosphère or the console environment may fall outside the scope of Lumiose Online support.

Collecting Diagnostic Logs

When troubleshooting an issue:

  1. Reproduce the problem, if possible.
  2. Record the exact error message.
  3. Locate the relevant diagnostic files and check their modification times.
  4. If update preparation failed, copy any temporary logs before retrying.
  5. Close the game or launcher when appropriate.
  6. Preserve the logs associated with the affected session. If play.log is empty, check play-anterior.log.
  7. Review the files for sensitive information.
  8. Attach the relevant logs when requesting support.


Preserve Logs Before Retrying
Avoid deleting or overwriting diagnostic logs until you have collected the files associated with the failure. Reinstalling, retrying updates, or repeatedly relaunching the application may make the original diagnostic information unavailable.

Protecting Sensitive Information

Diagnostic logs may contain system or environment information.

Before sharing them publicly, review the contents for:

  • Windows or macOS usernames
  • Local file paths
  • Public IP addresses
  • Authentication tokens or credentials
  • Other personally identifiable information

Remove sensitive values where necessary while preserving the surrounding diagnostic information.

Do not post private keys, passwords, or authentication tokens in public support channels.

Reporting an Issue

When requesting technical assistance, provide the following information:

  • Platform: Windows standalone, MonZaMac, Eden, or Nintendo Switch
  • Operating system: OS name and version
  • Game version: Installed Pokémon Legends: Z-A version
  • Lumiose Online version: Installed mod or launcher version
  • Hardware: CPU, GPU, and RAM, where applicable
  • Problem: Description of the failure
  • Reproduction steps: Actions required to trigger the problem
  • Error message: Exact text or screenshot
  • Diagnostic logs: Relevant files associated with the failure

If the problem occurs consistently, explain whether it happens every time or only under certain conditions.

For assistance, visit the official Lumiose Online Discord:

Lumiose Online Discord

Retrieved from "https://lumiwiki.tail2118a8.ts.net/index.php?title=Logs_%26_Diagnostics&oldid=169"