增加新modloader———NeoForge的支持 #2406
Comments
|
Forge团队里所有人都移到NeoForge里去了 |
|
看看情况再说吧 |
|
你也可以把neoforged的安装器拖进hmcl的自动安装里 |
|
多等一会儿，待事情结束以后再处理 |
|
这事起于Forge作者LexManos作死，把Forge团队的人惹毛了 |
|
u1s1，他是 |
|
neoforged是团队名 |
|
实际上，HMCL无法启动NeoForge (neoforged/NeoForge#75) |
啊，我这能启动啊 |
你是怎么安装的 |
|
|
这不是原版Forge？ |
我随便截得图， |
|
艹，多谢提醒 |
|
这是一件令人愉快的事
…---原始邮件---
发件人: ***@***.***>
发送时间: 2023年8月23日(周三) 下午4:23
收件人: ***@***.***>;
抄送: ***@***.******@***.***>;
主题: Re: [huanghongxun/HMCL] 增加新modloader———NeoForge的支持 (Issue #2406)
BMCLAPI 已支持 NeoForge
https://bmclapidoc.bangbang93.com/#api-Neoforge
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
可以观察一下原始的 forge 是否会被继续维护，如果没有积极维护的话，也许可以直接对于 1.20+ 用 NeoForge 直接替换掉 Forge 的位置。 |
还是别这样，新增一个位置就行了，不积极维护不代表不维护呀 |
forge团队可以说就剩一个人了 ，谁来更新代码啊，还不一定有新血液加入 |
|
|
mcmod社区又多了一个加载器（ |
|
现在 Forge 的情况怎么样了？ |
@burningtnt 你可以来 Forge 的 Discord 看一看，仍然在活跃，仍然在更新 |
|
但是应该像当时quilt出现时的那样立马做兼容（
| |
***@***.***
|
|
***@***.***
|
…---- 回复的原邮件 ----
| 发件人 | ***@***.***> |
| 日期 | 2023年09月10日 18:47 |
| 收件人 | ***@***.***> |
| 抄送至 | ***@***.***>***@***.***> |
| 主题 | Re: [huanghongxun/HMCL] 增加新modloader———NeoForge的支持 (Issue #2406) |
现在 Forge 的情况怎么样了？
@burningtnt 你可以来 Forge 的 Discord 看一看，仍然在活跃，仍然在更新
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
当时 Quilt 和现在 Forge 事件可不一样…… |
看到了，那可以考虑同时支持 NeoForged 和原 Forge |
|
具体情况只能看1.21发布后那个能更新到1.21了，但是高版本开发者一定会大量转向neoforge（因为和fabric开发组的关系已经没以前差了，甚至以前在forge的discord讨论任何和fabric和旧版本forge的内容都会被封禁）
| |
***@***.***
|
|
***@***.***
|
…---- 回复的原邮件 ----
| 发件人 | ***@***.***> |
| 日期 | 2023年09月10日 18:47 |
| 收件人 | ***@***.***> |
| 抄送至 | ***@***.***>***@***.***> |
| 主题 | Re: [huanghongxun/HMCL] 增加新modloader———NeoForge的支持 (Issue #2406) |
现在 Forge 的情况怎么样了？
@burningtnt 你可以来 Forge 的 Discord 看一看，仍然在活跃，仍然在更新
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
forge这次问题更加严重，就应该提前做好兼容以防以后的变故，而且neoforge官方放出了api给开发者查询版本列表
| |
***@***.***
|
|
***@***.***
|
…---- 回复的原邮件 ----
| 发件人 | ***@***.***> |
| 日期 | 2023年09月10日 18:53 |
| 收件人 | ***@***.***> |
| 抄送至 | ***@***.***>***@***.***> |
| 主题 | Re: [huanghongxun/HMCL] 增加新modloader———NeoForge的支持 (Issue #2406) |
但是应该像当时quilt出现时的那样立马做兼容
当时 Quilt 和现在 Forge 事件可不一样……
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
？你要是在 HMCL 讨论 PCL，我也会考虑把你封了 |
|
把neoforge塞入forge里面，告诉玩家neoforge是forge的改进版（
| |
***@***.***
|
|
***@***.***
|
…---- 回复的原邮件 ----
| 发件人 | ***@***.***> |
| 日期 | 2023年09月10日 18:55 |
| 收件人 | ***@***.***> |
| 抄送至 | ***@***.***>***@***.***> |
| 主题 | Re: [huanghongxun/HMCL] 增加新modloader———NeoForge的支持 (Issue #2406) |
现在 Forge 的情况怎么样了？
@burningtnt 你可以来 Forge 的 Discord 看一看，仍然在活跃，仍然在更新
看到了，那可以考虑同时支持 NeoForged 和原 Forge
但我怕在自动安装界面放 NeoForge 和 Forge 两个过于相似的名称会导致部分玩家误解（我这个担忧有道理吗（？））
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
但是mod社区不应该是竞争关系，mod社区本来就应该是互相包容的，而且forge项目组和fabric项目组的主要冲突就是lexmanos，现在forge项目组也受不了lexmanos了
| |
***@***.***
|
|
***@***.***
|
…---- 回复的原邮件 ----
| 发件人 | ***@***.***> |
| 日期 | 2023年09月10日 18:57 |
| 收件人 | ***@***.***> |
| 抄送至 | ***@***.***>***@***.***> |
| 主题 | Re: [huanghongxun/HMCL] 增加新modloader———NeoForge的支持 (Issue #2406) |
具体情况只能看1.21发布后那个能更新到1.21了，但是高版本开发者一定会大量转向neoforge（因为和fabric开发组的关系已经没以前差了，甚至以前在forge的discord讨论任何和fabric和旧版本forge的内容都会被封禁）
？你要是在 HMCL 讨论 PCL，我也会考虑把你封了
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
（启动器圈是什么时候出现这种非商业竞争的？）
| |
***@***.***
|
|
***@***.***
|
…---- 回复的原邮件 ----
| 发件人 | ***@***.***> |
| 日期 | 2023年09月10日 18:57 |
| 收件人 | ***@***.***> |
| 抄送至 | ***@***.***>***@***.***> |
| 主题 | Re: [huanghongxun/HMCL] 增加新modloader———NeoForge的支持 (Issue #2406) |
具体情况只能看1.21发布后那个能更新到1.21了，但是高版本开发者一定会大量转向neoforge（因为和fabric开发组的关系已经没以前差了，甚至以前在forge的discord讨论任何和fabric和旧版本forge的内容都会被封禁）
？你要是在 HMCL 讨论 PCL，我也会考虑把你封了
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
这不是商业竞争。 如果你愿意给 HMCL 的各位开发者发工资，那么，我们一定会让 HMCL 及时更新。 |
|
我说的是PCL和其他的C#套壳启动器（还有就是我说的不是非商业竞争吗）
| |
***@***.***
|
|
***@***.***
|
…---- 回复的原邮件 ----
| 发件人 | ***@***.***> |
| 日期 | 2023年09月10日 19:08 |
| 收件人 | ***@***.***> |
| 抄送至 | ***@***.***>***@***.***> |
| 主题 | Re: [huanghongxun/HMCL] 增加新modloader———NeoForge的支持 (Issue #2406) |
这不是商业竞争。
HMCL 是开源启动器，由社区共同开发。因此，HMCL 的更新做不到及时，开发速度完全取决于最近开发者闲不闲。
因此，我们经常会等待一个时态稳定后再做出决定，防止无用功。
如果你愿意给 HMCL 的各位开发者发工资，那么，我们一定会让 HMCL 及时更新。
@Jack253-png
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
合并至 #2509 |
描述 Description
目前Forge团队貌似拆散了，重新组了个新的。
这是新的github
https://github.com/neoforged/NeoForge
这是新的网站页面
https://neoforged.net/
原因 Why
Forge可能停更；
这是NeoForge给的描述
What has happened here?
As of July 12th 2023, the discord formerly known as “Forgecord” was rebranded to a new project - NeoForged.
NeoForged is a fork of MinecraftForge. Almost all of the original team has joined the new team, with one obvious exception, LexManos (hereby referred to as Lex).
This news post will attempt to explain the circumstances leading to this drastic action. It presents the perspective of the new team however, and specifically, my (cpw) perspective and motivations.
Why did this happen?
Firstly, I want to be clear. Attributing this to a single event is to attribute death by a thousand cuts to a single cut.
After the latest difficulties in the Minecraft Forge discord, I wanted to understand why Curle felt she needed to resign from the position Lex put her in - namely, leader of the project. She had done an amazing job of organizing the team prior to the promotion to leader, and it was surprising to me that she felt the need to leave so shortly after. The discussion with her opened my eyes to the fact that there had been ongoing difficulties with the team she had spent so much time to build, and Lex was the root of the problem.
I want to be clear, Lex has been a problem in the modding community for many, many years. Almost every veteran minecraft modder has had a negative interaction with him over the past 12 years. I have, when able to, tried to steer people to not abandon Forge just because of Lex - defending him in many a private conversation with a frustrated modder who’d just been called a “Cunt” for 1,000th time by Lex, or banned from our online spaces for a trivial transgression like discussing Fabric or coremods.
In evaluating the situation I was in, it quickly became clear I could take one of three actions:
Do nothing. If I did nothing, I believe we would be watching the slow disintegration of the Forge project. This is why we recruited Curle in the first place - to try and help build a useful team, that would enable Lex to step back from the limelight and community management aspects. Her departure would cement that the Forge team was too toxic to continue to function in a viable capacity, in my opinion. We would have seen more public disputes and abuse, with more modders and community leaders becoming increasingly frustrated.
Babysit Lex. In effect, this is what I have been doing, to a more or lesser extent, for the past 10 years. He would not see it that way, but I have been defending Lex to all comers for many many years. I truly thought that if he could stop being so toxic online, we would become successful.
Do what we have done - fork the project and start afresh.
Note that due to personal physical and mental health issues, I was not well enough to continue with 2 and have rather withdrawn from the community - effectively 1 - because I needed to preserve my health. Lex has argued repeatedly that I had the power to rein him in, but that’s an accident of history and not something that I believe should have been necessary between two adult friends, and if it had killed me - a non-zero likelihood (I am not a young man) - then there would have been no one left anyway.
We have forked
Yes, we have forked the project. Curle and I both agreed this was the best decision for the future of the project and more importantly for the community - I never wanted the money or the power that comes with being leader and we have rather started the process of putting together a simple consitution for the project moving forward, which we will be sharing as time allows.
We have had to fork - because many of the core assets are licensed by Lex’s company Forge LLC. It is better for us to fork and rebrand. We will be removing those assets that are part of the MinecraftForge project, as we develop our own brand and styling.
Note that this is not a hard fork yet. We remain compatible with existing Forge for the present time. Whether we break that compatilibity in the future is one of many topics of discussion. Some want us to quickly clean up the technical debt, others feel that we should take a more measured approach to that effort. Suffice to say, both opinions have some merit and we encourage discussion and adult debate about what measures are appropriate on what timescales.
Why did this seem so rushed?
We had been in planning and discussion for around 9 days - and had a private discord setup where we could discuss the future direction and do work on initial setup and planning. This was well underway when I received the shock of my life yesterday morning - for who but Lex themselves was in our private discord, reading the backlog. The reasons for this are still unclear, and we’ll likely never know the full extent of what happened, but suffice to say, the cat was definitely out of the bag.
Faced with an unknown quantity, we felt that we had to act to quickly preserve the community, rather than risk all that has been built, especially in the past two years. Thus we launched our rebrand, before we were truly ready, but it was in effort to preserve the community.
Why did you take the discord?
The discord was always mine. I set it up very early on in discord’s life, originally as an experiment, but when it became clear that discord was getting popular, I suggested to Lex that we transition it to our new online space. At first it was secondary to #minecraftforge on esper.net IRC, but over time, it became the primary community hub. Lex was never interested in taking ownership of the server, even though I offered it several times. So it is my asset, and as my asset, I felt it best to rebrand it.
What happens now?
Things will settle as time passes. We should have our governance documents soon - we have good plans for a fresh approach to governing the project. We have had many many offers of support and help from many many community members, including corporations that run large hosting providers, distribution platforms and more. We will be setting up an opencollective for those that wish to financially support the project. That financial support will be funneled directly back into the project - we hope to be able to help our many contributors with a little pocket money for their kind donations of time.
My opinion and perspective
I want to be clear, this is my opinion and perspective. Others will have their own opinions, and they may differ in the details, but I believe this is the best possible future for the project as a whole.
I hope curle will write her perspective on the matter for publishing here.
The text was updated successfully, but these errors were encountered: