Skip to content

Instantly share code, notes, and snippets.

@slash1div

slash1div/build-coreprotect.md

Last active August 5, 2025 23:57
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save slash1div/4a9eb50e74e303cdd55357e32d24589f to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save slash1div/4a9eb50e74e303cdd55357e32d24589f to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. slash1div revised this gist May 21, 2025. 1 changed file with 5 additions and 1 deletion.
    6 changes: 5 additions & 1 deletion build-coreprotect.md
    View file
    Original file line number Diff line number Diff line change
    @@ -73,8 +73,12 @@ jobs:
    java-version: 21
    distribution: temurin

    - name: Set version in pom.xml to 23.0
    run: |
    sed -i '0,/<version>.*<\/version>/s//<version>23.0<\/version>/' pom.xml
    - name: Build with branch override
    run: mvn package --file pom.xml -Dproject.branch=development
    run: mvn package --file pom.xml -Dproject.branch=master

    - name: Get correct jar
    id: jar
  2. slash1div revised this gist May 20, 2025. 1 changed file with 8 additions and 5 deletions.
    13 changes: 8 additions & 5 deletions build-coreprotect.md
    View file
    Original file line number Diff line number Diff line change
    @@ -141,12 +141,15 @@ An example of the jar file's download button location is below.

    ### 7. Delete Your Fork

    Leaving this fork can cause confusion to people looking for an actual fork of CoreProtect. To delete your fork:
    Once you've downloaded your jar file, it's a good idea to delete your fork. Leaving it up might confuse others who are searching for an actual development fork of CoreProtect.

    1. Click the settings tab at the top.
    2. Scroll all the way down to delete this repository.
    3. Click the "Delete this Repository" button.
    4. Follow all prompts to delete the repository.
    To delete your fork:

    1. Go to your forked repository on GitHub.
    2. Click the **"Settings"** tab at the top.
    3. Scroll to the bottom of the page.
    4. Click **"Delete this repository"**.
    5. Follow the prompts to confirm and permanently delete it.

    ![Delete Button Location](https://gist.github.com/user-attachments/assets/08a45fab-bcfd-4635-9de7-be90a555aaed)

  3. slash1div revised this gist May 20, 2025. 1 changed file with 21 additions and 6 deletions.
    27 changes: 21 additions & 6 deletions build-coreprotect.md
    View file
    Original file line number Diff line number Diff line change
    @@ -9,13 +9,13 @@

    ## Why This Tutorial Exists

    Starting with Minecraft version **1.21**, CoreProtect no longer provides downloads unless you build it yourself using Java and Maven. If you're not a developer, this locks the plugin behind a paywall.
    Starting with Minecraft version **1.21**, CoreProtect no longer provides downloads unless you pay for their Patreon. The plugin still remains open source, so you can build it yourself using Java and Maven. If you're not a developer, this seemingly locks the plugin behind a paywall.

    Many people have switched to alternatives like **Prism**, which don't measure up at all. This has caused small servers to suffer, with some shutting down due to griefing.
    Some people have switched to alternatives like **Prism**, which don't measure up at all. This has caused small servers to suffer. Some even shut down due to griefing, with no reliable way to trace or roll back the damage.

    This guide walks you through **how to build CoreProtect using GitHub only**. No Java knowledge, no downloads, and no B.S.
    I've subscribed to CORE’s Patreon and plan to continue supporting it, but not everyone can afford to do that, or let alone even use Patreon. Minecraft is largely played by kids and teens, not adults.

    I am not a writer, just a tech guy, so try to power through.
    This guide walks you through **how to build CoreProtect using GitHub only**. No Java knowledge, no downloads. I'm not a writer, just a tech guy doing his best, so hang in there with me. I barely know Java or Maven's basics myself.

    ---

    @@ -117,7 +117,7 @@ The build will start!
    ### 5. Open the Workflow
    1. Refresh the page to see the newest workflow at the top.
    2. Once the workflow finishes, you'll see a green checkmark.
    2. Once the workflow finishes, you'll see a green checkmark (✅).
    > Note: The workflow shouldn't take longer than 2 minutes to complete. If it is still yellow, refresh again.
    3. Click the title of the workflow to open it!
    @@ -139,10 +139,25 @@ An example of the jar file's download button location is below.

    ---

    ### 7. Delete Your Fork

    Leaving this fork can cause confusion to people looking for an actual fork of CoreProtect. To delete your fork:

    1. Click the settings tab at the top.
    2. Scroll all the way down to delete this repository.
    3. Click the "Delete this Repository" button.
    4. Follow all prompts to delete the repository.

    ![Delete Button Location](https://gist.github.com/user-attachments/assets/08a45fab-bcfd-4635-9de7-be90a555aaed)

    ---

    ## You Did It!

    You now have the **latest version of CoreProtect**, built from source without needing to understand a single line of code (or download anything!).

    If you value the plugin, support [CoreProtect's Patreon](https://www.patreon.com/CoreProtect) as it will keep future development going.

    Although this "paywalling" may seem annoying, it is necessary to keep the project going. Show some love to the developers and it might change in the future.
    Although this "paywalling" may seem annoying, it is necessary to keep the project going. Show some love to the developers and it might change in the future.

    Thank you CORE for keeping this plugin going for so long. This is extremely rare in the Minecraft community, and deserves a lot of respect. ❤️
  4. slash1div revised this gist May 20, 2025. 1 changed file with 36 additions and 36 deletions.
    72 changes: 36 additions & 36 deletions build-coreprotect.md
    View file
    Original file line number Diff line number Diff line change
    @@ -67,23 +67,33 @@ jobs:
    - name: Checkout repository
    uses: actions/checkout@v4

    - name: Set up JDK 22
    - name: Set up JDK 21
    uses: actions/setup-java@v4
    with:
    java-version: 22
    java-version: 21
    distribution: temurin

    - name: Build
    run: mvn package --file pom.xml

    - name: Get build artifact ready
    run: mkdir staging && cp target/*.jar staging

    - name: Upload a Build Artifact
    - name: Build with branch override
    run: mvn package --file pom.xml -Dproject.branch=development

    - name: Get correct jar
    id: jar
    run: |
    mkdir staging
    for file in target/*.jar; do
    if [[ "$(basename "$file")" != original-* ]]; then
    cp "$file" staging/
    echo "jar_name=$(basename "$file")" >> "$GITHUB_OUTPUT"
    break
    fi
    done
    - name: Upload the .jar directly
    uses: actions/upload-artifact@v4
    with:
    name: Custom Fork Build
    path: staging
    name: ${{ steps.jar.outputs.jar_name }}
    path: staging/${{ steps.jar.outputs.jar_name }}
    compression-level: 0
    ```
    3. Click **"Commit changes"** in the top-right corner.
    @@ -92,23 +102,7 @@ jobs:
    ---
    ### 4. Change the Branch
    1. At the top of your page, click your repo name (e.g. `CoreProtect` or `CoreProtect-Build`).
    2. In the list on the left, navigate to:
    `src/main/resources/plugin.yml`
    3. Click the **pencil icon** (✏️) in the top-right corner to edit the file.
    4. Find **line 4** and replace it with:
    ```
    branch: developement
    ```
    5. Click **"Commit changes"** in the bottom-left corner.

    ![Edited File and Commit Button](https://gist.github.com/user-attachments/assets/f3d49755-ca92-4368-ad2d-f7c2b7ba97eb)

    ---

    ### 5. Run the Build
    ### 4. Run the Build
    1. At the top of the page, click the **"Actions"** tab.
    2. In the left sidebar, click **"Custom Fork Build"**.
    @@ -120,22 +114,28 @@ The build will start!
    ---
    ### 6. Download the Finished Build
    ### 5. Open the Workflow
    1. Once the workflow finishes (you'll see a green checkmark), click the top result.
    2. Look for **"Artifacts"** and download the `.zip` file.
    1. Refresh the page to see the newest workflow at the top.
    2. Once the workflow finishes, you'll see a green checkmark.
    > Note: The workflow shouldn't take longer than 2 minutes to complete. If it is still yellow, refresh again.
    3. Click the title of the workflow to open it!
    ![Artifact Zip Location](https://gist.github.com/user-attachments/assets/079c6470-d199-4da1-92f9-ce9b30a506df)
    An example of a finished workflow is below. You will click where the arrow is.
    ![Finished Workflow](https://gist.github.com/user-attachments/assets/dba1f5dd-6c5e-44e8-bb23-83005b0e32a1)
    ---
    ### 7. Grab the Right File
    ### 6. Grab the Jar
    1. Open the zip file you downloaded.
    2. **Choose the file that does _*not*_ start with `original-`**.
    1. If the workflow is finished, you should see a jar file at the bottom of the page.
    2. Click the download button next to the jar file artifact.
    3. Upload that `.jar` file to your Minecraft server — you’re done!

    ![Zip File Overview with Proper File Circled. Improper file crossed out.](https://gist.github.com/user-attachments/assets/913ede31-5477-4f0e-9b62-41f2b2172ef6)
    An example of the jar file's download button location is below.

    ![Artifact Download Button](https://gist.github.com/user-attachments/assets/7d3056de-3267-4e49-8159-f1452195e7eb)

    ---

  5. slash1div revised this gist May 19, 2025. 1 changed file with 20 additions and 4 deletions.
    24 changes: 20 additions & 4 deletions build-coreprotect.md
    View file
    Original file line number Diff line number Diff line change
    @@ -92,7 +92,23 @@ jobs:
    ---
    ### 4. Run the Build
    ### 4. Change the Branch
    1. At the top of your page, click your repo name (e.g. `CoreProtect` or `CoreProtect-Build`).
    2. In the list on the left, navigate to:
    `src/main/resources/plugin.yml`
    3. Click the **pencil icon** (✏️) in the top-right corner to edit the file.
    4. Find **line 4** and replace it with:
    ```
    branch: developement
    ```
    5. Click **"Commit changes"** in the bottom-left corner.

    ![Edited File and Commit Button](https://gist.github.com/user-attachments/assets/f3d49755-ca92-4368-ad2d-f7c2b7ba97eb)

    ---

    ### 5. Run the Build

    1. At the top of the page, click the **"Actions"** tab.
    2. In the left sidebar, click **"Custom Fork Build"**.
    @@ -104,7 +120,7 @@ The build will start!

    ---

    ### 5. Download the Finished Build
    ### 6. Download the Finished Build

    1. Once the workflow finishes (you'll see a green checkmark), click the top result.
    2. Look for **"Artifacts"** and download the `.zip` file.
    @@ -113,7 +129,7 @@ The build will start!

    ---

    ### 6. Grab the Right File
    ### 7. Grab the Right File

    1. Open the zip file you downloaded.
    2. **Choose the file that does _*not*_ start with `original-`**.
    @@ -127,6 +143,6 @@ The build will start!

    You now have the **latest version of CoreProtect**, built from source without needing to understand a single line of code (or download anything!).

    If you value the plugin, support CoreProtect's [Patreon](https://www.patreon.com/CoreProtect) as it will keep future development going.
    If you value the plugin, support [CoreProtect's Patreon](https://www.patreon.com/CoreProtect) as it will keep future development going.

    Although this "paywalling" may seem annoying, it is necessary to keep the project going. Show some love to the developers and it might change in the future.
  6. slash1div revised this gist May 19, 2025. 1 changed file with 81 additions and 26 deletions.
    107 changes: 81 additions & 26 deletions build-coreprotect.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,33 +1,59 @@
    # Tutorial on how to build CoreProtect, entirely on GitHub!
    # How to Build CoreProtect Using Only GitHub (No Coding Required!)

    **Only a web browser, GitHub account, and a brain required.**
    > ✅ All you need:
    > - A **web browser**
    > - A **GitHub account**
    > - A bit of **patience**
    I am not a writer, I am just a nerdy dude who somewhat understands computers. If you have some experience with technology, you can probably power through this.
    ---

    CoreProtect has been what I'd call soft-paywalled starting with 1.21. What I mean is that if you have __no Java/Maven knowledge__, you cannot download CoreProtect on the latest versions.
    ## Why This Tutorial Exists

    I personally see why they did this, but this has caused a fair bit of users to swap to other plugins, such as Prism, which absolutely do not compare.
    Starting with Minecraft version **1.21**, CoreProtect no longer provides downloads unless you build it yourself using Java and Maven. If you're not a developer, this locks the plugin behind a paywall.

    This is causing many small servers to crash and burn on the slightest sign of griefing. I have paid for CoreProtect's Patreon, and do support donating to them, but there is some harm from "paywalling" this way.
    Many people have switched to alternatives like **Prism**, which don't measure up at all. This has caused small servers to suffer, with some shutting down due to griefing.

    This tutorial requires absolutely no knowledge on programming, is isolated entirely to your web browser, and takes only a few seconds to set up.
    After you are done, you should have the *LATEST* CoreProtect build within 5 minutes.
    This guide walks you through **how to build CoreProtect using GitHub only**. No Java knowledge, no downloads, and no B.S.

    # Let's get started.
    I am not a writer, just a tech guy, so try to power through.

    ---

    ## Let’s Get Started

    ---

    ### 1. Fork the Repository

    1. Visit this link:
    > https://github.com/PlayPro/CoreProtect/fork
    2. Click the **"Create fork"** button.
    3. (Optional) Rename it to something like `CoreProtect-Build`.

    ### Fork The Github
    You need a GitHub account. To fork the repo, click the link below and press the "Create fork" button.
    I'd rename it to something such as "CoreProtect-Build" so you know why the repo is in your account for future reference.
    https://github.com/PlayPro/CoreProtect/fork
    ![Creating Fork Page](https://gist.github.com/user-attachments/assets/d89b3bd2-7d48-4525-b3c6-c5c774cbbea9)

    ### Create a New File
    After forking, you should immediately be brought to your own repository.
    Near the upper middle of your screen, there is an "Add File" dropdown. Click that and then click "Create new file".
    ---

    ### 2. Create a New File

    1. After the fork is created, you’ll be in your own copy of the CoreProtect repository.
    2. Click the **"Add file"** dropdown near the top-middle of the page.
    3. Select **"Create new file"**.

    ![Create File Button Location](https://gist.github.com/user-attachments/assets/9f1e9b4c-7aa8-4b74-a010-a988e462aee1)

    ### Paste Contents
    Paste the text `.github/workflows/custom-fork-build.yml` into your file name at the top left. Then paste the code below into the giant file contents box.
    ---

    ### 3. Add Workflow Code

    1. In the **file name** box at the top, paste this:
    ```
    .github/workflows/custom-fork-build.yml
    ```

    2. Then paste the code below into the **big text box** underneath:

    ```yaml
    name: Custom Fork Build

    @@ -59,19 +85,48 @@ jobs:
    name: Custom Fork Build
    path: staging
    ```
    You can then create the file with the Commit Changes button on the top right.
    3. Click **"Commit changes"** in the top-right corner.
    ![Final Result of Pasting and Commit Button Location](https://gist.github.com/user-attachments/assets/6e9a0778-31a7-4910-aa49-d6f477f14778)
    ### Building the file
    On the top of the page, click the "Actions" button. After, there should be a "Custom Fork Build" in the sidebar.
    Click that, and there will be a "Run workflow" button. Click that and it will start running.
    ---
    ### 4. Run the Build
    1. At the top of the page, click the **"Actions"** tab.
    2. In the left sidebar, click **"Custom Fork Build"**.
    3. Click the **"Run workflow"** button.
    The build will start!
    ![Run Workflow Button Location](https://gist.github.com/user-attachments/assets/99d63532-67aa-47bc-b4d6-e096a261bfdd)
    ### Download it!
    On the top of your page, click the top workflow. Wait until it completes, and download the artifact zip. You will know it is done if there is a green checkmark.
    ---
    ### 5. Download the Finished Build
    1. Once the workflow finishes (you'll see a green checkmark), click the top result.
    2. Look for **"Artifacts"** and download the `.zip` file.

    ![Artifact Zip Location](https://gist.github.com/user-attachments/assets/079c6470-d199-4da1-92f9-ce9b30a506df)

    ### Grab the Correct File
    Inside the zip file, grab the file that **does not have** "original-" in front. You can upload this to your server to get CoreProtect!
    ---

    ### 6. Grab the Right File

    1. Open the zip file you downloaded.
    2. **Choose the file that does _*not*_ start with `original-`**.
    3. Upload that `.jar` file to your Minecraft server — you’re done!

    ![Zip File Overview with Proper File Circled. Improper file crossed out.](https://gist.github.com/user-attachments/assets/913ede31-5477-4f0e-9b62-41f2b2172ef6)

    ---

    ## You Did It!

    You now have the **latest version of CoreProtect**, built from source without needing to understand a single line of code (or download anything!).

    If you value the plugin, support CoreProtect's [Patreon](https://www.patreon.com/CoreProtect) as it will keep future development going.

    Although this "paywalling" may seem annoying, it is necessary to keep the project going. Show some love to the developers and it might change in the future.
  7. slash1div revised this gist May 19, 2025. 1 changed file with 6 additions and 6 deletions.
    12 changes: 6 additions & 6 deletions build-coreprotect.md
    View file
    Original file line number Diff line number Diff line change
    @@ -19,12 +19,12 @@ After you are done, you should have the *LATEST* CoreProtect build within 5 minu
    You need a GitHub account. To fork the repo, click the link below and press the "Create fork" button.
    I'd rename it to something such as "CoreProtect-Build" so you know why the repo is in your account for future reference.
    https://github.com/PlayPro/CoreProtect/fork
    ![image](https://gist.github.com/user-attachments/assets/d89b3bd2-7d48-4525-b3c6-c5c774cbbea9)
    ![Creating Fork Page](https://gist.github.com/user-attachments/assets/d89b3bd2-7d48-4525-b3c6-c5c774cbbea9)

    ### Create a New File
    After forking, you should immediately be brought to your own repository.
    Near the upper middle of your screen, there is an "Add File" dropdown. Click that and then click "Create new file".
    ![image](https://gist.github.com/user-attachments/assets/9f1e9b4c-7aa8-4b74-a010-a988e462aee1)
    ![Create File Button Location](https://gist.github.com/user-attachments/assets/9f1e9b4c-7aa8-4b74-a010-a988e462aee1)

    ### Paste Contents
    Paste the text `.github/workflows/custom-fork-build.yml` into your file name at the top left. Then paste the code below into the giant file contents box.
    @@ -60,18 +60,18 @@ jobs:
    path: staging
    ```
    You can then create the file with the Commit Changes button on the top right.
    ![image](https://gist.github.com/user-attachments/assets/6e9a0778-31a7-4910-aa49-d6f477f14778)
    ![Final Result of Pasting and Commit Button Location](https://gist.github.com/user-attachments/assets/6e9a0778-31a7-4910-aa49-d6f477f14778)
    ### Building the file
    On the top of the page, click the "Actions" button. After, there should be a "Custom Fork Build" in the sidebar.
    Click that, and there will be a "Run workflow" button. Click that and it will start running.
    ![image](https://gist.github.com/user-attachments/assets/99d63532-67aa-47bc-b4d6-e096a261bfdd)
    ![Run Workflow Button Location](https://gist.github.com/user-attachments/assets/99d63532-67aa-47bc-b4d6-e096a261bfdd)
    ### Download it!
    On the top of your page, click the top workflow. Wait until it completes, and download the artifact zip. You will know it is done if there is a green checkmark.
    ![image](https://gist.github.com/user-attachments/assets/079c6470-d199-4da1-92f9-ce9b30a506df)
    ![Artifact Zip Location](https://gist.github.com/user-attachments/assets/079c6470-d199-4da1-92f9-ce9b30a506df)
    ### Grab the Correct File
    Inside the zip file, grab the file that **does not have** "original-" in front. You can upload this to your server to get CoreProtect!
    ![image](https://gist.github.com/user-attachments/assets/913ede31-5477-4f0e-9b62-41f2b2172ef6)
    ![Zip File Overview with Proper File Circled. Improper file crossed out.](https://gist.github.com/user-attachments/assets/913ede31-5477-4f0e-9b62-41f2b2172ef6)
  8. slash1div created this gist May 19, 2025.
    77 changes: 77 additions & 0 deletions build-coreprotect.md
    View file
    Original file line number Diff line number Diff line change
    @@ -0,0 +1,77 @@
    # Tutorial on how to build CoreProtect, entirely on GitHub!

    **Only a web browser, GitHub account, and a brain required.**

    I am not a writer, I am just a nerdy dude who somewhat understands computers. If you have some experience with technology, you can probably power through this.

    CoreProtect has been what I'd call soft-paywalled starting with 1.21. What I mean is that if you have __no Java/Maven knowledge__, you cannot download CoreProtect on the latest versions.

    I personally see why they did this, but this has caused a fair bit of users to swap to other plugins, such as Prism, which absolutely do not compare.

    This is causing many small servers to crash and burn on the slightest sign of griefing. I have paid for CoreProtect's Patreon, and do support donating to them, but there is some harm from "paywalling" this way.

    This tutorial requires absolutely no knowledge on programming, is isolated entirely to your web browser, and takes only a few seconds to set up.
    After you are done, you should have the *LATEST* CoreProtect build within 5 minutes.

    # Let's get started.

    ### Fork The Github
    You need a GitHub account. To fork the repo, click the link below and press the "Create fork" button.
    I'd rename it to something such as "CoreProtect-Build" so you know why the repo is in your account for future reference.
    https://github.com/PlayPro/CoreProtect/fork
    ![image](https://gist.github.com/user-attachments/assets/d89b3bd2-7d48-4525-b3c6-c5c774cbbea9)

    ### Create a New File
    After forking, you should immediately be brought to your own repository.
    Near the upper middle of your screen, there is an "Add File" dropdown. Click that and then click "Create new file".
    ![image](https://gist.github.com/user-attachments/assets/9f1e9b4c-7aa8-4b74-a010-a988e462aee1)

    ### Paste Contents
    Paste the text `.github/workflows/custom-fork-build.yml` into your file name at the top left. Then paste the code below into the giant file contents box.
    ```yaml
    name: Custom Fork Build

    on:
    workflow_dispatch: {}

    jobs:
    build:
    runs-on: ubuntu-latest
    steps:
    - name: Checkout repository
    uses: actions/checkout@v4

    - name: Set up JDK 22
    uses: actions/setup-java@v4
    with:
    java-version: 22
    distribution: temurin

    - name: Build
    run: mvn package --file pom.xml

    - name: Get build artifact ready
    run: mkdir staging && cp target/*.jar staging

    - name: Upload a Build Artifact
    uses: actions/upload-artifact@v4
    with:
    name: Custom Fork Build
    path: staging
    ```
    You can then create the file with the Commit Changes button on the top right.
    ![image](https://gist.github.com/user-attachments/assets/6e9a0778-31a7-4910-aa49-d6f477f14778)
    ### Building the file
    On the top of the page, click the "Actions" button. After, there should be a "Custom Fork Build" in the sidebar.
    Click that, and there will be a "Run workflow" button. Click that and it will start running.
    ![image](https://gist.github.com/user-attachments/assets/99d63532-67aa-47bc-b4d6-e096a261bfdd)
    ### Download it!
    On the top of your page, click the top workflow. Wait until it completes, and download the artifact zip. You will know it is done if there is a green checkmark.
    ![image](https://gist.github.com/user-attachments/assets/079c6470-d199-4da1-92f9-ce9b30a506df)
    ### Grab the Correct File
    Inside the zip file, grab the file that **does not have** "original-" in front. You can upload this to your server to get CoreProtect!
    ![image](https://gist.github.com/user-attachments/assets/913ede31-5477-4f0e-9b62-41f2b2172ef6)