Facing legacy issues

English

面对历史遗留问题

wiki 版本：0.0.8.0

从历史一脉相承的窘境、无法统一的矛盾冲突，到掌握改造代码的力量。

直视问题，才能开始解决问题。

一个模组：

• 不会永远保持在最初的样子
• 不可能同时满足所有人的需求
• 不会因为玩家提出需求就自动更新

⏩模组如何延续？

一个模组要持续发展，现实往往不尽如人意：

• 💔兴趣消失：当开发者兴趣消散，模组随时面临停更的风险
• 😕没有文档：开发者没留下文档，后来的维护者苦心钻研
• 😥门槛太高：玩家想参与贡献，却被开发技术直接劝退

这些问题交织在一起，还会引发连锁反应：

• 💥当模组出了问题，谁能修复它？
• 🙁没人懂其中的技术，模组是否还能维护？
• 🤖用 AI 写代码，人能不能看懂？

很多时候，问题不在于技术有多难，而在于开发者没有为后来者铺路：

• 💪项目的“经验老人”有经验和熟练度，而新人却在外围摸索
• 👴模组没有新鲜血液的接力，原开发团队却逐渐老去
• 🤑当模组形成稳定的利益关系后，也可能会阻碍后来者参与

⚔️面对不可调和的冲突

开发者的精力是有限的，而玩家的需求是无限的：

• 🤷一个模组不可能同时满足所有人的需求
• 🫠开发时既要权衡各玩家群体的需求，又需要社区的力量来弥补人手的不足
• 🌐因此，社区中不乏扩展模组、兼容模组、移植版、魔改版/定制版

当不同声音碰撞在一起：

• 😬玩家等不及开发者的更新速度，有什么解决办法？
• 💬对模组设计的意见不同，如何公开开展讨论？
• ❌维护者不接受合并请求，多样的需求如何满足？

面对冲突，需要厘清几件事：

• 📢Issue 光说不做，谁需要为此解决问题？代码不会凭空变出来
• 👑维护者可以决定最终采用的方案，但总有时候无法“既要又要”
• 🚨代码没有量子力学，一个版本里无法同时存在两套互相冲突的逻辑

有些需求可以通过讨论解决☺️，而也有无法在同一个模组中实现的😓

不存在完美的方案能同时解决互斥的需求，因此需要多一种选择：

• ⚖️如果模组开源许可证允许，则可 fork 出新的项目，开辟新的道路
• ✨让不同的理念各自发展，让不同版本满足不同需求

✊掌握改造代码的力量

如果别人不改，别人不教，那该怎么办？

谁来解决“参与者想参与却力所不及”的问题？

自己学会做模组，就是答案之一。

开发者和玩家指出问题很重要，但问题最终还需要有人解决：

• 🧑‍💻批判的代码当然不能替代代码的批判，代码只能用代码来解决
• 📄文档和教程能让更多人获得改造代码的能力
• 掌握了改造代码的能力，就能开始着手对模组的改造，实现不同的想法和需求

🤤🙅不要祈祷别人总能满足你——独立自主，自己动手丰衣足食🌟

📜留下可以接手的东西

历史问题总会出现，但可以减少遗留给后人的问题：

• 📄重要的开发经验写下来，避免只存在于某个人的脑子里
• 🗂️保持清晰的目录和代码结构，方便别人浏览
• 🔎遇到奇怪的问题时，尽可能提供信息，相信后人的智慧

这些事情并不能保证模组永远有人维护；但这些就是引导后来者开始的起点和动力：

• 留下经验，就是给后来者铺路

当你踩过一遍坑，把答案留下来，比让下一个人重新踩一遍更有意义。

如果现成的答案不存在，你可以逐渐成为那个提供答案的人☀️

📚引用文献

“哲学家们只是用不同的方式解释世界，而问题在于改变世界。”——卡尔·马克思《关于费尔巴哈的提纲》

“批判的武器当然不能代替武器的批判，物质力量只能用物质力量来摧毁；但是理论一经掌握群众，也会变成物质力量。理论只要说服人，就能掌握群众；而理论只要彻底，就能说服人。”——卡尔·马克思《黑格尔法哲学批判》导言

English

wiki version: 0.0.8.0

From long-standing problems and unresolvable conflicts, to mastering the ability to refactor code.

Only by facing problems head-on can we begin to solve them.

A mod:

• Will not stay the way it started forever
• Cannot satisfy everyone's needs at the same time
• Will not magically update just because players ask for something

⏩How can a mod keep going?

For a mod to keep developing, reality often falls short of expectations:

• 💔Losing interest: When a developer loses interest, the mod risks stopping updates at any time
• 😕No documentation: If the developer leaves no documentation behind, future maintainers have to figure it out the hard way
• 😥High barrier to entry: Players may want to contribute, but are scared off by technical barriers

These problems can also lead to a chain reaction:

• 💥When something goes wrong with the mod, who can fix it?
• 🙁If no one understands the technology behind it, can the mod still be maintained?
• 🤖If AI writes the code, can people still understand it?

Most of the time, the problem isn't that the technology is difficult. It's that developers didn't pave the way for those coming after:

• 💪"Veterans of the project" have all the experience and fluency, while newcomers are left trying to find their way from the outside
• 👴Without fresh blood to take over, the original dev team gradually moves on
• 🤑Once a mod forms stable financial interests, it may even block newcomers from getting involved

⚔️Facing unresolvable conflicts

Developers have limited time and energy, but players' demands are endless:

• 🤷A mod cannot satisfy everyone's needs at the same time
• 🫠During development, you have to balance the needs of different player groups, while also relying on the community to help make up for the lack of people
• 🌐That's why the community has many addon mods, compatibility mods, ports, and custom/tweaked versions

When different voices clash:

• 😬Players can't wait for the developer to update the mod. What can they do?
• 💬People have different opinions about the mod's design. How can they discuss them openly?
• ❌Maintainers don't accept pull requests. How can different needs be satisfied?

When facing conflicts, a few things need to be cleared up:

• 📢Opening an Issue doesn't solve the problem by itself. Who actually steps up to fix the problem? Code does not appear out of nowhere
• 👑Maintainers get the final say on which approach to take, but sometimes you just can't "have your cake and eat it too"
• 🚨Code isn't quantum physics. Two conflicting pieces of logic can't exist in the same version at the same time

Some needs can be resolved through discussion☺️, while others simply can't be implemented in the same mod😓

There is no perfect solution that solves mutually exclusive needs, which is why we need another choice:

• ⚖️If the mod's open source license allows it, fork a new project and blaze a new path
• ✨Let different ideas develop separately, with different versions serving different needs

✊Mastering the ability to refactor code

What if nobody else changes it? What if nobody else teaches you how?

Who is going to solve the problem of "people want to participate, but don't have the ability to do so"?

Learning to make mods yourself is one answer.

It's important for developers and players to point out problems, but at the end of the day, someone still needs to solve them:

• 🧑‍💻The weapon of criticism cannot, of course, replace criticism of the weapon. Code can only be changed with code
• 📄Documentation and tutorials help more people to gain the ability to refactor code
• Once you master the ability to refactor code, you can start changing the mod yourself and bring different ideas and needs to life

🤤🙅Don't pray that others will always satisfy you — learn to do it yourself and build what you need🌟

📜Leave behind something others can take over

Historical issues will always pop up, but we can reduce what gets passed down to those who come after us:

• 📄Write down important development experience so it doesn't just live in someone's head
• 🗂️Keep a clear directory and code structure so it's easy for others to browse
• 🔎When running into weird issues, provide as much info as possible and trust the wisdom of those who follow

These things cannot guarantee that a mod will always have someone maintaining it; but they serve as the starting point and motivation for newcomers:

• Leaving behind experience is paving the road for those who follow

Once you have fallen into a pit, leaving the answer behind is much more useful than making the next person fall into the same pit again.

If there is no ready-made answer, you can gradually become the person who provides one☀️

📚References

"The philosophers have only interpreted the world, in various ways; the point is to change it." — Karl Marx, Theses On Feuerbach

"The weapon of criticism cannot, of course, replace criticism of the weapon, material force must be overthrown by material force; but theory also becomes a material force as soon as it has gripped the masses. Theory is capable of gripping the masses as soon as it demonstrates ad hominem, and it demonstrates ad hominem as soon as it becomes radical." — Karl Marx, Critique of Hegel's Philosophy of Right Introduction