Novadegree Posted August 6 Report Posted August 6 Hello, I released my first mod about a month ago and have released a few updates to it since. My questions are about information in the description and general advice: 1) Install and uninstall instructions when users update, should these be included? Or is that common knowledge? 2) Removing the WIP statement from the description even though I am adding new content, should I have left it? 3) Update frequency, does when or why matter? If it adds something new or improves the mod? 4) The mention of other mods I feel work well with mine? 5) Reaching out to other mod authors, what's the best way? 5) Advice about the matter in general? Here is a link to My mod Empty Village Thank you.
Solution LadyWYT Posted August 7 Solution Report Posted August 7 3 hours ago, Novadegree said: 1) Install and uninstall instructions when users update, should these be included? Or is that common knowledge? A lot of it should be common knowledge, however, that doesn't necessarily mean that the player will be aware of it. I think as a general rule, instructions for installing/uninstalling tend to only be included if there are special steps the player needs to be aware of in order to avoid breaking things, especially if the mod can't be uninstalled mid-playthrough. It's not a bad idea to include instructions though, even if it's as simple as "click the appropriate checkbox in the modlist to enable/disable". 3 hours ago, Novadegree said: 2) Removing the WIP statement from the description even though I am adding new content, should I have left it? Work-in-progress labels are generally reserved for mods that are available on the download but otherwise very clearly not finished. Once the mod is considered stable and has achieved the general initial vision, the WIP label is typically removed and the mod may or may not receive new content later as the author sees fit. 3 hours ago, Novadegree said: 3) Update frequency, does when or why matter? If it adds something new or improves the mod? Adding new content, fixing bugs, adding translating, or otherwise ensuring that the mod works on a newer game version are all reasons that a mod might be updated. 3 hours ago, Novadegree said: 4) The mention of other mods I feel work well with mine? This part is entirely optional. The only time that it's not is if the mod requires other mods as dependencies. 3 hours ago, Novadegree said: 5) Reaching out to other mod authors, what's the best way? It depends on who you're trying to contact. Many, but not all, hang out on the Discord. The direct message feature on the forums is also an option, but not everyone checks the forums either. Leaving a comment on the mod page is another way. In many cases the mod page will list the mod author's preferred method of contact. 3 hours ago, Novadegree said: 5) Advice about the matter in general? If you used AI-generated assets, or otherwise used AI to assist with the mod's development(more than just a superficial use, that is), it's probably a good idea to put a polite disclaimer in the mod's description. Of course, it's not necessary to do so, but it is a courtesy to those who want to avoid such content. Overall, writing a good mod description is basically just making sure that the player has access to all the pertinent information about the mod, so they can make an informed choice on whether or not they want to use it. Including relevant screenshots alongside a general summary is a good way to explain basic functions and show the player how things look in the game.
Novadegree Posted August 7 Author Report Posted August 7 Funny how we sometimes need someone to explain our own questions to us so we can answer them. Thank you LadyWYT.
Recommended Posts