Template talk:Gecko

Allowed Categories
There may be one other allowed classification. A small subset of codes may be used to work-around bugs or emulation issues beside problems with the widescreen, though I'm not clear if any of these sorts of codes still exists (i.e. fewer are needed with our more accurate emulation). In any case a "bugfix" category may be appropriate. Kolano (talk) 21:16, 31 December 2017 (CET)
 * It's going to be difficult to correctly flag cheat code as bugfix because there's arbitrary way how it's called, and anyone can flag it as bugfix with their malicious edits. Just say it's not 16:9 or 60FPS will allow us to patrol those codes.
 * Actually, if you mean that we can rename "Not 16:9 or 60FPS" category into "bugfix" and they work the same way, I'm up for it. Lucario (talk) 21:59, 31 December 2017 (CET)

The only pages I know of that use patches to fix bugs right now are Mario Kart Arcade GP and Mario Kart Arcade GP 2. There's handling for it in Template:Config as well, but I don't think that's ever been used. - Xerxes (talk) 04:26, 1 January 2018 (CET)

Regions
Though the vast majority of titles can be classified with NA/JP/EU, there are other regions and sub-divisions (i.e. EU language releases, special editions, etc.). May want to handle it more generically allowing GameIDs to be fed in as identifiers (more generic region identifier names could likely be determined through the 5th character). Kolano (talk) 21:32, 31 December 2017 (CET)


 * I agree that users who submit new codes should be forced to specify what ID those codes are for. I think this is a healthy change. And yes, they don't always split into nice regions. There's always weird exceptions, even a high profile game like Super Mario Galaxy 2 had a Chinese language release for example. I would be in favor of this to the point of even including duplicates of the same codes on a page just to show that the codes work with each GameID for a title. The only problem with enforcing this would be that there would be some ambiguity with what ID existing codes are for, but that's not a problem with the Gecko template, that ambiguity has always existed. - Xerxes (talk) 04:22, 1 January 2018 (CET)

Quality Categories
If you want to turn gecko codes into a template (not a bad idea), it might be good if you're going to try and integrate quality checks to hook it into Template:Problems/GC Widescreen Auto and Template:Problems/GC Widescreen 16-9. If the game supports 16:9 already but also has widescreen codes for whatever reason, then the template should generate flags to show that the widescreen gecko codes aren't needed. That would give the template tangible benefits rather than just style compared to the current way of doing it. I don't know how to handle that with Wii though, but I don't really know how widespread the creation/desire for widescreen Wii codes is when most games already support it (I think?). - Xerxes (talk) 04:17, 30 December 2017 (CET)
 * Good idea, if this new template is going to make it to game pages then we can add additional qualility checks regarding games that already support widescreen. We may like another category for whether it's used in Wii game pages. Lucario (talk) 03:29, 31 December 2017 (CET)