Replies: 3 comments
-
My thoughts: I don't have the time or ability to fork Lich4, update it for the TLS change, and maintain it structurally. Further, we've known about the TLS change for a few weeks now, and no one has volunteered to take said task on. The most recently very active real-life dev who also still plays the game -- @KatoakDR -- (no offense to those who no longer play), is currently playing life/family and is not available to take this on. And the TLS change is imminent, and it's a fully breaking change if we don't take action. What we have in Lich5 is few fold:
It was asked recently in Discord why we're leaning toward favoring a switch to Lich5 vs. updating Lich4 to handle the TLS changes. I think the simple answer is this: of those who have the ability, who has offered to update Lich4? So, in absence of anyone willing or able to take on a fork/update of Lich4, @MahtraDR has spearheaded the charge to get us loaded up on Lich5 with the crucial support of the GS-Lich5 crew. And no less critical, Doug and team from GS-Lich5 have been extraordinarily free with their time to help take big steps to integrate DR. I've tried to do my part with testing of the install process and the functionality. As a final point, let me say that we owe a lot to the old DR Lich folks (some of which are still involved). And nothing I've written above is meant to lessen the project that they built from the ground up and from which we are currently benefiting. But we're faced at the moment with the necessity of change. And the Lich5 approach seems to be best for all involved, in my opinion. Thanks to: @rpherbig @rcuhljr @KatoakDR @MahtraDR @BinuDR @Hiinky -- among others who formerly have and are currently contributing in the way they can, some of whom don't even play the game any longer but still help the project as a labor of love. Appreciate ya' all. |
Beta Was this translation helpful? Give feedback.
-
The Lich fork was always a last resort, it just wasn't tenable to have 3+ month turn arounds on core parts of the lich suite that controlled movement, stream processing, and other low level issues. The transition to an actively maintained and shared tooling system is really the best possible outcome I can see for it at this point. The fact that we get a more integrated one click installer is just gravy to help out with new user adoption. I think at this point it's probably safe to say that the useful functionality of lich fork and the dr-scripts repos are first class citizens in DragonRealms for people using Lich, this change just highlights that fact, even if there's some incidental toe stepping. |
Beta Was this translation helpful? Give feedback.
-
I'm 100% on board with switching over to lich 5. I've played around with the test branch a bit here and there and did not notice anything breaking. Would have responded to this earlier but work has been brain melting the last couple of weeks. The Elanthia Online folks on the GS side seem to be very keen on getting the DR side of things merged in and have been actively working with the DR Script's team to make this happen. I think this is a great partnership and with the combined coding abilities of both teams we can see much further into the future than as things currently stand. |
Beta Was this translation helpful? Give feedback.
-
Hi folks,
Simu decided, about 20 days ago now, that they would disable non-TLS authentication to DR. This has created a scramble in the 3rd party front-end community, since many FEs did not do this natively. We were then in a comparatively fortunate position, since Gemstone has already had this enabled for awhile, and the fine folks over at https:/elanthia-online/lich-5 had working code, and @OSXLich-Doug in particular helped port that code to dr-lich, this was merged into our fork with dragon-realms/dr-lich#74 about two weeks ago.
Simu has not, as yet, shut off the non-TLS port, as they are waiting on their Avalon team to enable TLS on that FE before doing so. We have been told this is imminent, in a manner of weeks, not months.
At the same time that I submitted the PR to dr-lich, I also submitted the same code to Tillmen's repo here matt-lowe/Lich#62
Without a fix for the TLS issue being merged into Tillmen's lich, our existing install process will cease to function when Simu flips the switch.
In light of this, and since we had an excellent experience with the lich5 folks already, I started discussions on merging dr-lich into lich5. Which by and large is done now.
The lich5 community is extremely welcoming, friendly, and more importantly, active. As of now, I've been using lich5 with dr-lich changes for a couple of weeks. There have been minor hiccups, but largely those have been addressed.
This discussion is more to flag any potential caveats I don't think of, or any concerns folks might have with this move.
Major benefits of moving to lich5 include:
Drawbacks of moving to lich5:
Considerations:
I personally think moving to lich5 is the best path forward for us. We leverage the development team of lich5, and continue with relatively minimal involvement, as we like, and can focus on dr-scripts, which is my personal preference.
My thoughts. Opinions?
Beta Was this translation helpful? Give feedback.
All reactions