From 0a335d342a9c2b62d2e2417782ef6715d19eb2b5 Mon Sep 17 00:00:00 2001 From: Raffson Date: Sun, 25 Sep 2022 19:11:50 +0200 Subject: [PATCH] Update Issue templates --- .github/ISSUE_TEMPLATE/bug-report.yml | 25 +++++++++++++------------ .github/ISSUE_TEMPLATE/new-game-bug.yml | 17 +++++++++-------- 2 files changed, 22 insertions(+), 20 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml index 6b2a1881..d43be14b 100644 --- a/.github/ISSUE_TEMPLATE/bug-report.yml +++ b/.github/ISSUE_TEMPLATE/bug-report.yml @@ -17,7 +17,7 @@ body: label: Affected versions multiple: true description: > - Select all DCS Liberation versions in which you have observed this bug. + Select all DCS Retribution 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. @@ -28,15 +28,16 @@ body: filing. - If the bug was found in a development build, select "Development build" - and provide a link to the build in the field below. + If the bug was found in a test/development build, select "Test build" or "Development build" + and provide a link to the applicable build in the field below. options: - - 5.2.0 + - 1.0.0 + - Test build - Development build - type: input attributes: - label: Development build - description: A link to the development build, if applicable. + label: Test/Development build + description: A link to the test/development build, if applicable. - type: textarea attributes: label: Description @@ -52,27 +53,27 @@ body: description: > Attach any files needed to reproduce the bug here. **A save game is required.** We typically cannot help without a save game (the - `.liberation` file found in - `%USERPROFILE%/Saved Games/DCS/Liberation/Saves`), so most bugs filed + `.retribution` file found in + `%USERPROFILE%/Saved Games/DCS/Retribution/Saves`), so most bugs filed without saved games will be closed without investigation. Other useful files to include are: - The Liberation log file. The log file is located at - `/logs/liberation.log`. The log often + The Retribution log file. The log file is located at + `/logs/retribution.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 + The `retribution_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 - `/state.json`. This file is essential for + `/state.json`. This file is essential for investigating any issues with end-of-turn results processing. diff --git a/.github/ISSUE_TEMPLATE/new-game-bug.yml b/.github/ISSUE_TEMPLATE/new-game-bug.yml index bb4ad5cf..cb548b3c 100644 --- a/.github/ISSUE_TEMPLATE/new-game-bug.yml +++ b/.github/ISSUE_TEMPLATE/new-game-bug.yml @@ -25,7 +25,7 @@ body: label: Affected versions multiple: true description: > - Select all DCS Liberation versions in which you have observed this bug. + Select all DCS Retribution 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. @@ -36,15 +36,16 @@ body: filing. - If the bug was found in a development build, select "Development build" - and provide a link to the build in the field below. + If the bug was found in a test/development build, select "Test build" or "Development build" + and provide a link to the applicable build in the field below. options: - - 5.2.0 + - 1.0.0 + - Test build - Development build - type: input attributes: - label: Development build - description: A link to the development build, if applicable. + label: Test/Development build + description: A link to the test/development build, if applicable. - type: input attributes: label: Campaign name @@ -102,8 +103,8 @@ body: attributes: label: Log file description: > - Attach the Liberation log file. The log file is located at - `/logs/liberation.log`. + Attach the Retribution log file. The log file is located at + `/logs/retribution.log`. You can attach files to the bug by dragging and dropping the file