User talk:Tiddlywinks/Archive 3: Difference between revisions

:I've edited the sections to address your most fundamental concern. The new wording should, perhaps, imply to anyone with a modicum of know-how that they don't have to lose the save (although if they have a modicum of know-how, they probably don't really need such a hint anyway). I'm still very uncertain that in-depth work-around instructions are needed, especially when potential "liabilities" are considered. (In a sort of informal sense, at least. It wouldn't be great if someone had cause to accuse us of breaking their game.) [[User:Tiddlywinks|Tiddlywinks]] ([[User talk:Tiddlywinks|talk]]) 15:26, 23 January 2017 (UTC)

::I agree on the technical part. Thank you for attempting to address the issue. I referred SnorlaxMonster to this discussion, although I was considering moving it entirely to either article's talk page. The articles still mention GameShark as a utility for backing up a save. GameShark isn't a brand owned by Nintendo so I find it a little comical that they come across as a more legitimate way of preserving a save file than does replacing the battery, which is non-invasive code-wise. GameShark is obviously non-invasive hardware-wise, but even though you preserved a save file this way you'd still need to replace the battery anyway (which the article correctly states). I'm probably repeating myself but one solution could be to change the wording "{...}''will'' cause any current save file to be lost" to something tad milder. For example "Since it powers the save file, interrupting the power by removing the battery will cause any current save file to be lost '''unless the memory remains powered by external means'''." --[[User:Black Eagle|Black Eagle]] ([[User talk:Black Eagle|talk]]) 16:38, 23 January 2017 (UTC)