Add launcher_log.txt support for stdout/stderr logging #1113
+19
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR implements support for
launcher_log.txt
to capture stdout and stderr from Minecraft processes, matching the behavior of the vanilla Minecraft launcher.Changes
Modified
xmcl-runtime/launch/LaunchService.ts
to:launcher_log.txt
file in the game directory when launching MinecraftImplementation Details
When a Minecraft process is launched, the launcher now:
launcher_log.txt
file is created in the game directory (instance path) using a write streamBehavior
Each new launch overwrites the previous
launcher_log.txt
file, matching vanilla Minecraft launcher behavior. This makes it easier for users and developers to debug launch issues.Fixes the issue described in #[issue_number] where the launcher was missing this standard Minecraft logging feature.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.