Merged
Conversation
Member
Author
|
26.1.1 test is failing due to Paper Server issue. I've opened a PR there to resolve the issue: PaperMC/Paper#13741 |
Absolutionism
approved these changes
Apr 7, 2026
1 task
sovdeeth
approved these changes
Apr 9, 2026
Efnilite
approved these changes
Apr 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Skript is not currently working on Paper's 26.1 development branch due to changes within BukkitUnsafe. Paper 26.1 also requires Java 25, which we will need to update to.
Solution
This PR updates Skript to build with Java 25. Java 21 is still supported (meaning no newer features can be used).
I've also reworked how aliases applies item component data (the cause of Skript not running). Rather than use BukkitUnsafe, we can instead use Brigadier's ItemStack parser, exposed by Paper (which is essentially what the BukkitUnsafe method does anyways). This is the more stable (and likely recommended) approach.
Testing Completed
Added 26.1.1 testing environment.
Supporting Information
Completes: none
Related: none
AI assistance: none