Reporting a bug¶
All · 5 min · No code
If a problem is not in this section and Diagnostics did not explain it, report it. A report that lets us reproduce the problem on the shipped sample is usually fixed fastest.
Before you report¶
- Check the Troubleshooting index for your symptom.
- Try it on the shipped sample: open
Maps/L_XenoCore_Gymand see whether the same thing happens with the sample party and minions. If it does not, the difference between the sample and your content is often the answer. - Close every editor, check Task Manager that no
UnrealEditor.exeis left running, reopen the project once, and try again. Several problems on the Build and editor page come from a stale editor process.
What to include¶
| Include | Why |
|---|---|
| XenoCore version and Unreal Engine version (for example 5.8.1) | Fixes are per release. The XenoCore version is shown on the XenoCore entry in Edit › Plugins (the VersionName in XenoCore.uplugin). The build number on the title screen is your project's own version, not XenoCore's. |
| What you did, step by step | Start from opening a named map: "Open L_XenoCore_Gym, press Play, lock on to a minion, use the second Art." |
| What you expected, and what happened | One sentence each. |
| Every time, or sometimes? | And whether it also happens on the shipped sample. |
| The log | Saved/Logs/<project name>.log in the project folder (beside the .uproject) from the session where it happened. Attach the whole file; the lines that matter are often the ones before the problem. |
| What you changed | Which shipped assets you edited, and which of your own assets are involved. Name them with their folder. |
| Screenshots or a short video | Especially for animation, UI and camera problems. |
| C++ changes | If you changed or added C++, say so, and whether the problem happens without your change. |
| Crash details | If the editor crashed, the call stack from the crash window, plus the log. |
Remove anything private from logs before you send them. Logs contain file paths, which can include your Windows user name.
Where to report¶
Open an issue at github.com/baremetalrt/xenocore-dist/issues (the Support link on the XenoCore entry in Edit › Plugins goes to the same page). You need a free GitHub account.
- Search the open and closed issues first: your problem may already have an answer.
- Click New issue. Give it a title that names the symptom, for example "Companion never draws its weapon after a leader switch".
- Fill it in with everything in What to include above: the XenoCore and Unreal Engine versions, the steps from a named map, what you expected and what happened, the log, and what you changed.
- Drag the log file, screenshots or a short video into the issue to attach them. For a log too big to attach, zip it first.
Issues on that page are public. Do not post anything private, such as your licence details, your own project's unreleased content, or logs you have not checked for personal paths.
What happens next¶
We reproduce the problem on the shipped sample. If it is a template bug, the fix goes into a future release, and this Troubleshooting section gains an entry so the next person finds the answer here.