Template talk:GlobalProblems/Virtual Console

Too broad?
This template seems too broad to be useful. It also hasn't been used in game pages like the global problem templates of each VC system does; these are already sufficient and easy to maintain. I'm fine with seeing this template go honestly. Lucario (talk) 02:44, 15 August 2017 (CEST)
 * Apparently, after reviewing the codes behind template:GlobalProblems, this template will be called in virtual console game pages when there's a new issue for it. Still, it wouldn't be too hard to copy/paste the problem entry into each template of the affected VC system. Lucario (talk) 02:59, 15 August 2017 (CEST)
 * I'm completely against removing it. The whole GlobalProblems and its subtemplates were made to avoid duplicating common entries in different places and to get changes made here or in any of the subtemplates instantly reflected on all applicable pages, and I personally think they serve this purpose very well. Dolphin got more accurate as the development continued, and even through we never relied on GlobalProblems/Virtual Console that much, I still prefer to have it around if we ever need it in the future than having to duplicate whatever entries that could be put here on any of the other GlobalProblems subtemplates, which would go completely against all the reasons that made us develop GlobalProblems on the first place. Plus, having this template around actually doesn't add any maintenance burden at all, so there's really no benefit in purging it, we would just be losing functionality without winning anything in return - mbc07 (talk) 06:17, 15 August 2017 (CEST)
 * Of course, the GlobalProblems template and its subtemplates for each VC system are very important to have, but with them around, this template isn't much to me. I don't think the loss would be too devastating with this template purged either. For example, it's going to be extraordinary for us to even find issue that applies to all Virtual Console either way, and even if so, the GlobalProblems for each VC system can relay the duplicate problem information into game pages pretty well. I had the urge feel to purge out Virtual Console to feel consistent with Main Page... well, idk. Lucario (talk) 09:00, 15 August 2017 (CEST)
 * If that's your only motivation for purging this template, I still prefer making it hidden by default (just like in the game pages), adding the section in Virtual Console only when we have active entries than completely purging it. It's actually very easy to do that. - mbc07 (talk) 05:11, 16 August 2017 (CEST)
 * You could make GlobalProblems completely consistent on platform pages with the way it works on game pages like this, only adding a header when necessary, or just remove the header from Virtual Console only and add a check to GlobalProblems to add it back when there's a problem, like this. The first one seems cleaner to me than page specific behavior. Actually if you make the behavior the same between both types of pages, you could collapse a lot of this code. You could take out the whole switch statement and page type checks and just have this. - Xerxes (talk) 08:10, 16 August 2017 (CEST)
 * Well it's going to feel cleaner to have this template purged as well. The codes meant to call VC subtemplate can be "hidden" in GlobalProblems' edit history for performance reasons and the subtemplate itself can be recreated quite easily. You can come back and prove me wrong that they were necessary all along that there's a new problem that actually needs to relay in all VC pages out there, hmm? Lucario (talk) 09:25, 16 August 2017 (CEST)

I kind of understand removing it since it's been empty for four years and the Virtual Console page looks a little less attractive with the blank header, but since there were actual global VC problems in the past which spurred having this template, conceivably it could happen again. I'm not really in a position to make a prediction like that, though. - Xerxes (talk) 09:31, 15 August 2017 (CEST)