Important reminder for everyone who makes submods #7844
Booplicate
announced in
Announcements & Releases
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Important reminder for everyone who makes submods.
When you make a public submod, please, thoughtfully test every path in your topics before releasing it to people. I'll ask to pay special attention to delicate things like affection changes/rare events/existing variables changes/different unlocks/etc in your code.
We had a number of issues where some submods unlock events (spoiler, but for example: first kiss) much, much earlier than they should be unlocked. You ruin this sweet one-time event for people, and which is worse nor you nor we can even fix it. So people will never get to see/experience the proper event.
I'll also say that you should not unlock such things in your submods and leave it to official mod content. That's because we have our expectation of when and how those one-off events happen, and more things depend on it when we're adding more content. Once your submod interferes, the entire system breaks.
For affection, if you change the numbers a lot, not only it's harder for us to account for, but also people will skip entire stages of the mod, which they will never be able to experience again. Don't take it away from people, let them enjoy the mod.
Those are just a few examples of the issues we saw. Making submods is cool, it's fun and we all like them, but it's also a responsibility. Please, test your code! And for those who use submods, daily reminder to make backups, particularly when you install a new submod.
Beta Was this translation helpful? Give feedback.
All reactions