Rebrand as GME (#37)

* Move mod files to addons/GME

* Add github templates

* Add editorconfig and gitattributes

* Add stringtable to gitattributes

* Add authors list

* Change prefixes and file names to GME

* Update readme

* Update logo

* Fix paths in readme

* Change version shield label

* Update AUTHORS.txt

Co-authored-by: Crowdedlight <[email protected]>

* Mention Odin in README.md

* Update list of features

Saving/loading only works on PC for MP

---------

Co-authored-by: Crowdedlight <[email protected]>

.editorconfig

@@ -0,0 +1,20 @@
+root = true
+
+[*]
+end_of_line = lf
+insert_final_newline = true
+charset = utf-8
+indent_style = space
+indent_size = 4
+trim_trailing_whitespace = true
+
+[*.md]
+trim_trailing_whitespace = false
+
+[*.yml]
+indent_style = space
+indent_size = 2
+
+[Makefile]
+indent_style = tab
+indent_size = 4

.gitattributes

@@ -0,0 +1,14 @@
+* text=auto
+*.png binary
+*.jpg binary
+*.edds binary
+
+# Change GitHub language categorization
+addons/**/*.c linguist-language=EnforceScript
+addons/**/*.st linguist-language=Stringtable
+
+optionals/**/*.c linguist-language=EnforceScript
+optionals/**/*.st linguist-language=Stringtable
+
+# Do not count extras in language usage stats
+extras/* linguist-vendored

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,55 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+---
+
+<!--
+🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨
+
+I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
+1. If I delete this entire template or parts of it and go my own path, the team may close my issue without further explanation or engagement.
+2. If I list multiple bugs/concerns in this one issue, the team may close my issue without further explanation or engagement.
+3. If I write an issue that has duplicates, the team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
+4. If I leave the title incomplete when filing the issue, the team may close my issue without further explanation or engagement.
+5. If I file something completely blank in the body, the team may close my issue without further explanation or engagement.
+6. If I file an issue without collecting logs (console.log file, etc...), the team may close my issue without further explanation or engagement. 
+
+All good? Then proceed and fill out all items below.
+-->
+
+**Arma Reforger Version:** `1.x.x.x` (stable / experimental)
+**GME Version:** `1.x.x`
+<!-- Make sure to reproduce the issue with only GME on a official Game Master scenario! -->
+
+**Mods:**
+```
+- GME
+```
+
+**Description:**
+Add a detailed description of the error. This makes it easier for us to fix the issue.
+
+**Expected behavior:**
+A clear and concise description of what you expected to happen.
+
+**Steps to reproduce:**
+Add the steps needed to reproduce the issue.
+
+1. _Go to ..._
+2. _Click ..._
+3. _See ..._
+
+**Where did the issue occur?**
+- Dedicated / Self-Hosted Multiplayer / Singleplayer / Workbench
+
+**Additional information:**
+Provide any additional information that will help us solve this issue.
+
+**console.log file:**
+- Add a link ([gist](https://gist.github.com) or [pastebin](http://pastebin.com)) to the client and/or server `console.log` file. An instruction to find your log files can be found [here](https://community.bistudio.com/wiki/Arma_Reforger:Crash_Report).
+
+**Screenshots:**
+If applicable, add screenshots to help explain your problem.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/enhancement-request.md

@@ -0,0 +1,32 @@
+---
+name: Enhancement request
+about: Suggest an improvement for this project
+title: ''
+labels: enhancement
+assignees: ''
+---
+
+<!--
+🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨
+
+I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
+1. If I delete this entire template or parts of it and go my own path, the team may close my issue without further explanation or engagement.
+2. If I list multiple features in this one issue, the team may close my issue without further explanation or engagement.
+3. If I write an issue that has duplicates, the team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
+4. If I leave the title incomplete when filing the issue, the team may close my issue without further explanation or engagement.
+5. If I file something completely blank in the body, the team may close my issue without further explanation or engagement.
+
+All good? Then proceed and fill out all items below.
+-->
+
+**Is your enhancement related to a problem?**
+A clear and concise description of what the enhancement entails. Ex. [...] would improve user experience.
+
+**Solution you'd like:**
+A clear and concise description of what you want to happen.
+
+**Alternatives you've considered:**
+A clear and concise description of any alternative solutions or ideas you've considered.
+
+**Additional context:**
+Add any other context or screenshots about the enhancement here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,32 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: feature
+assignees: ''
+---
+
+<!--
+🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨
+
+I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
+1. If I delete this entire template or parts of it and go my own path, the team may close my issue without further explanation or engagement.
+2. If I list multiple features in this one issue, the team may close my issue without further explanation or engagement.
+3. If I write an issue that has duplicates, the team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
+4. If I leave the title incomplete when filing the issue, the team may close my issue without further explanation or engagement.
+5. If I file something completely blank in the body, the team may close my issue without further explanation or engagement.
+
+All good? Then proceed and fill out all items below.
+-->
+
+**Is your feature request related to a problem?**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Solution you'd like:**
+A clear and concise description of what you want to happen.
+
+**Alternatives you've considered:**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context:**
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/other.md

@@ -0,0 +1,19 @@
+---
+name: Other
+about: Create an issue for something else (task, question)
+title: ''
+labels: ''
+assignees: ''
+---
+
+<!--
+🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨
+
+I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
+1. If I post this blank issue that should have followed any of the premade templates, the team may close my issue without further explanation or engagement.
+2. If I write an issue that has duplicates, the team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
+3. If I leave the title incomplete when filing the issue, the team may close my issue without further explanation or engagement.
+4. If I post only one sentence without further context, the team may close my issue without further explanation or engagement.
+
+All good? Then proceed and fill out all items below.
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,4 @@
+**When merged this pull request will:**
+- Describe what this pull request will do
+- Each change in a separate line
+- Include documentation if applicable

.github/release.yml

@@ -0,0 +1,21 @@
+changelog:
+  categories:
+    - title: '**ADDED:**'
+      labels:
+        - 'feature'
+    - title: '**IMPROVED:**'
+      labels:
+        - 'enhancement'
+        - 'optimization'
+    - title: '**CHANGED:**'
+      labels:
+        - 'cleanup'
+    - title: '**FIXED:**'
+      labels:
+        - 'bug fix'
+    - title: '**TRANSLATIONS:**'
+      labels:
+        - 'translation'
+  exclude:
+    labels:
+      - 'ignore changelog'

AUTHORS.txt

@@ -0,0 +1,12 @@
+# GAME MASTER ENHANCED CONTRIBUTOR LIST
+# If you contributed, but are not listed here,
+# contact one of the Core Team members.
+#
+# Feel free to add yourself to this when creating a pull
+# request, preferably including an email address.
+
+# CORE TEAM
+Crowdedlight <[email protected]>
+Kexanone <[email protected]>
+
+# CONTRIBUTORS