Skip to content

Make the temporary getRegistryClassInfo public and outside the BukkitClasses #8041

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: dev/patch
Choose a base branch
from

Conversation

TheLimeGlass
Copy link
Contributor

@TheLimeGlass TheLimeGlass commented Jul 16, 2025

Problem

If this temporary solution of doing reflection is how Skript is going to registries for past version support, you need to also allow addon developers to do the same methods.

Also this new method being at the bottom of BukkitClasses will be a git conflict nightmare.

Solution

To move it into BukkitUtils or PaperUtils where this method calls parts of from anyways.

Other

This PR was made during the merge of 2.12 so when the dev/patch eventually gets updated from master, the target branch can be changed to that, assuming nothing gets reverted from master. Targeting dev/patch because this new way of registering registries needs to be given to addon developers asap.

@TheLimeGlass TheLimeGlass requested a review from a team as a code owner July 16, 2025 04:15
@TheLimeGlass TheLimeGlass requested review from Burbulinis and TheMug06 and removed request for a team July 16, 2025 04:15
@TheLimeGlass TheLimeGlass changed the base branch from master to dev/patch July 16, 2025 04:27
@sovdeeth sovdeeth added enhancement Feature request, an issue about something that could be improved, or a PR improving something. needs reviews A PR that needs additional reviews labels Jul 16, 2025
@skriptlang-automation skriptlang-automation bot added patch-ready A PR/issue that has been approved and is ready to be merged/closed for the next patch version. and removed needs reviews A PR that needs additional reviews labels Jul 17, 2025
@sovdeeth sovdeeth moved this to Awaiting Merge in 2.12 Releases Aug 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature request, an issue about something that could be improved, or a PR improving something. patch-ready A PR/issue that has been approved and is ready to be merged/closed for the next patch version.
Projects
Status: Awaiting Merge
Development

Successfully merging this pull request may close these issues.

4 participants