amethystlilac
commented
2 days ago For number 3, we may want to have it say If you can't find it, you may need to launch the game once because for some people, that will not solve them not being able to find it, if they just don't know where to look.
For number 6, is removing the comma needed? It may be a short list, but it could be read as 'the package is corrupt, meaning it's either damaged or locked,' and lead to confusion. And we may need a longer list somewhere, and being consistent is a good thing in my opinion
HelenTheHunter
For consideration:
1)
<data name="CatalogDisplay_IncompatiblePack_NotInstalled_Tip" xml:space="preserve">Is this needed? If it is needed, change to "{0} requires that {1} is NOT installed. You do NOT have {1} installed. This message is for information only, you do not need to make any changes."2)
<data name="CatalogDisplay_RequiredPack_Installed_Tip" xml:space="preserve">Is this needed? If it is change to "{0} requires that {1} is installed. You do have {1} installed. This message is for information only, you do not need to make any changes."3)
<data name="FoldersSelector_ValidateUserDataFolder_NoOptionsIni" xml:space="preserve">Change to "Hey, Silly! That's not your Sims 4 User Data Folder. 😏 If you can't find it, you may need to launch the game once then exit and try again..."4) Change "Script Archive" to "Script File" or ".ts4script file" for every use of that phrase. I know script files are archives but most users don't and we want less confusion not more.
5)
<data name="ManifestEditor_Hashing_Warning" xml:space="preserve">Change to "The inclination to increase this setting because the thought of players altering your mods upsets you is valid; but please do consider that some players may have a good reason for this, such as using your mod in a language for which you do not provide a translation, and arbitrary strictness here will punish them when that may not be your intention."6)
<data name="ManifestEditor_Error_InaccessiblePackage_Caption" xml:space="preserve"><value>Package corrupt, damaged, or locked</value>and<data name="ManifestEditor_Error_InaccessibleScriptArchive_Caption" xml:space="preserve"><value>Script archive corrupt, damaged, or locked</value>Remove 2nd comma7) ```
Do we want to explain somewhere why there are references to the marmot? Some sort of clickable link, tooltip or easter egg for the curious to checkout?
8)
<data name="ManifestEditor_Confirm_Note_BlankPromoCode" xml:space="preserve">Change to "Your mod requires packs which some players may not have, but might purchase specifically to use with your mod. If you have an EA Promo Code you really should be using it, don't go leaving money on the table like this, friend. Consider doing yourself a solid, heading back to the Requirements step, and filling in that code.<br />{0}If you don't have one, but you're interested in getting a commission for all the packs your awesome mod is about to help EA sell, please allow me to direct you to where that journey begins."9)
<data name="ManifestComponentEditor_ManifestSnippetTuningResourceName_HelperText" xml:space="preserve">Change to "Because this component of your mod is a package file, its manifest will be a snippet tuning resource in your package. This is the name of that resource and it should be unique. I will generate the full instance for the snippet tuning resource on my own using the Sims 4 modding community standard implementation of the 64-bit Fowler–Noll–Vo hash function with the highest-order bit set. You can change it if you are feeling brave, but make it unique."10)
<data name="ModFileSelector_SelectAModFileManifest_Info_MultipleManifests_Text" xml:space="preserve">Change to "This is embarassing, but because some bozo merged their files and didn't update the manifests 🤦, I'm going to have to ask you to select precisely which of the multiple manifests in this mod file you want to use. {0}{1}"