79,221
edits
Template talk:Config: Difference between revisions
Jump to navigation
Jump to search
→More Appropriate Text
| (3 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
What are you thinking it should say instead? Something like "This title has known emulation issues which cannot be worked around by configuration" for below 5 stars without any config entries? - [[User:Xerxes|Xerxes]] ([[User talk:Xerxes|talk]]) 09:32, 18 December 2017 (CET) | What are you thinking it should say instead? Something like "This title has known emulation issues which cannot be worked around by configuration" for below 5 stars without any config entries? - [[User:Xerxes|Xerxes]] ([[User talk:Xerxes|talk]]) 09:32, 18 December 2017 (CET) | ||
: Something along those lines, we at least shouldn't be indicating that non-5 start titles won't require config changes. At the same time we need to keep the phrasing vague, since presumably some 4 star titles are actually unaccounted for perfects. So some subtly is required, but probably not too hard to account for beyond the rating integration.[[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 06:25, 19 December 2017 (CET) | |||
I just made it say what it said before only for 5 star games, and changed the message for games with any other rating to "No configuration changes are known to affect compatibility for this title." That seemed general enough to me, and it removes the "run properly" part that was bugging you. - [[User:Xerxes|Xerxes]] ([[User talk:Xerxes|talk]]) 11:06, 19 December 2017 (CET) | |||
Looks good, thanks for addressing it. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 11:19, 19 December 2017 (CET) | |||
== Config List == | == Config List == | ||
| Line 14: | Line 20: | ||
: It'll need some refactoring to automatically add new option to a list and the template's code is messy at the moment. A temporary solution is creating a page and include Config template with every possible entry and then update accordingly whenever we add new options. It's a quick way to archive #2 until we refactor the template's code. [[User:mbc07|mbc07]] ([[User talk:mbc07|talk]]) | : It'll need some refactoring to automatically add new option to a list and the template's code is messy at the moment. A temporary solution is creating a page and include Config template with every possible entry and then update accordingly whenever we add new options. It's a quick way to archive #2 until we refactor the template's code. [[User:mbc07|mbc07]] ([[User talk:mbc07|talk]]) | ||
The template is changed so rarely that I've just been doing this by hand at [[Template:Config/testcases]]. Since the preview of the options on the documentation has to be updated anyways, it's really not that hard to just copy/paste the complete empty template from [[Template:Config/doc]] to the testcases page and fill in nonsense for all the options. There's no need for this kind of automation at all, nor do I know a good way to do it. - [[User:Xerxes|Xerxes]] ([[User talk:Xerxes|talk]]) 09:43, 18 December 2017 (CET) | |||
== Misalignment with Current Rev == | == Misalignment with Current Rev == | ||