mirror of
https://github.com/dcs-liberation/dcs_liberation.git
synced 2025-11-10 14:22:26 +00:00
94 lines
3.6 KiB
YAML
94 lines
3.6 KiB
YAML
---
|
|
name: Bug report
|
|
description: >
|
|
Use for any bug that happens after campaign generation. If the New Game wizard
|
|
failed, use the "New Game wizard failed" template instead.
|
|
labels: bug
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: >
|
|
Before filing, please search the issue tracker to see if the issue has
|
|
already been reported.
|
|
- type: dropdown
|
|
validations:
|
|
required: true
|
|
attributes:
|
|
label: Affected versions
|
|
multiple: true
|
|
description: >
|
|
Select all DCS Liberation versions in which you have observed this bug.
|
|
You do not need to test all of them, but the information is useful if
|
|
you have it.
|
|
|
|
|
|
If you do not see your version listed here you are on an old release
|
|
that is not supported, and the bug may already be fixed in a newer
|
|
release. Check that the bug still exists in a newer release before
|
|
filing.
|
|
|
|
|
|
If the bug was found in a development build, select "Development build"
|
|
and provide a link to the build in the field below.
|
|
options:
|
|
- 13.0.0
|
|
- Development build
|
|
- type: textarea
|
|
attributes:
|
|
label: Build information
|
|
description:
|
|
The build information from the Help -> Report an issue window.
|
|
- type: textarea
|
|
attributes:
|
|
label: Description
|
|
description: >
|
|
Describe the bug. What went wrong? What did you expect to happen
|
|
instead? What steps should we take to reproduce the error? If an error
|
|
dialog was shown, include the full text.
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
attributes:
|
|
label: Save game and other files (save game required, bugs without saves will be closed)
|
|
description: >
|
|
Attach any files needed to reproduce the bug here. **A save game is
|
|
required.** Even if it seems unnecessary to you, this is required.
|
|
Repro steps that are obvious to you might not be obvious to anyone
|
|
else, and it is impossible for us to know what default settings or mods
|
|
may be impacting behavior without a save game. Bugs filed without a
|
|
save game are very often not reproducible, and those waste scarce
|
|
developer time. It is **much** easier for you to attach a save game
|
|
than it is for us to recreate your save state by guessing at what you
|
|
did. As such, bug reports that do not attach a saved game will be
|
|
closed without investigation. Attach the `.liberation.zip` file found
|
|
in `%USERPROFILE%/Saved Games/DCS/Liberation/Saves`.
|
|
|
|
|
|
Other useful files to include are:
|
|
|
|
|
|
The Liberation log file. The log file is located at `<Liberation install
|
|
directory>/logs/liberation.log`. The log often includes data about
|
|
non-fatal errors that could be the root cause of the problem.
|
|
|
|
|
|
The `liberation_nextturn.miz` or a track file. This should always be
|
|
included for bugs where the mission was generated incorrectly or where
|
|
the in-game AI is misbehaving.
|
|
|
|
|
|
The `state.json` file for the most recently completed turn, located at
|
|
`<Liberation install directory>/state.json`. This file is essential for
|
|
investigating any issues with end-of-turn results processing.
|
|
|
|
|
|
If reporting an issue that occurred during or after flying the mission
|
|
in DCS, the DCS log file found in `%USERPROFILE%/Saved Games/DCS/Logs`.
|
|
|
|
|
|
You can attach files to the bug by dragging and dropping the file into
|
|
this text box. GitHub will not allow uploads of all file types, so
|
|
attach a zip of the files if needed.
|
|
validations:
|
|
required: true
|