# How to Build CoreProtect Using Only GitHub (No Coding Required!)

> ✅ All you need:  
> - A **web browser**  
> - A **GitHub account**  
> - A bit of **patience**

---

## Why This Tutorial Exists

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.

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.

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.

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.

---

## 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`.

![Creating Fork Page](https://gist.github.com/user-attachments/assets/d89b3bd2-7d48-4525-b3c6-c5c774cbbea9)

---

### 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)

---

### 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

on:
  workflow_dispatch: {}

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

      - name: Set up JDK 21
        uses: actions/setup-java@v4
        with:
          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=master

      - 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: ${{ steps.jar.outputs.jar_name }}
          path: staging/${{ steps.jar.outputs.jar_name }}
          compression-level: 0
```

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)

---

### 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)

---

### 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 (✅).
  > 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!

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)

---

### 6. Grab the Jar

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!

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)

---

### 7. 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.

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)

---

## 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. 

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. ❤️