diff --git a/.github/ISSUE_TEMPLATE/000-bug-report.yml b/.github/ISSUE_TEMPLATE/000-bug-report.yml
index a42e83e66a..09dff0852d 100644
--- a/.github/ISSUE_TEMPLATE/000-bug-report.yml
+++ b/.github/ISSUE_TEMPLATE/000-bug-report.yml
@@ -2,6 +2,22 @@ name: Bug Report
 description: Report a bug where something is not working as expected.
 labels: [ "bug" ]
 body:
+  - type: checkboxes
+    id: existing-issue
+    attributes:
+      label: Checked for existing issues
+      description: You have checked for existing reports of this issue, open or closed.
+      options:
+        - label: "I have checked for existing issues, and have found none."
+          required: true
+  - type: checkboxes
+    id: tried-latest
+    attributes:
+      label: Tested latest version
+      description: You have checked that this issue occurs on the latest version of GTCEu.
+      options:
+        - label: "I have checked that this occurs on the latest version."
+          required: true
   - type: input
     id: version
     attributes:
@@ -41,6 +57,14 @@ body:
         - "Unsure"
     validations:
       required: true
+  - type: textarea
+    id: other-mods
+    attributes:
+      label: Other Installed Mods
+      description: List all mods you have installed here, or the name of the modpack you're playing.
+      placeholder: "Example: ATM9, Embeddium, NuclearCraft Neoteric, AE2..."
+    validations:
+      required: true
   - type: textarea
     id: expected
     attributes:
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 0000000000..34fece6112
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,18 @@
+## What
+_This section describes what this PR is about. It should be a clear and concise description concerning what this PR is for, why this PR is needed, and why it should be accepted._
+_Linking an issue can be used alternatively to writing a description._
+
+## Implementation Details
+_Any implementations in this PR that should be carefully looked over, or that could/should have alternate solutions proposed._
+
+## Outcome
+_A short description of what this PR added/fixed/changed/removed._
+_For correct linking of issues please use any of the Closes/Fixes/Resolves keywords. Example: When a PR is fixing a bug use "Fixes: #number-of-bug"_
+
+## Additional Information
+_This section is for screenshots to demonstrate any GUI or rendering changes, or any other additional information that reviewers should be aware of._
+
+## Potential Compatibility Issues
+_This section is for defining possible compatibility issues. It must be used when there are API changes, item/block/material/machine changes, or recipe changes._
+
+**Please fill in as much useful information as possible. Also, please remove all unused sections, including this and the other explanations.**
\ No newline at end of file