Leaderboard

I actually think this is a solid idea. I would take this a step further and use this to point out if the EXE is in a subfolder as well (example: {{P|game}}\Binaries\Danielle\x64\Release\Prey.exe) Normally I would also say that Installation Folder isn't all that helpful, but there are some edge cases that are... unreasonable. Most notably, you may have trouble finding Mega Man Legacy Collection 1 in your Steamapps\common folder. That's because it's called Suzy. I could see it being standard practice to have an {{ii}} under game data if the folder has a strange name such as this, or note that every game in a collection has its own data stored in a dedicated subfolder. It would probably be best as a table in #Game_data as @SirYodaJedi suggested, with Mac/Linux file names directly below the Windows EXE.

After extensive discussion, I think we're close to finalize the details of how we would cover it best. The way I see right now is a multi-parameter approach like the DualShock 4 parameters under input, where we both track support (native, hackable, etc) separately from the mode supported itself (DirectSound3D, Windows Spatial, etc). Inputting e.g. "EAX" into the mode field would interpret it as DirectSound3D and show it as such.

While I agree that the way we had series hindered pages in large franchises, I definitely would like something verbose like this at the bottom of the page to be able to quickly navigate between pages: https://tcrf.net/Category:LEGO_series It helps SEO, too.

Overhauling the editing guide sounds too encompassing 🙂 What I think is needed is that we simply go into more detail about the various parameters that allows true/limited/hackable/false values, with the focus being on Video and Input sections primarily, with the Audio section secondarily. A few example discussion points: 4K parameter seems heavily tied to 16:9 at the moment. Should preferably not be tied to any particular aspect ratio and more in general deal with whether a game can run at the 4K resolution of whatever aspect ratio the game is designed for (3840x2160 for 16:9-designed games, 3840x2400 for 16:10-designed games, 3840x2880 for 4:3-designed games). Repurpose multi-monitor parameter somehow, since right now it tends to mean "wider aspect ratio than ultra-widescreen". The "main element" of multi-monitor gaming today is AMD Eyefinity and Nvidia Surround, which isn't really relevant to the game itself, as all of that logic is separate from the game. Possibly repurpose to real multi-monitor support? As in games that allows the use of a secondary monitor for minimaps, view etc? Real native multi-monitor support, that is, without involving AMD Eyefinity or Nvidia Surround? Generally make it clearer whether a parameter means that a game have an option for toggling something vs. supports something. Right now the difference isn't always clear, which can cause new editors to interpret some parameters incorrect (e.g. should "mouse acceleration" be set to true or false if mouse acceleration is used, but no option is available to adjust it?) New parameter(s) in Audio settings detailing spatial audio support and possible tech required to enable it. Either replacing the existing EAX support field, or supplementing it somehow. The above is just a few examples that can be discussed. Past that, we should add abbreviations (hover explanations) to all of the parameters in the tables with a short and concise description of what the parameter tracks to make it easier editing without having to visit the Editing Guide. Some parameters already have this, and it simply needs to be extended to the rest after the discussions about what the parameters should actually mean have finalized.