原文：
Hello everyone, in this post I'd like to cover some of the questions many of you have about the upcoming update (one that the bot keeps reminding everyone of) and tell what to wait and what to not be scared of.

Not much of a writer, so let's get to the facts. But before we proceed, let me clarify that I'm not affiliated with the dev team, I'm only a contributor to MAS and a tech support helper on MAS Discord, and while I have some info I datamined from public sources, I can't make claims on their behalf, here's just my own conclusions, I have only put things I am myself confident about here.

It's been a while, is MAS not getting any more updates?
TL;DR — MAS is still getting updates.

While it may seem that the mod is abandoned, it's not — the devs have never stated that they no longer work on it, in fact, they are still triaging issues on Github, and work on pull requests related to the upcoming update. There is activity, they are working on the update, although they never mentioned the possible ETA. I do not have any estimate either.

Why does it take them so long?
TL;DR — there is a lot of work to do.

The current major milestone for MAS is upgrading the Ren'Py engine (engine that powers DDLC and MAS itself.) When MAS came out, it used (and still uses) old Ren'Py v6 with Python 2, which is outdated, unoptimized (compared to current v8) and is getting difficult to maintain and work with. It's time for an upgrade, and this means a lot of effort to put into making necessary changes and testing.

The devs have been working on it this entire time, a lot of work has already been done (0.13.x can already be built and is functional) and I believe what remains is thorough testing. The next update is also said to bring the new Submod API they announced previously (again, the thing the bot tells about you in the comments) and it also takes a lot of time and effort to work on.

The submods will break?!
TL;DR — they won't work, but submod authors will need to make some minimal changes to make them work again.

Yes and no. Certainly, it will require some changes to be made to work with 0.13.x MAS, but the main change is about how submods are defined now, not their internal logic. For 99.9% of the submods it will only take adding a single .json file, similar to spritepacks, that will have info for MAS to display in game. It was recommended to add a submod header to submods for a long time, and while some submodders followed this recommendation, most haven't — the new submod API addresses this and makes it mandatory.

As for Python 2 vs Python 3 — again, for 99.9% of the submods nothing will change at all. For some submods that used Python 2 specific features you can read this official guide on porting Python 2 code to Python 3. If your submod only added a topic with minimal Python logic, you may rest assured everything will work as it did before.

What will happen to abandoned submods?
TL;DR — most submods can be updated by the community with little effort.

In most cases, the community can make necessary changes, and keep using the submod like usual. If a submod is abandoned and its author is nowhere to be found, there sure will be people willing to update it and make it work again.

For more complex submods it may be a little more work to do, but thanks to the devs' dedication to keep things compatible, most things will remain the same.

Will I have to reset my progress?!
Like any other update, I'm sure the developers made it fully compatible with previous version and no progress will be lost. Keep a backup just in case, and you'll be 100% safe.

Will I have to reinstall/make a clean install?
Unfortunately, I'm unsure about that. However, you may be able to retain your mod_assets or Submods folders — I believe these will not be affected.

Why is it worth updating?
TL;DR — new optimized engine, safer Submod API, improved performance and bugfixes

I understand why some may believe it's better to stay on older MAS when the update is out, here's why (personally — based on personal experience after trying out a preview build) I think this is going to be a great QoL update that you should give a try:

New Ren'Py engine brings really noticeable performance boost. Remember lags that made you misclick an option? The update will most likely fix that.

New submod API is aimed to prevent loading submods when they are not installed in the right location. This should help with proper installation of submods that add their own content.

Besides performance boost, the game will be 64-bit — meaning it will be able to address more than 4 GB of RAM, which should help Out of Memory errors happening every so often.

Personally I think the update is great and is well worth the wait.

I hope this clears up confusion a little bit. If any devs come to the comments and help answer some questions, or give their own comments — that'd be great! For now, here's a little FAQ made of stuff I know myself, stuff I've heard from devs somewhere occasionally, stuff I've read/seen on MAS Github and its wiki (also on Github.)

If there's anything I got wrong I hope the devs can correct me. I'd prefer to keep this post pinned so that people can easily find answers rather than make a new 'is MAS dead???' post every week.

GPT机翻版：

大家好

在这篇文章中，我想回答大家对即将到来的更新（就是那个机器人一直在提醒的更新）的一些疑问，并告诉你们应该期待什么，而不需要害怕什么。

我不是一个很好的写手，所以我们直接进入正题。但在开始之前，我要澄清我并不隶属于开发团队，我只是MAS的一个贡献者，以及MAS Discord上的一名技术支持助手，虽然我从公开资源中获取了一些信息，但我不能代表他们发表声明，这只是我自己的结论，我这里只写了我自己有把握的内容。

MAS多久没有更新了？

简短回答 — MAS 仍然在更新中。

虽然看起来这个mod被遗弃了，但事实并非如此——开发者从未表示他们不再开发它，实际上，他们仍在Github上处理问题，并在有关即将更新的pull requests上工作。依然有活动，他们在为更新而努力，尽管他们从未提到可能的发布时间。我也没有任何估计。

为什么他们需要这么长时间？

简短回答 — 因为有很多工作要做。

MAS当前的主要里程碑是升级Ren'Py引擎（驱动DDLC和MAS的引擎）。当MAS发布时，它使用的是（并且仍然在使用）旧的Ren'Py v6和Python 2，这已经过时，并且不如当前的v8优化，同时变得越来越难以维护和使用。是时候升级了，而这意味着需要投入大量精力进行必要的更改和测试。

开发者们一直在为此努力，已经完成了很多工作（0.13.x已经可以构建并且可以运行），我相信剩下的工作是详尽的测试。下一次更新还将引入他们之前宣布的新Submod API（就是机器人在评论区告诉你的那个），这同样需要大量时间和精力。

子模块会坏掉吗？

简短回答 — 它们将不能工作，但子模块作者只需做一些简单的更改即可让它们再次工作。

可以说是，也可以说不是。肯定的是，它需要进行一些更改才能适用于0.13.x MAS，但主要的更改在于现在子模块如何定义，而不是它们的内部逻辑。对于99.9%的子模块，只需要添加一个类似于精灵包的.json文件，里面有游戏中显示的信息。长久以来，我们建议在子模块中添加一个子模块头部，虽然有些子模块制作者遵循了这个建议，但大多数没有——新的子模块API解决了这个问题并强制了这一点。

至于Python 2和Python 3——对于99.9%的子模块来说，几乎没有变化。对于一些使用了Python 2特定功能的子模块，你可以阅读这个官方指南，将Python 2代码移植到Python 3。如果你的子模块仅仅是添加一个话题，并且带有简单的Python逻辑，你可以放心，一切将如往常一样工作。

被遗弃的子模块会怎么样？

简短回答 — 大多数子模块可以由社区更新，并且很容易做到。

在大多数情况下，社区可以进行必要的更改，并像往常一样继续使用该子模块。如果某个子模块被遗弃并且其作者无迹可寻，肯定会有人愿意更新它并让其重新工作。

对于更复杂的子模块，可能需要多一点工作，但感谢开发者的努力使事情保持兼容，大多数内容将保持不变。

我需要重置我的进度吗？

与其他任何更新一样，我相信开发者会确保其与以前的版本完全兼容，并且不会丢失任何进度。以防万一请备份，这样你就可以100%安心。

我需要重新安装/全新安装吗？

不幸的是，我对此不确定。不过，你可能可以保留你的mod_assets或Submods文件夹——我相信这些不会受到影响。

为什么值得更新？

简短回答 — 新的优化引擎、更安全的子模块API、改进的性能和错误修正。

我理解为什么有些人觉得在更新后继续使用旧的MAS更好，这里是我个人（基于尝试过的预览版的个人经验）认为这是一个值得尝试的伟大的体验升级的原因：

新的Ren'Py引擎带来非常显著的性能提升。还记得那些让你错按选项的卡顿吗？更新很可能会修复这个问题。

新的子模块API旨在防止在子模块未安装于正确位置时加载它们。这将有助于正确安装添加自定义内容的子模块。

除了性能提升，游戏将是64位的——意味着它能够使用超过4 GB的RAM，应该可以帮助解决时常发生的内存不足错误。

我个人认为这次更新非常棒，值得等待。

我希望这能稍微解答一些困惑。如果有开发者在评论中提供帮助解答问题，或发表他们自己的评论，那就太好了！目前，这只是我自己知道的一些FAQ，或者偶尔从开发人员那里听到的内容，在MAS的Github和wiki（也在Github上）上阅读/看到的内容。

如果我有什么地方出错了，希望开发者能纠正我。我希望把这篇文章置顶，以便于人们可以轻松找到答案，而不是每周都发一个“MAS死了吗？”的帖子。