From a0fc8778f6683015824e9ed2b8db396cb230600b Mon Sep 17 00:00:00 2001
From: negativeExponent
Date: Wed, 1 Jul 2020 11:06:48 +0800
Subject: Update custom-issue-report.md

i believe posting logs should be the norm regardless of issue:---
 .github/ISSUE_TEMPLATE/custom-issue-report.md | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/custom-issue-report.md b/.github/ISSUE_TEMPLATE/custom-issue-report.md
index a19f94f..d31f02b 100644
--- a/.github/ISSUE_TEMPLATE/custom-issue-report.md
+++ b/.github/ISSUE_TEMPLATE/custom-issue-report.md
@@ -11,18 +11,24 @@ assignees: ''
 
 If the issue also occurs in standalone PCSX-ReARMed, the upstream repo is probably a better place for it.
 
-##Description
+## Description
 
 Please describe the issue. If this is a feature request, please add [feature request] to the title of the issue report.
 
-##Steps to reproduce
+## Steps to reproduce
 
 How can we reproduce this issue? Please include all relevant steps, as well as any settings that you have changed from their default values, particularly including whether you are using the dynarec or interpreter CPU emulation.
 
-##When did the behavior start?
+## When did the behavior start?
 
 If you can bisect the issue (that is, pinpoint the exact commit that caused the problem), please do. Someone has to do it, and having this already done greatly increases the likelihood that a developer will investigate and/or fix the problem. Barring that, please state the last time it worked properly (if ever).
 
-##Your device/OS/platform/architecture
+## Your device/OS/platform/architecture
 
 Such as Android, iOS, Windows 10, Linux, x86_64, a smart toaster, etc.
+
+## Logs (enable file logging and set log levels to DEBUG for core and frontend)
+
+## Screenshots (if needed for visual confirmation)
+
+## Others (save states and/or save files nearest to the affected area, compressed)
-- 
cgit v1.2.3