Jump to content

Logs & Diagnostics

From LumiWiki
Revision as of 23:16, 13 November 2026 by Guinevere (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


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

Log File Purpose Typical Use
play.log Records game execution and runtime events. Startup failures, gameplay problems, runtime errors
crash.log Records crash-related diagnostic information when generated. Application crashes, exceptions, access violations
smoke.log Records diagnostic output from isolated startup or preparation checks. Isolated startup failures, update preparation problems
capture.log Records diagnostic output associated with preparation or capture operations. Update preparation and related failures

Not every installation or failure generates all four files.

play.log

The play.log file records information about game execution.

Depending on the launcher version, it may contain:

  • ZA Recomp version information
  • Windows version
  • CPU and system information
  • Game initialization events
  • Launcher status messages
  • Runtime warnings and errors

Location (Windows standalone launcher):

<ZA Recomp installation folder>\logs\play.log

For example:

D:\Games\Switch\ZA Recomp\logs\play.log

How to locate play.log:

  1. Open the folder containing lasrecomp.exe.
  2. Open the logs directory.
  3. Locate play.log.
  4. Attach the file when requesting technical support.

When to collect:

  • The game fails to launch.
  • The game starts but encounters errors.
  • Gameplay behaves unexpectedly.
  • The launcher displays a runtime error.

When possible, reproduce the issue and collect the log from the affected session.

crash.log

The crash.log file may be generated when the game encounters a crash.

Depending on the failure, it may contain:

  • 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.

Location:

The exact location has not yet been verified. Check available diagnostic directories and provide the file if generated.

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.


Crash Investigation
When reporting a crash, include both crash.log and play.log if available. The execution log may provide context about events immediately preceding the crash.

smoke.log

The smoke.log file contains diagnostic information associated with isolated startup or update preparation checks.

This log may be relevant when the launcher reports errors such as:

  • Update preparation failed
  • Isolated startup did not finish
  • Game preparation or validation failed

Location (Windows standalone launcher):

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

The initial- directory contains a variable suffix generated during update preparation.

For example:

D:\ZA-Recomp-windows\ZA Recomp\lumiose\update-work\initial-_ql5vc3z\smoke.log

The exact directory name differs between preparation attempts.

How to locate smoke.log:

  1. Open the folder containing lasrecomp.exe.
  2. Navigate to lumiose → update-work.
  3. Look for a directory beginning with initial-.
  4. Open that directory.
  5. Locate smoke.log.
  6. Copy the file to another location before retrying the failed update.
  7. Attach the copied log when requesting technical support.


Temporary Diagnostic Files
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.

When to collect:

Collect this log when an installation or update preparation operation fails and the file is available.

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:

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

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.


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.

Open PowerShell and run the following command, replacing the example installation path with the location of your own ZA Recomp installation: 

Get-ChildItem -Path "C:\Games\ZA Recomp" -Recurse -File -ErrorAction SilentlyContinue |
Where-Object { $_.Name -in @("play.log", "crash.log", "smoke.log", "capture.log") } |
Select-Object Name, FullName

The command searches the installation directory and its subdirectories for the listed log files.

It does not modify or delete any files.


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?

Use the following table to identify the most relevant diagnostic files for a reported issue.

Problem Recommended Logs
Game fails to start play.log, crash.log if generated
Game crashes during gameplay crash.log, play.log
Update preparation fails smoke.log, capture.log if generated
Isolated startup did not finish smoke.log, capture.log if generated
Game import fails Relevant launcher or import diagnostic output
Multiplayer connection fails play.log and relevant connection error messages
Performance problems play.log, hardware specifications, and graphics settings

These recommendations apply primarily to the Windows standalone launcher.

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.
  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.
  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=150"