chore: remove legacy CI flag and upstream contribution leftovers

.github/workflows/build.yml

@@ -27,9 +27,9 @@ jobs:
           if [[ "$GITHUB_EVENT_NAME" == "pull_request" ]]; then
             dev_version="DEV-$(date -u +%Y%m%d-%H%M)"
           fi
-          mvn -B --no-transfer-progress -P'!deploy-live' org.codehaus.mojo:versions-maven-plugin:2.22.0:set \
+          mvn -B --no-transfer-progress org.codehaus.mojo:versions-maven-plugin:2.22.0:set \
             -DnewVersion="$dev_version" -DgenerateBackupPoms=false
-          mvn -B --no-transfer-progress -P'!deploy-live' help:evaluate \
+          mvn -B --no-transfer-progress help:evaluate \
             -Dexpression=project.build.finalName -Doutput="$RUNNER_TEMP/final-name"
           final_name=$(cat "$RUNNER_TEMP/final-name")
           [[ "$final_name" =~ ^[A-Za-z0-9][A-Za-z0-9._-]*$ ]] || exit 1
@@ -38,7 +38,7 @@ jobs:
           echo "jar=target/$final_name.jar" >> "$GITHUB_OUTPUT"
 
       - name: Run unit tests and build
-        run: mvn -B --no-transfer-progress -P'!deploy-live' clean verify -DskipTests=false -Dmaven.test.skip=false
+        run: mvn -B --no-transfer-progress clean verify -DskipTests=false -Dmaven.test.skip=false
 
       - name: Verify runtime JAR
         env:

.github/workflows/maven-release.yml

@@ -59,14 +59,14 @@ jobs:
         env:
           TAG: ${{ github.ref_name }}
         run: |
-          mvn -B --no-transfer-progress -P'!deploy-live' org.codehaus.mojo:versions-maven-plugin:2.22.0:set \
+          mvn -B --no-transfer-progress org.codehaus.mojo:versions-maven-plugin:2.22.0:set \
             -DnewVersion="${TAG#v}" -DgenerateBackupPoms=false
-          mvn -B --no-transfer-progress -P'!deploy-live' help:evaluate \
+          mvn -B --no-transfer-progress help:evaluate \
             -Dexpression=project.build.finalName -Doutput="$RUNNER_TEMP/final-name"
           final_name=$(cat "$RUNNER_TEMP/final-name")
           [[ "$final_name" =~ ^[A-Za-z0-9][A-Za-z0-9._-]*$ ]] || exit 1
           echo "jar=target/$final_name.jar" >> "$GITHUB_OUTPUT"
-          mvn -B --no-transfer-progress -P'!deploy-live' clean verify -DskipTests=false -Dmaven.test.skip=false
+          mvn -B --no-transfer-progress clean verify -DskipTests=false -Dmaven.test.skip=false
 
       - name: Stage only the release JAR
         env:

CONTRIBUTING.md

@@ -1,7 +1,8 @@
 # Contributing
 
+This is the TFMC fork of [PlayPro/CoreProtect](https://github.com/PlayPro/CoreProtect).
 When contributing to this repository, please first discuss the change you wish to make via issue,
-on Discord, or any other method with the owners of this repository before making a change. 
+on the [TFMC Discord](https://discord.gg/tfmc), or any other method with the owners of this repository before making a change.
 
 Please note we have a code of conduct, please follow it in all your interactions with the project.
 
@@ -11,9 +12,9 @@ Please note we have a code of conduct, please follow it in all your interactions
 - Use descriptiveCamelCase for variable/method names. Names containing underscore or abbreviations should be changed.
 - Restrict changes in a commit to a single event or section of code (e.g. refactor BlockBreakEvent and BlockPlaceEvent in separate commits)
 - Attempt to keep the amount of code modified in a single pull request small and readable. 
-- Please utilize [SonarLint](https://www.sonarlint.org) in your IDE. Contributions are automatically analyzed.
+- Please utilize [SonarLint](https://www.sonarlint.org) in your IDE.
 - When adding new functionality, please also be sure to update the documentation as well.
-- Use common sense. If you have a suggestion for a contribution guideline, post it on Discord.
+- Use common sense. If you have a suggestion for a contribution guideline, open an issue.
 
 Please note that although numerous improvements have been made to the codebase over the past few years, there’s still significant work to be done. Parts of this plugin are over a decade old, and new functionality is continuously being added. Refactoring is welcomed, but please be sure to keep commits a reasonable size.
 
@@ -78,8 +79,8 @@ representative at an online or offline event.
 ### Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement on our Discord server, at
-[discord.gg/b4DZ4jy](https://discord.gg/b4DZ4jy).
+reported to the community leaders responsible for enforcement on the TFMC Discord server, at
+[discord.gg/tfmc](https://discord.gg/tfmc).
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the