Workaround templates for issues

Hi, RedDevilus! I have an idea for streamlining workarounds for issues on game pages. I'm creating a handful of templates which contain instructions for a common workaround. Some contain a single parameter for flexibility's sake, e.g. you can use '{{Renderer hacks|Hack name here}}' such that there doesn't have to be a unique template for every single renderer hack. This is a work-in-progress and could become more sophisticated, but it's pretty basic right now.

On its face, this may not seem like a big deal. It saves a bit of typing and a few dozen bytes on a page; so what? However, what makes this really useful is that updating the template globally updates every instance where it's used. So for example, if 1000 articles have a workaround where you need to enable a renderer hack, but the path to the renderer hack changes and obsoletes those workaround instructions, you can just update the template and globally fix all 1000 instances. TheTechnician27 (talk) 03:52, 9 February 2022 (UTC)