Spottedleaf

Final change of plans (March 8, 2024)

I don't see that many people are using Starlight on modern versions anymore. As such, I don't see any reason to continue to maintain the mod versions, given that they do have real mod conflict issues with other mods. Starlight is also not neccessary to use on 1.20.x anyways.

Starlight may make a return in a future project of mine, but for now I am ceasing to upload new mod versions and commit updates to the github. If you want Starlight on the server, you will need to use Paper or one of its derivatives.

advaith1

Discord Nitro Subscription Links

	Monthly	3 Month	6 Month	Yearly
Nitro Basic	$2.99 🎁	N/A	N/A	$29.99 🎁
Nitro Classic	$4.99 🎁	N/A	N/A	$49.99 🎁
Nitro	$9.99 [🎁](https://discord.com/billing/premium/subscribe?plan_id=51165

FxMorin

Introduction

Let me start by clarifying that the following doesn't exclusively apply to Debugify, but they serve as an excellent illustration of the heinous behavior outlined in the following. The mods in question shall therefore be collectively referred to as "Scummy Mods".

Scummy Mods are mods that incorporate or outright copy foreign code bases, without permission from the original author. They commonly state to either "replace" or "include" the original work, if any mention is given at all. Developing a mod is not easy. Many mod creators sacrifice significant chunks of their personal time and resources to their creations, essentially for free. Curseforge offers a symbolic compensation for the hours poured, but it's usually insignificant and just a nice bonus.

The Problem

The majority of the original projects are still in development. Since the creators behind Scummy Mods typically do not understand the code they copied to begin with, they lack the knowledge required to eliminate the bugs that will

falseresync

Gist of it:

• Player swapped Apple for callo
• People got angry about that and called out Player
• Player responded by silencing people
• People went crazy shit about silencing and started telling Player all his flaws to the face
• Player went on a power trip and used the nuclear option: ban and mute 30+ people, he removed several hundreds of messages and managed to kick out of the team several big Fabric and Yarn contributors
• modmuss left Fabric for a while
• people are now actually preparing a Fabric fork with better and well defined governance a drop in replacement with decent governance at first, better tech afterwards

Result:

The-Fireplace

So, as I update mods and switch more of them over to Fabric, I'm sure I'll frequently get asked "Will you port to Forge" or "Why not Forge," so I figured I'd make a document explaining why and link to it instead of typing up the explanation every time.

The Short Version

Maintaining mods for two different mod loaders is time consuming, and when choosing between them, Fabric is the clear choice to me. If I ever get to the point where my mods are all updated, I will consider porting mods to Forge on a case-by-case basis, but it will not be a priority. The lead developer of Forge, LexManos, has essentially told me he will not support features that allow me to update at least one of my mods past 1.12.2, and on top of that, he did so very rudely while treating me like a complete idiot for trying to make it possible to continue using Forge for that mod. I am not the only person he has treated in this manner, and I do not support this kind of toxic behavior.

But how does Fabric compare to Forge?

I've conside

jagrosh

Step 1 - Make a Discord Webhook

1. Find the Discord channel in which you would like to send commits and other updates

2. In the settings for that channel, find the Webhooks option and create a new webhook. Note: Do NOT give this URL out to the public. Anyone or service can post messages to this channel, without even needing to be in the server. Keep it safe!

Step 2 - Set up the webhook on Github

1. Navigate to your repository on Github, and open the Settings