-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Change SignTranslateEvent to use Adventure #688
Comments
I think the days of 1.18.2 support are numbered, so if it's cleaner to make a 1.20+ compatible system with no support for 1.18.2, I'd prefer that. |
It is cleaner to remove 1.18 support. For a comparable system, i have the SignWrapper class in my sign PR, it essentially abstracts away the relevant calls to an event or sign side |
So, just to get this straight: I do have permission to remove 1.18.x stuff from the repo via a PR that fixes this issue? |
For now I'd like to keep 1.18.2 support, so if possible I'd like for this change to be separated from the sign PR. With that said, please feel free to open up a PR which removes 1.18.2 and implements this, it just may not be merged immediately. Originally the plan was to keep 1.18.2 support until Minecraft 1.22 drops, but this issue is a good reason to accelerate that timeline and drop it earlier. However, AP is still running 1.18.2 and I will need to update it before we drop support. |
Alright, do you mind if i use my "adapter" that i already have within the PR then? |
Sure, but put in some comments mentioning that when 1.18.2 is dropped, they should be removed as well (specifically include "1.18.2" so that a search all finds them). |
Sounds good, i'll leave a deprection note and a comment in the relevant places. |
Is your feature request related to a problem? Please describe.
All old setLine(), getLine() etc methods that operate on strings are deprecated and the new methods use Components. We should do the same in our event.
In addition since 1.20 signs have multiple sides you can write on, so in that version we need to call that event per side, otherwise we will lose data.
Describe the solution you'd like
Migrate the fields and methods to use Components and as long as 1.18 is being used, define a wrapper class that actually fills and handles the relevant parts in Translate and Rotate tasks.
The text was updated successfully, but these errors were encountered: