DOCUMENTATION / SUPPORT
A little help for the next step
Something in the alpha not going to plan? Start with the pack's source, exact version and the step that stopped.
A few useful checks
- Confirm the pack source, Minecraft version and exact loader release.
- For missing Discover results, check whether that catalog supports the selected filters.
- For sign-in or Play, switch to the official Minecraft Launcher and select the prepared installation.
- After an interrupted update, follow the app's recovery guidance before launching again.
Make a useful bug report
Include your alpha build/version, Windows version, pack source and exact pack version. Describe what you expected, what happened, and the smallest set of steps that reproduces it. Copy the visible error text if possible.
Share only the relevant diagnostic excerpt after reviewing it. Remove account details, access tokens, private world information and personal filesystem paths. Never send passwords or Microsoft sign-in codes. Do not post private alpha artifacts or internal project records in public channels.
Talk to us
Prefer another Matrix client? Open the owner's contact with matrix.to. These links open the chosen service; they do not automatically join a room or send a message.
Launcher, Minecraft and other logs
The inherited log pages show different diagnostic sources. Capture the relevant error text and the step that produced it. Review excerpts before sharing: logs can contain personal paths, usernames, server addresses and other private information.
The optional Collect-Diagnostics.cmd included with the alpha creates a local build/integrity report; it does not upload it or collect whole profiles/worlds. Review the result and share only what is needed. For security or account-related concerns, contact the owner privately instead of posting in a public channel.