Template talk:Infobox VG/sandbox

ID Verify

Chiming in on the recent ID Verify update. I'm not clear it's a particularly good solution, as it seems to depend on the verifier being a reliable source, which likely isn't a safe presumption over the thousands of IDs to verify. Something like a method to provide an outside URL confirming each ID would probably be preferable. I'm not clear about the mechanics, but perhaps we could also work out pulling in things like the language details that have been populated on redirect pages.

If not possible through standard wiki mechanics, I'm guessing some JavaScript as I'm hoping to implement to restore random videos might be able to handle it. Kolano (talk) 08:08, 29 December 2017 (CET)

After taking another look at it, I don't think I liked my old design either, it seemed tacky. This new version tries to consolidate everything to the GameIDs section instead of adding a new section. All that it does is look for a variable in the page's infobox that matches the name of each ID, and if there's a match then it links to wherever that variable says to instead of to the redirect page like it normally does; if there's no match for one or more IDs, then it adds the page to the unverified IDs category. For example, on page Atlantis no Nazo, if I were to confirm that page's ID FEAJ01, all I would have to do is add the line |FEAJ01 = <NUS link> and the link in the infobox under the GameIDs section would take you to the NUS. (Ironically a bad example since FEAJ doesn't have a download from NUS...) There's a demonstration on the Dummy Page so you can see what I mean.

The ultimate goal would be to have a system with some kind of small checkmark icon next to verified IDs and an X next to unverified IDs in the infobox and make the checkmark what links instead of the ID itself, but I'd need to go find some public domain icons and figure out how to do that visually. - Xerxes (talk) 10:27, 29 December 2017 (CET)

I wanted to try and do the information on the ID redirect page as a hover over for IDs in the infobox, but I don't know how to do that. Trying to transclude a redirect just gives you the contents of the page it redirects to. That's how redirects work for template names so it's core to MediaWiki that it does this. - Xerxes (talk) 09:44, 2 January 2018 (CET)

How to retrieve parameter information from Template:Config to Template:Infobox VG?

My goal is to output "(480p no AA)" after rating text if it detects these existing parameter(s): antialiasing, anisotropic filtering, and/or internal resolution in the configuration template. Can this be done at all? I'm not sure if #var_final is working or I'm doing it wrong.

Okay, my actual goal is to drop pixelated stars while retaining these parentheses. Lucario (talk) 10:46, 6 July 2017 (CEST)

Is it still good idea to have these parentheses after rating text though? The question above won't matter anymore if the parentheses are not going to make it out of the sandbox anyway. Lucario (talk) 11:06, 6 July 2017 (CEST)

You can detect the existence of a config entry by using #ifpageincat on the categories in Category:Config Required. That doesn't get you any of the actual information entered within, just whether or not that parameter is set to something or not. That was how I was able to get platform information from the page categories to automate that part of the infobox. Though, the standard right now as I understand it is to not use any config entries for problems with enhancements, since config is reserved for issues with default settings. - Xerxes (talk) 10:02, 2 January 2018 (CET)

We've also allowed for enhancement related settings when such result in known issues. such as filtering options scrambling video; though it's not handled consistently. Kolano (talk) 10:19, 2 January 2018 (CET)

Oh, great, thanks! But how can I use that method for blue stars since there'd be too many different categories? Feeling hopeless for 480p no AA stars. I wish that "default vs non-default" rule doesn't apply to the built-in enhancement settings. Lucario (talk) 03:57, 3 January 2018 (CET)

You can do {{#ifpageincat:antialiasing|{{#vardefine:bluestars|true}}}} and duplicate it a few times for each category. Then do an {{#if:{{#var:bluestars}}|blue stars|regular stars}} later on to access it and wrap that around the styling for the stars in the infobox. I haven't looked too closely at the rating stars but that's the basic skeleton I would use. You can even stack the #ifpageincats inside of each other like the platforms section does, but that can hurt readability; only did it there because there were so many that doing all those checks every single page seemed stupid. - Xerxes (talk) 04:54, 3 January 2018 (CET)

Um, what is the point of this additional parenthetical? I'm guessing that there's a lot of details here that either aren't or can't be accounted for. For instance...

• 480p is only the resolution for many NTSC titles. There are a lot of GameCube / Wii rendering modes, and many are not using 480p. It's been a while since I took a closer look, but the most common case is likely PAL titles (i.e. PAL is 576p).
• We long established that "enhancement" settings should have no impact on ratings.
• Negative outcomes from AA, Anti-aliasing, Texture Filtering, Higher IR vary wildly. Some so minor they wouldn't effect a rating, others completely game breaking.

This probably needs some discussion before you spend a lot of time on it. Kolano (talk) 05:24, 3 January 2018 (CET)