How to Prepare Logs for Balm Troubleshooting

Collect a useful report while keeping unrelated personal information private. Learn more about Balm Mod.

Capture the failing attempt

Reproduce the issue in the intended profile and preserve the corresponding recent log and crash report if one exists. Note the time, action and complete error message. Write down Minecraft, loader, Balm and affected mod versions. A screenshot of only the final line may omit the requirement that explains why loading stopped.

Review before sharing

Read the files for account tokens, private addresses, chat content and personal paths before posting them publicly. Remove private information while retaining the context needed to understand the error. Follow the receiving project's reporting instructions and avoid sharing unrelated backups or entire personal directories when a focused log is sufficient.

Explain a repeatable case

Describe what you expected, what happened and the smallest set of steps that reproduces it. State whether the issue also happens in a copied instance with the relevant compatible files. Include which changes preceded the failure. Check existing reports before opening a new one, and avoid assuming that the last library name mentioned in a stack trace identifies the faulty component.