Update Minecraft 1.21.8

[NoltoxGit]

Overview

This pull request introduces support for Minecraft server version 1.21.8 by updating configuration files, dependencies, and constants. The changes ensure compatibility with the new version while maintaining support for previous versions.

Fixes #3236

Description

• Updated .github/ISSUE_TEMPLATE/bug_report.yml to include 1.21.8 as a selectable server version in the bug report template.
• Updated the build.gradle.kts file in the adapter-1_21_6 module to use the Paper dev bundle for version 1.21.8-R0.1.
• Modified PaperweightAdapter.java to include a check for DATA_VERSION_MC_1_21_8 and updated the error message to reflect support for 1.21.6, 1.21.7, and 1.21.8.
• Added a new constant DATA_VERSION_MC_1_21_8 with the value 4440 in Constants.java.

Submitter Checklist

• Make sure you are opening from a topic branch (/feature/fix/docs/ branch (right side)) and not your main branch.
• Ensure that the pull request title represents the desired changelog entry.
• New public fields and methods are annotated with @since TODO.
• I read and followed the contribution guidelines.

[Athar42]

In the build.gradle.kts, there is at least one mistake :
the().paperDevBundle("1.21.8-R0.1-20250717.225444-12")

This release can't exist, max build for 1.21.8 is 5, so -12 can't be ^^

Source : https://repo.papermc.io/service/rest/repository/browse/maven-public/io/papermc/paper/dev-bundle/1.21.8-R0.1-SNAPSHOT/

So, a more accurate one would be :
the().paperDevBundle("1.21.8-R0.1-20250718.183306-5")

[NoltoxGit]

In the build.gradle.kts, there is at least one mistake : the().paperDevBundle("1.21.8-R0.1-20250717.225444-12")

This release can't exist, max build for 1.21.8 is 5, so -12 can't be ^^

Source : https://repo.papermc.io/service/rest/repository/browse/maven-public/io/papermc/paper/dev-bundle/1.21.8-R0.1-SNAPSHOT/

So, a more accurate one would be : the().paperDevBundle("1.21.8-R0.1-20250718.183306-5")

Fixed!

[Athar42]

@Tsoccerguy3 : You are not using the latest commits, you get the failure from the error I reported earlier (and for which he already correct it)

[ghost]

Can you make it possible to export as a Jar File in Action for download?

[NoltoxGit]

@SarabethIrwys
You can pick up the build here: https://github.com/IntellectualSites/FastAsyncWorldEdit/actions/runs/16378261089

[PierreSchwang]

Please cherry-pick EngineHub/WorldEdit@9164c46 and adjust the version check (as done similarly in WorldEdit in a later commit). Not sure if we should reference the WorldEdit docs in the version warning.

[NoltoxGit]

Like this @PierreSchwang?

[NoltoxGit]

It's good now @PierreSchwang?

[PierreSchwang]

seems to work

[SirYwell]

Two minor suggestions

[NoltoxGit]

Hey @SirYwell,
I've just apply your suggestions!

I've questions about your modifications, does I need to delete 1.21.7 everywhere?
Like here:

1. https://github.com/IntellectualSites/FastAsyncWorldEdit/pull/3237/files#diff-637f7b97bba458badb691a1557c3d4648686292e948dbe3e8360564378b653efR31
2. https://github.com/IntellectualSites/FastAsyncWorldEdit/pull/3237/files#diff-893e7c3b186915bea4471756076fdec0614b8acb139668fb458e3063784473a8R223
3. https://github.com/IntellectualSites/FastAsyncWorldEdit/pull/3237/files#diff-a1d9aab73ba4bf503e22d332759cba434aa3ef3ebb024c248d7a4fb04b8a8b07R120

[SirYwell]

I've questions about your modifications, does I need to delete 1.21.7 everywhere?

No, we still support 1.21.7, but we don't need a special runServer gradle task for that version as we can just run a 1.21.8 server.

[NoltoxGit]

I've questions about your modifications, does I need to delete 1.21.7 everywhere?

No, we still support 1.21.7, but we don't need a special runServer gradle task for that version as we can just run a 1.21.8 server.

Oke, good!

[SirYwell]

Why does it seem like the Coreprotect feature doesn't work with FAWE in this version? You haven't been approved yet.

This PR has nothing to do with CoreProtect.

[SirYwell]

Going to approve even though the CI currently fails due to jitpack issues. The changes look good.

[NoltoxGit]

Why does it seem like the Coreprotect feature doesn't work with FAWE in this version? You haven't been approved yet.

Hey @SarabethIrwys,
Surely it's for CoreProtect to update its API or something else, as nothing touches CoreProtect in this PR.
Please get in touch with the developer of this plugin!

[NoltoxGit]

Hey,
Normally the problem seems to have been solved, as I've been able to compile it locally!

[SirYwell]

Thanks @NoltoxGit