-
-
Notifications
You must be signed in to change notification settings - Fork 74
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
Monitor feature #650
base: dev/0.8
Are you sure you want to change the base?
Monitor feature #650
Conversation
only can load and have events so far
but it still have some bugs when rendering
Apologies for barging in here. I don't really like to do this, but I do think this is important. When copying code from another project, you need to follow the license that code is released under. Personally, I'm not normally fussed for small stuff, but this PR contains ~2k LoC copied from CC/CC:T. In this case, it looks like the code has been copied from the 1.19.2 branch of CC:T, and so is licensed under the CCPL. The CCPL is a viral license, and requires that all projects using its code are also licensed under the CCPL. I'd recommend instead taking as much code as possible from the 1.20.1 branch1. More of the code there is licensed under the MPL 2.0 which, unlike the CCPL, is non-viral. However, some pretty significant components are still under the CCPL (text rendering, monitor BE). For those, you have several options:
Footnotes
|
@SquidDev Thanks for the LICENSE suggesting. (I'm not experience at it.) Just to confirm, if I paste the codes from 1.20.1 branch, which are under MIT license, is there no risk that will ask to change the LICENSE for all codes under AP? Also do I need to mention and keep the MIT license for those files that copied? |
Yeah, software licensing is very confusing! I find Choose a License and TLDR;Legal both pretty useful resources for summarising what a license enables/prevents you from doing. For the MPL 2.0 (I assume you meant this rather than MIT, CC:T does not use MIT), the main requirement is that code licensed under the MPL retains that license. So you just need to keep the copyright header intact. |
Unfortunately a few files are still under CCPL (such as ServerMonitor), so I probably need rewrite some logics. |
Okay, I probably have to use mixins, hopefully that won't break things. |
This PR is abandoned for two months, just to clarify, there are two problems need to solve.
|
Transparent rendering is just pain in minecraft, it's a bit better in newer versions but still not nice to play with
CC:T does not support 1.19.2 anymore and I hope I can drop support for 1.19.2 too when I finish everything for 0.8 |
PLEASE READ THE GUIDELINES BEFORE MAKING A CONTRIBUTION
What kind of change does this PR introduce? (Bug fix, feature, ...)
Feature
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their scripts due to this PR?)
No