Difference between revisions of "Template:Game"
m |
|||
| Line 1: | Line 1: | ||
<includeonly>'''{{{title}}}''' is {{{description}}}</includeonly> | <includeonly>'''{{{title}}}''' is {{{description}}}</includeonly> | ||
<noinclude>Title and description will go here | <noinclude>Title and description will go here {{Game Sidebar}} | ||
</noinclude> | </noinclude> | ||
== Installation == | == Installation == | ||
Revision as of 23:09, 13 March 2024
Title and description will go here
| Developer | {{{developer}}} |
|---|---|
| Performance | {{{performance_rating}}} |
| ProtonDB | {{{protondb_rating}}} |
| Available on | Steam |
| Known Issues | See Workarounds |
Installation
This section should have a uniform way of displaying commands to run, based on a user's distro choice that persists and can be easily changed. Should be similar to Android docs, such as https://developer.android.com/guide/components/intents-filters?hl=en#aria-tab-kotlin, where you can select the language right at the point where the command is viewed. The "command" function/template will contain a small list of common commands, and select the proper one to display based on the user's distro and type of command. For example, command("package_install", "wine") might display "pacman -S wine" if the user has their Distro choice set to Arch, while another user would see "apt install wine" if their distro choice is Debian. Auto-detection via user-agent string could be used to set an optimal default, respecting user choice should they wish to change it. Something such as an associative array parameter will be needed to address packages with different names on different distros.
Pseudocode example:
enum CMD_TYPE = {INSTALL, REMOVE, CUSTOM};
command(CMD_TYPE type, string value)
Support status
Brief description of the official stance from the developer, in addition to ProtonDB rating and AreWeAnticheatYet rating as necessary. Brief, vague, generalized description of issues, if any, affecting the game e.g. "XYZ runs well but crashes on some missions. See Workarounds on how to fix this."
Workarounds
A list of issues that the game has, as well as the steps to workaround them, or a related issue tracker/forum post/details about the bug and when/if it might be fixed. I'm not decided on whether this section should include specific commands, or just English language steps, because commands may need to be "translated" between multiple distro, a real headache. Or maybe the command parsing function I touched on early will be robust enough, soon enough, to handle this translation. This needs more thought.
See also
Additional links such as ArchWiki entries, developer/game website, related issues on Proton github