(译注:Slikey 是 Hytale 开发团队的技术总监,Kaupenjoe 是社区模组大使。服务端源码自抢先体验首发时就是未混淆状态。)
Slikey:
嘿 @Kaupenjoe!我正在考虑抽一些我自己的时间,也调配一些开发人员的时间,深入梳理一下现有的缺口和文档。
我听说,尤其是在对 ECS 和其他 API 的理解上,缺口还挺大的。我们可以在模组作者和开发人员之间安排一些深度访谈,来提供关键信息、具体计划,以及这些子系统的未来愿景。
哪些系统最急需,大家问得最多?我们正在收尾一些工作:Java 文档(自动更新)将在 1-2 周内完成,Github 上的源码共享将在 3-4 周内完成。
Kaupenjoe:
这个时间安排听起来太棒了,正好满足了大家反复提出的最大需求之一!一个月左右就能有文档和源码,简直太赞了!
@EverlandsHytale 团队(译注:曾经运营了一个服务器)在处理复杂的交互时遇到了很大困难。
我最近和 @PacificKB 聊过,他特别提到了 NPC 相关的短板,比如寻路、运动控制器、NPC 物品栏和编解码器,他说这些地方严重拖慢了他们的进度(完整报告下周也会出来)。
这也和 @oskarscot 写的内容吻合。
至于模组作者访谈,我有一份模组作者/团队的名单,可能你都知道他们,很适合邀请来做访谈,覆盖各种不同类型的模组应用场景!我也可以把这份名单转给你!:)
AzureDoomC:
共享源码是只在 github 上,还是会也放到 maven 上?如果能在我自己的插件里省掉用 Vineflower 反编译的步骤就好了,虽然对我本地来说,反编译也就不到一分钟的事。
Slikey:
一开始会先放到 Github 上。我会再确认一下 Maven 的事情。你说得对,我会尽量把 Maven 这边也搞定。
Buuz135mods:
我觉得源码比文档更重要,有了源码,我们就可以搜索某个功能被用在哪些地方,模组开发会简单 100%。
现在根本没法知道某个东西是干什么用的,因为搜不到它的使用场景。
Slikey:
我的意思不是说这两者只能选一个。我们在解决源码访问问题的同时,也可以为文档做贡献。只是当法务团队需要创建一个全新的授权许可时,这件事确实快不起来,因为没有现成的通用许可正好符合所有要求。
原文:
Slikey:
嘿 @Kaupenjoe!我正在考虑抽一些我自己的时间,也调配一些开发人员的时间,深入梳理一下现有的缺口和文档。
我听说,尤其是在对 ECS 和其他 API 的理解上,缺口还挺大的。我们可以在模组作者和开发人员之间安排一些深度访谈,来提供关键信息、具体计划,以及这些子系统的未来愿景。
哪些系统最急需,大家问得最多?我们正在收尾一些工作:Java 文档(自动更新)将在 1-2 周内完成,Github 上的源码共享将在 3-4 周内完成。
Kaupenjoe:
这个时间安排听起来太棒了,正好满足了大家反复提出的最大需求之一!一个月左右就能有文档和源码,简直太赞了!
@EverlandsHytale 团队(译注:曾经运营了一个服务器)在处理复杂的交互时遇到了很大困难。
我最近和 @PacificKB 聊过,他特别提到了 NPC 相关的短板,比如寻路、运动控制器、NPC 物品栏和编解码器,他说这些地方严重拖慢了他们的进度(完整报告下周也会出来)。
这也和 @oskarscot 写的内容吻合。
至于模组作者访谈,我有一份模组作者/团队的名单,可能你都知道他们,很适合邀请来做访谈,覆盖各种不同类型的模组应用场景!我也可以把这份名单转给你!:)
AzureDoomC:
共享源码是只在 github 上,还是会也放到 maven 上?如果能在我自己的插件里省掉用 Vineflower 反编译的步骤就好了,虽然对我本地来说,反编译也就不到一分钟的事。
Slikey:
一开始会先放到 Github 上。我会再确认一下 Maven 的事情。你说得对,我会尽量把 Maven 这边也搞定。
Buuz135mods:
我觉得源码比文档更重要,有了源码,我们就可以搜索某个功能被用在哪些地方,模组开发会简单 100%。
现在根本没法知道某个东西是干什么用的,因为搜不到它的使用场景。
Slikey:
我的意思不是说这两者只能选一个。我们在解决源码访问问题的同时,也可以为文档做贡献。只是当法务团队需要创建一个全新的授权许可时,这件事确实快不起来,因为没有现成的通用许可正好符合所有要求。
原文:
Slikey:
Hey @Kaupenjoe! I am considering taking some of my own time and some time from devs to have some deep dives into gaps / documentation.
I heard there are gaps especially in understanding of ECS and other APIs. We could have some in depth interviews between Modders and Devs to provide critical info, concrete plans and future vision for those subsystems.
Which systems would be most needed and what is more requested? We are finalizing some stuff right now: Java Docs (automatically updated) within 1-2 weeks and shared source on Github in 3-4 weeks.
Kaupenjoe:
The timeline on that sounds amazing, and fulfils one the of biggest requests that keeps coming up! Docs + Sources in around a month will be amazing!
The @EverlandsHytale crew had a hard time with complex Interactions specifically.
On my recent talk with @PacificKB, he highlighted mostly NPC-related gaps about Pathfinding, Motion Controllers, NPC Inventories, and Codecs, those slowed him down immensely, he said! (Full report on that coming next week too)
This also lines up with what @oskarscot wrote.
As for some Modder interviews, I have a list of Modders/teams, probably all of which you're aware of too, that would be great to reach out to for interviews with a diverse set of modding applications! I can forward that to you too! :)
AzureDoomC:
Is the shared source only on github or will it be on the maven as well? Being able to cut out decompiling via vineflower in my plugin would be nice, even if locally for me its just under a minute to do so.
slikey:
It will initially be on Github. I'll check for Maven aswell. Will try to get that delivered aswell because you are right.
Buuz135mods:
I feel like source is more important than docs, one we can search the uses for stuff modding will be 100% easier.
Right now its impossible to know what something does because we can't search the uses for it
slikey:
I mean its not really an either or. We can contribute to docs while we work on source access anyway. There is simply no speeding up creating a brand new license when a legal team needs to create it as there is no generic license out there that just fits the requirements.
Hey @Kaupenjoe! I am considering taking some of my own time and some time from devs to have some deep dives into gaps / documentation.
I heard there are gaps especially in understanding of ECS and other APIs. We could have some in depth interviews between Modders and Devs to provide critical info, concrete plans and future vision for those subsystems.
Which systems would be most needed and what is more requested? We are finalizing some stuff right now: Java Docs (automatically updated) within 1-2 weeks and shared source on Github in 3-4 weeks.
Kaupenjoe:
The timeline on that sounds amazing, and fulfils one the of biggest requests that keeps coming up! Docs + Sources in around a month will be amazing!
The @EverlandsHytale crew had a hard time with complex Interactions specifically.
On my recent talk with @PacificKB, he highlighted mostly NPC-related gaps about Pathfinding, Motion Controllers, NPC Inventories, and Codecs, those slowed him down immensely, he said! (Full report on that coming next week too)
This also lines up with what @oskarscot wrote.
As for some Modder interviews, I have a list of Modders/teams, probably all of which you're aware of too, that would be great to reach out to for interviews with a diverse set of modding applications! I can forward that to you too! :)
AzureDoomC:
Is the shared source only on github or will it be on the maven as well? Being able to cut out decompiling via vineflower in my plugin would be nice, even if locally for me its just under a minute to do so.
slikey:
It will initially be on Github. I'll check for Maven aswell. Will try to get that delivered aswell because you are right.
Buuz135mods:
I feel like source is more important than docs, one we can search the uses for stuff modding will be 100% easier.
Right now its impossible to know what something does because we can't search the uses for it
slikey:
I mean its not really an either or. We can contribute to docs while we work on source access anyway. There is simply no speeding up creating a brand new license when a legal team needs to create it as there is no generic license out there that just fits the requirements.