Version Bump: 1.17

.github/CONTRIBUTING.MD

@@ -0,0 +1,49 @@
+## Contributing to ArmorStandEditor
+
+We are happy that you are willing to contribute. Usually, we are very lenient with all PRs, but there are still some guidelines you can follow to make the approval process go smoother.
+
+- Do you run a server and have experience in Development? Take a look at our ["Help Wanted"](https://github.com/Wolfieheart/ArmorStandEditor/labels/help%20wanted) and ["BUG-0: Pending Investigation"](https://github.com/Wolfieheart/ArmorStandEditor/labels/BUG-0%3A%20Pending%20Investigation) Issues,  where you can find issues that need extra testing and investigation.
+- Do you speak multiple languages? If so, we always welcome contributions for our Language Files/Translations
+
+## Contributing Code?
+Code Contributions are always welcomed and are made via GitHub's Pull Request System. Make a Personal Fork of the ArmorStandEditor repository (this) and open it in your IDE of Choice.
+You can ask for any information/help on your idea/contribution to the [ASE Discord](https://discord.com/invite/aUf4AWAKmr) in the #development channel.
+
+- Please make sure to read our [License](https://github.com/Wolfieheart/ArmorStandEditor/blob/master/LICENSE.md) before contributing.  If you do not agree with the terms and conditions of our license, please do not contribute any code.
+- By making a pull request, you represent that you have the right to waive copyright and related rights to your contribution, and agree that all copyright and related rights in your contributions are waived, and you acknowledge that we have the copyright to use and modify your contribution under our [License](https://github.com/Wolfieheart/ArmorStandEditor/blob/master/LICENSE.md) for perpetuity.
+
+## Making Any Changes
+- Create a personal fork (not an org fork) of the ArmorStandEditor repository (this).
+    - Name your branch something relevant (i.e: /dev/\<Version Here>/\<Feature Name Here>)
+    - Work off the Development Branch unless already Merged into Main - This will therefore allow Developments to be merged together to 1 big branch
+    - To create a branch in Git;
+        - `git branch relevantBranchName`
+        - Then checkout the new branch with `git checkout relevantBranchName`
+    - Check for unnecessary whitespace with `git diff --check` before committing.
+    - Please follow the below for Commits:
+      - `[CORE]` annotation for New Features, Bug Fixes, Performance Improvements etc.
+      - `[CI]` annotation for changes related to Continuous Integration
+      - `[DOC]` annotation for Documenting - Either code or fixing the wiki
+      - `[LANG]` annotation for new languages/updated translations
+      - `[MISC]` annotation for anything that does not fit the above requirements
+
+## Code requirements
+- You must use Tabs (Size 4 Spaces).
+- Keep your environment in Java 17. GitHub handles building all of this into Java 17 and 18, but keep in mind that, while you will be able to use modern language features that way (like patterns), some standard library methods added after jdk 11 (the minimum supported version: 55.0 for certain plugins) will not work and cause "cannot find symbol" errors when building (like String.isBlank).
+- Avoid Wildcard Imports (Preferred, but is allowed. Let me know if this can't be avoided on Discord.)
+- Don't run IDE Formatters over entire class files, unless it's a new class-file you're implementing
+    - This is done to avoid us changing the lines everytime, each IDE is different, so we don't have a constant here and there.
+    - This also keeps file compares on GitHub simple.
+- Reflection should be a last resort.
+- Do not use NMS or CraftBukkit Code. Bukkit/Spigot API calls only.
+
+
+## Contributing translations
+Translations of ArmorStandEditor's Base Language File [English (US)](https://github.com/Wolfieheart/ArmorStandEditor/blob/master/src/main/resources/lang/en_US.yml) are welcomed and can be done following the Code Guidelines outlined above.
+
+- Do not work on the en_US.yml base file, this gets overwritten when the plugin gets enabled. Please create a new language file
+- Language files are stored in `resources/lang/<name_Here>.yml` 
+  - Usually Name_Here points to Language Code and Land Code (ex: nl_BE.yml). 
+  - Examples can be found [here](https://www.fincher.org/Utilities/CountryLanguageList.shtml).
+- Change the formatting codes at the start of a file as desired.
+- Please add your language/translation on the Discord, so we know that you added it. We will handle the rest by working off your branch such as adding it to the Metrics tool and adding it to the update routine.

.github/ISSUE_TEMPLATE/behaviour-bug.yml

@@ -0,0 +1,55 @@
+name: Behavior Bug or other issue
+description: Report issues with the plugin or other behavior related issues.
+labels: ["bug", "BUG-0: Pending Investigation"]
+title: "[Bug]: "
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Before reporting a crash here, please make sure you are on the latest version of the Plugin.
+        Forks of the plugin receive no support here. If you are using a fork, please make sure that this issue also happens when using the latest release.
+
+  - type: textarea
+    attributes:
+      label: Expected behavior
+      description: What you expected to see.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Observed/Actual behavior
+      description: What you actually saw.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Steps/models to reproduce
+      description: This may include a build schematic, a video, or detailed instructions to help reconstruct the issue.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Plugin list
+      description: All plugins running on the server.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Plugin Version
+      description: What version of the Plugin are you using for this? As of 1.18, you can get this via /ase version.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Server Version
+      description: What Server Backend are you using? Put your output of /version ingame here
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Other
+      description: |
+        Please include other helpful information below.
+        The more information we receive, the quicker and more effective we can be at finding the solution to the issue.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -0,0 +1,46 @@
+name: Feature Request
+description: Suggest an idea for ArmorStandEditor
+labels: ["NF-0: Pending Investigation"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for filling out a feature request for ArmorStandEditor! Please be as detailed as possible so that we may consider and review the request easier.
+        We ask that you search all the issues to avoid a duplicate feature request. If one exists, please reply if you have anything to add.
+
+  - type: textarea
+    attributes:
+      label: Is your feature request related to a problem?
+      description: Please give some context for this request. Why do you want it added?
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe the solution you'd like.
+      description: A clear and concise description of what you want.
+    validations:
+      required: true
+  - type: textarea
+    attributes:
+      label: Describe alternatives you've considered.
+      description: List any alternatives you might have tried to get the feature you want.
+    validations:
+      required: true
+
+  - type: checkboxes
+    attributes:
+      label: Agreements
+      description: Please agree to the following. Failure to check these will result in your issue being marked CLOSED and INVALID.
+      options:
+        - label: I have searched for and ensured there isn't already an open issue regarding this.
+          required: true
+        - label: I have ensured the feature I'm requesting isn't already in the latest ArmorStandEditor Build.
+          required: true
+
+
+  - type: textarea
+    attributes:
+      label: Other
+      description: Add any other context or screenshots about the feature request below.
+    validations:
+      required: false

.github/dependabot.yml

@@ -0,0 +1,18 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://help.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+version: 2
+updates:
+  # Maintain dependencies for GitHub Actions
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+
+  # Maintain dependencies for maven
+  - package-ecosystem: "maven"
+    directory: "/"
+    schedule:
+      interval: "weekly"

.github/pull_request_template.md

@@ -0,0 +1,32 @@
+<!--- Welcome! It looks like you're opening a pull request for the ArmorStandEditor project, we think that's great. This form is pre-populated with a Contributor License Agreement, which is required if you want to contribute your code. It is there to protect your copyright over the code but also to protect ArmorStandEditor, making your code available to us to use indefinitely. --->
+#### Description:
+<!--- Describe your Pull Request's purpose here please. --->
+
+----
+### [CORE] Changes
+*Changes to the core of the plugin - Performance Fixes, Bug Fixes, New Features, New Permission Nodes, New Config Options etc.* 
+<!---- List your changes under this in a bullet point list --->
+
+
+
+----
+### [CI] Changes
+*Changes relating to the Continuous Integration of other Plugin APIs, Github Workflows, Issue Templates etc.*
+<!---- List your changes under this in a bullet point list --->
+
+----
+### [DOC] Changes
+*Changes relating to plugin Documentation - See the Wiki for more info*
+<!---- List your changes under this in a bullet point list --->
+
+----
+### [MISC] Changes
+*Changes that does not fit in the above list*
+<!---- List your changes under this in a bullet point list --->
+
+
+____
+- [ ] I have tested this pull request for defects on a server.
+<!--- Place x between [ ] if you have tested this code on a server. --->
+
+By making this pull request, I represent that I have the right to waive copyright and related rights to my contribution, and agree that all copyright and related rights in my contributions are waived, and I acknowledge that the ArmorStandEditor Project Owners have the copyright to use and modify my contribution under the ArmorStandEditor [License](https://github.com/Wolfieheart/ArmorStandEditor/blob/master/LICENSE.md) for perpetuity.

.github/stale.yml

@@ -0,0 +1,19 @@
+daysUntilStale: 60
+daysUntilClose: 7
+exemptLabels:
+  - "Build: Devel"
+  - "bug"
+  - "NF-0: Accepted"
+  - "NF-2: Implementation - In Progress"
+  - "NF-4: Rebase Required"
+  - "BUG-1: Reproduced"
+  - "Work in Progress"
+staleLabel: "Stale"
+markComment: >
+  This issue has been automatically marked as stale because it has not had
+  recent activity. It will be closed if no further activity occurs. Thank you
+  for your contributions.
+closeComment: >
+  This issue has been automatically closed because it has not had activity in
+  a long time. If the issue still applies to the most recent supported
+  version, please open a new issue referencing this original issue.

.github/workflows/maven-publish.yml

@@ -0,0 +1,63 @@
+# This workflow will build a Java project with Maven
+# For more information see: https://help.github.com/actions/language-and-framework-guides/building-and-testing-java-with-maven
+
+name: Java CI with Maven
+on: [push, pull_request]
+
+jobs:
+  compile:
+    if: "!contains(github.event.head_commit.message, 'ci-skip') || !contains(github.event.head_commit.message, 'CI-SKIP') || !contains(github.event.head_commit.message, 'CI SKIP') || !contains(github.event.head_commit.message, 'ci skip') "
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        java: ['21']
+    steps:
+      # 1. Check out the current working tree
+      - name: Checkout ArmorStandEditor Repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0  # Shallow clones should be disabled for a better relevancy of analysis
+
+      # 2. Setup Java JDK
+      - name: Set up JDK Environments
+        uses: actions/setup-java@v4
+        with:
+          java-version: ${{ matrix.java }}
+          distribution: 'zulu'
+
+      # 3. Setup local Maven package cache to speed up building
+      - name: Cache SonarCloud packages
+        uses: actions/cache@v4
+        with:
+          path: ~/.sonar/cache
+          key: ${{ runner.os }}-sonar
+          restore-keys: ${{ runner.os }}-sonar
+
+      - name: Cache Maven packages
+        uses: actions/cache@v4
+        with:
+          path: ~/.m2
+          key: ${{ runner.os }}-m2-${{ hashFiles('**/pom.xml') }}
+          restore-keys: ${{ runner.os }}-m2
+
+      # 4. Build via Maven
+      - name: Build and analyze
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}  # Needed to get PR information, if any
+          SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
+        run: mvn -B verify org.sonarsource.scanner.maven:sonar-maven-plugin:sonar -Dsonar.projectKey=wolfieheart_ArmorStandEditor
+
+      #5: Create a Clean Package - and Verify it
+      - name: Clean package
+        run: mvn -B clean package
+
+      - name: Clean Verify
+        run: mvn -B clean verify
+
+      #6 Upload Artifacts (Debug Purposes)
+      - name: Upload Artifact for Debugging
+        uses: actions/upload-artifact@v4.5.0
+        with:
+          name: artifact
+          path: /home/runner/work/ArmorStandEditor/ArmorStandEditor/target/armorstandeditor-*-*.jar
+          if-no-files-found: error