Skip to content
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

My plugin stopped working #11411

Closed
foxya27 opened this issue Sep 17, 2024 · 6 comments
Closed

My plugin stopped working #11411

foxya27 opened this issue Sep 17, 2024 · 6 comments
Labels
status: needs triage type: bug Something doesn't work as it was intended to.

Comments

@foxya27
Copy link

foxya27 commented Sep 17, 2024

Expected behavior

I have a self-written plugin UsefulWanderingTrader and it worked on Purpur 2306 version

Observed/Actual behavior

image

Steps/models to reproduce

Install the plugin and start the server

Plugin and Datapack List

image

Paper version

Current Purpur Version: 1.21.1-2306-bc7bcbb (MC: 1.21.1)*

Other

I had to go back to the previous version again for the plugin to work, this is not a PurPur mistake, they just made the last 2 versions upstream
image

@foxya27 foxya27 added status: needs triage type: bug Something doesn't work as it was intended to. labels Sep 17, 2024
@foxya27
Copy link
Author

foxya27 commented Sep 17, 2024

UsefulWanderingTrader-1.4.0-SNAPSHOT.zip
This plugin

@electronicboy
Copy link
Member

Spigot made a type change inside of internals, use the API

@electronicboy electronicboy closed this as not planned Won't fix, can't repro, duplicate, stale Sep 17, 2024
@foxya27
Copy link
Author

foxya27 commented Sep 17, 2024

Spigot made a type change inside of internals, use the API

Does this mean that the entire plugin will need to be rewritten?

@electronicboy
Copy link
Member

No, not unless you're performing such digging into internals all over the place. The API already covers the ability to mess with game profiles and has for years.

@foxya27
Copy link
Author

foxya27 commented Sep 17, 2024

No, not unless you're performing such digging into internals all over the place. The API already covers the ability to mess with game profiles and has for years.

I know that one of those lines causing error:
Field profileField = skullMeta.getClass().getDeclaredField("profile");
profileField.setAccessible(true);
profileField.set(skullMeta,profile);
How to get the same result using API, without getting into skillMeta's class which (probably) causes error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: needs triage type: bug Something doesn't work as it was intended to.
Projects
Status: Invalid
Development

No branches or pull requests

2 participants