Fabric Port 1.21.x

[cputnam-a11y]

I'm planning on porting this mod to fabric, It appears the license would permit such a thing.
In order to mirror behavior and maintain feature parity, I wanted to ask about your plans for 1.21. (1-3), and how you plan to adapt to the changes of newer versions. I understand that a port/update to modern versions may be a ways off. It seems that the way BonsaiTrees uses recipes may shift to mirror the server sidedness of recipes? would appreciate any info that can be provided

[cputnam-a11y]

Side note this may not be the right place for this discussion, please feel free to redirect me to a more appropriate place

[davenonymous]

While the license would permit this, I am still actively working on this mod and might do a fabric port myself.
I'd appreciate not having a publicly released fork/port of the mod for the time being.

Edit: Since somebody else recently published a fork of this mod (which has been taken down by now), I'm going to change the license to something more restrictive in the future. Sorry.

[cputnam-a11y]

I'm going to give a not comment on you changing the licence and the legalities of that :) I assume that this means that you are not willing to give me a direction as of updates? I currently do not have plans to publish a fork, and if you released a fabric fork, mine would be archived, I don't like maintaining mods, only porting

[davenonymous]

Don't worry. 1.21 is going to be a complete rewrite anyway. But yeah, you are right. It's probably easier to keep reporting all re-releases than dealing with the drama.
I'm not sure what you mean regarding "direction of updates". Yes, recipes will work differently. Tree models will probably work differently. A lot of things will change.

[cputnam-a11y]

Okay, I'll rewrite it then

[davenonymous]

Great. Have fun with that.

[cputnam-a11y]

Re-Releases technically are not an infringement of license, and technically shouldn't be taken down. If you have qualms with your work being Re-Released, I would suggest going to a more restrictive licence, I was stating that code under mit is under mit, there is not requirement that a person that received code and assets under mit follow the updated licence, because it is not. I don't think I'll continue to talk licences, because I think that over text I may sound hostile and not informative.

[cputnam-a11y]

As a completely different question, and my last one, a fabric port may happen, or you have plans for one, or I'm not entitled to know lol?

[cputnam-a11y]

I'm guessing because this is closed, you won't get notifications on this, have a good day, thank you for your help :)

[davenonymous]

It's still common courtesy to ask whether it's ok to port an actively maintained mod. At least it was like that in the Minecraft community for a long time. It seems that has changed. But for me "I'm planning to do something with your thing without asking you if it's ok first" is not a good way to start a discussion.

[davenonymous]

The idea of releasing mods as open-source is in part so that someone can take over in case the original author lost interest and for others to learn from your code. Releasing the code as MIT, GPL, Apache or whatever is usually in good spirit that no one will abuse it even though the license says they could.

[cputnam-a11y]

No valid response, sorry I offended you. As I said above, thank you for your time and help. Hope I can start future interactions with you better. As said above, I currently have no plans to release your work, ported or not. When you make a fabric version, I would be interested in assisting, assuming it is permitted under whatever licencing you work out. Please understand that my discussion of licencing was not, I intend to violate your intention for your mod, but please fix this, it sounds like you have made a grave mistake in how you licenced your mod. as stated above, sorry for A. The very off topic thread and B. Everything else (I tried making this more specific, but It sounded very ah ish). Once again, have a good day and I wish you well on your modding and re-licencing journey.

[cputnam-a11y]

Okay, I'll rewrite it then

At this point, doubt you care given what you said about having reposts taken down, but I'll just not do it. I'll just become the number one lookout for the official fabric port.

I don't want to be the one ah that ruins your day, although I probably did. (I think I'm actually done talking now.)

[cputnam-a11y]

would you be open to prs on your lib for a fabric branch, if you see this? Responseless :( I didn't English properly and it cost me a potential relationship.