Hytale 共享源码计划
我们将发布完整的服务端源码、通信协议以及所有 Hytale 资产，甚至包括从未正式上线的内容！代码将托管在 GitHub 上，访问模式参考 Epic 的 Unreal Engine 源码：持有有效游戏许可并接受项目条款后，您将收到加入我们 GitHub 组织的邀请，届时可以查看、克隆并下载代码仓库。
每次正式发布和预发布都会同步更新源码。您会看到每个版本对应的分支，通过我们的 CI/CD 流水线自动推送。我们会对提交记录和作者信息做脱敏处理，原因有二：保护团队隐私，同时避免我们基于主干的高频工作流在公开历史中造成杂乱的噪声。下一步，我们会将源码 jar 包发布到 Maven，方便您直接在 IDE 中浏览代码。
关于代码贡献：我们暂时还不接受 PR（拉取请求），但未来有计划开放。坦白地说，在不严重影响自身开发效率的情况下，我们目前没有多余的精力审核这些贡献，而且在 AI 时代，提交数量会让我们应接不暇。并不是说贡献质量不好，而是数量实在太大。
我们在开源领域耕耘多年，最消磨热情的事就是 PR 长期无人回应。那样会让仓库变得乌烟瘴气，我们不想对你们这样做。保持半公开并加以许可证门槛，也有助于我们管理并减少垃圾访问，同时让法务团队安心，同时仍然让社区能够查看和使用与 Hytale 相关的代码。
具体计划如下：我们将从邀请制贡献者模式开始，面向部分社区成员。待模式验证成熟后，我们会将信任的成员提升为维护者，他们可以向团队推送 PR。当我们拥有足够信任的维护者后，就会向所有人开放贡献，并同步发布行为准则。
法律框架是其中最困难的部分。我们希望在 Hytale 生态内给予您最大限度的自由，同时阻止竞争对手直接复制粘贴我们的代码。
虽然这一过程花费了远超预期的时间，但我们很高兴终于能推出这一计划。这将使社区从反编译的灰色地带中解脱出来——无论是在开发者体验层面还是在法律层面。
访问账户界面以获取邀请：
https://accounts.hytale.com/shared-source
原文：
Hytale Shared Source - Our Plan:
We're releasing the full server source, the protocol, and all Hytale assets, even the stuff that never shipped! It will be on GitHub, with access modeled after Epic's Unreal Engine source: a valid game license and accepting the program terms will get you an invite to our GitHub org, where you can view, clone, and download the repo.
Updates ship with every release and pre-release. You'll see a branch for each, pushed automatically through our CI/CD pipeline. We strip individual commits and author data for two reasons: to protect the team's privacy, and to keep the constant churn of our trunk-based workflow out of the public history. Next up, we'll publish the sources jar to Maven so you can browse the code right inside your IDE.
On contributions: we won't accept PRs yet, but there's a path to opening them up. Honestly, we don't have the capacity to review them without tanking our own productivity, and in the age of AI we'd drown in volume. It's not that the contributions are bad. It's the sheer number.
We've spent years in open source, and nothing kills the passion faster than PRs that sit unanswered. That's how a repo turns toxic, and we won't do that to you. Keeping it semi-public and license-gated also helps us moderate and reduce spam access and keep our lawyer happy while still giving the community the ability to see and use the code with Hytale.
Here's the plan: we'll start with an invite-only contributor model for select community members. As that proves out, we'll promote the trusted ones to maintainers who can push PRs to the team. Once we have maintainers we trust, we'll open contributions to everyone, alongside a code of conduct.
The legal framework was the hard part. We wanted to give you maximum freedom inside the Hytale ecosystem while stopping competitors from copy-pasting our code.
It took far longer than it should have, but we're glad to ship it. This pulls the community out of the decompilation gray zone, for both the developer experience and the legal side.
We're releasing the full server source, the protocol, and all Hytale assets, even the stuff that never shipped! It will be on GitHub, with access modeled after Epic's Unreal Engine source: a valid game license and accepting the program terms will get you an invite to our GitHub org, where you can view, clone, and download the repo.
Updates ship with every release and pre-release. You'll see a branch for each, pushed automatically through our CI/CD pipeline. We strip individual commits and author data for two reasons: to protect the team's privacy, and to keep the constant churn of our trunk-based workflow out of the public history. Next up, we'll publish the sources jar to Maven so you can browse the code right inside your IDE.
On contributions: we won't accept PRs yet, but there's a path to opening them up. Honestly, we don't have the capacity to review them without tanking our own productivity, and in the age of AI we'd drown in volume. It's not that the contributions are bad. It's the sheer number.
We've spent years in open source, and nothing kills the passion faster than PRs that sit unanswered. That's how a repo turns toxic, and we won't do that to you. Keeping it semi-public and license-gated also helps us moderate and reduce spam access and keep our lawyer happy while still giving the community the ability to see and use the code with Hytale.
Here's the plan: we'll start with an invite-only contributor model for select community members. As that proves out, we'll promote the trusted ones to maintainers who can push PRs to the team. Once we have maintainers we trust, we'll open contributions to everyone, alongside a code of conduct.
The legal framework was the hard part. We wanted to give you maximum freedom inside the Hytale ecosystem while stopping competitors from copy-pasting our code.
It took far longer than it should have, but we're glad to ship it. This pulls the community out of the decompilation gray zone, for both the developer experience and the legal side.
