Project:To Do

From Dolphin Emulator Wiki
Jump to navigation Jump to search

Here is a list of stuff that needs doing on the wiki. Feel free to add anything you feel that needs to be done.

Regular tasks

These are regular tasks. Please do not remove them or mark as complete, as they need to be checked regularly.

Testing entry quality checks...

Scripts

Scripts created to assist in maintaining quality compatibility ratings and game pages.

Testing

You can help complete the compatibility list by updating the ratings of the unrated titles. If necessary please revise title ratings based on testing.

The categories below are generated by testing templates providing age of testing details that could get some update.

Missing Template Cleanup

Missing Infobox Template

Missing Config Template

Missing Problems Template

Missing VersionCompatibility Template


Missing Testing Start Template


Missing Testing End Template


Missing VideoGallery Template

Lots of these...

We need to mass edit and add missing template:VideoGallery to the game pages that need it ASAP please, this list is getting nuisance for this to-do page. Lucario (talk) 01:54, 21 August 2017 (CEST)

Pending

Game Page Status Template

We should probably generate a template to track "completion" and frequency of different tasks for game pages, it could exist on each page's talk page and assist with maintenance. I'd like some help to scope such out here.

How are we supposed to do this exactly? I don't understand the mechanics of what you are trying to accomplish. What level of automation would be involved, and how much work does it take of an editor to fulfill everything? - MayImilae (talk) 00:26, 1 February 2013 (CET)
This has been started at Template:Page Status. It's nowhere near complete though, it just shows that it's possible. It's actually fairly easy to automate finding missing sections, though the regex can behave kind of weird (pulling in garbage sometimes, transclusion errors?). Since the actual output isn't required, just existence or nonexistence, it still works ok. When I made it I didn't realize that this was on Project:To Do, so I didn't see the following section of suggestions, or the previous DPLs that accomplish a lot of the same things. I still don't really understand how some of these are supposed to be handled. The infobox information has to be confirmed by hand, and Kolano and I were the only people who ever did it, so that seems pretty pointless for the template. There's other things where it's like, if someone's going to report about it, they could instead just fix it themselves rather quickly, like the title's description can easily be copy/pasted from GameFAQs by anyone. Anything else I thought was questionable or I would like expansion on, I marked with a (?) in the list below. - Xerxes (talk) 02:31, 21 August 2017 (CEST)

My intention was really for some sort of manual review to be established, beyond just establishing that a few fields were present. I'm not clear the current template accomplishes much that couldn't be handled via some additions to output similar categories in the infobox template (oe as already seen here). I'm guessing it's a heavier query, so perhaps it is better to restrict it to talk pages. Though I'd guess pre-generation/caching would mean there's little real difference. Kolano (talk) 05:11, 21 August 2017 (CEST)

Well, if this template is planned for mass addition when it's completed, all of the error handling and maintenance categories for the different templates could theoretically be moved to Page Status. The intention was mostly to show that that sort of thing would be possible, missing sections isn't really that useful of an application. User-input sections like "I fixed this on this date" would be trivial to add, just something like |infobox=timestamp, then have some check that infobox exists, and if it does output "This page's infobox was last checked on timestamp", if not "This page's infobox has not been checked". I don't know about date handling tools available in particular, but that seems like a common operation so I'd be surprised if they weren't included with MediaWiki. I know there's magic words related to it.
The one thing that's actually completely functional in the template is the unconfirmed ID reporting, so if the rest falls through, there's potential to just keep that as its own template for tracking IDs. I intentionally did that part first and fully fleshed it out because I wanted it the most, and it has immediate application without requiring mass editing. - Xerxes (talk) 06:34, 21 August 2017 (CEST)

Proposed "Game Page Status" Template Fields

  • Infobox contains accurate information regarding the game
  • Navigation template is in place if appropriate (default to NA)
  • Page includes a full set of sections
  • Title applied if page title post-fixed (i.e. GC/Wii indicators)(default to NA)
  • Forumlink is in place
  • Wikipedia link is functional/accurate: Date of last review
  • Date of last forum page review
  • Date of last issue tracker scan (unclear this shouldn't just be handled with more regular review of the issues list, see section below)
  • Display and track unconfirmed GameIDs
  • Linkages to patches, texture packs, etc are in place and still valid
The "Patches" section in Xenoblade Chronicles is something like this. We could adopt this as template (and then add this in Project:Wiki Conventions) mbc07 (talk)
  • (?)Description is: accurate, brief, provides info beyond what's found in the infobox (if you notice it's bad, just copy paste from gamefaqs? this seems really pointless compared to the others since 99% of pages don't have original descriptions)
Even if they are mostly scraped from other sources, I'd still prefer the descriptions to not read as "Title is a Genre game published on Date by Publisher". It frequently is the start of Wikipedia articles and only duplicates info already provided by the infobox, and thus is generally pointless. Kolano (talk) 06:44, 21 August 2017 (CEST)
  • (?)Time since last compatibility check (there is currently an implementation of this in the testing template, but it might be possible to move it here if preferred)
  • (?)Rating is accurate for revision XXX (how? just look for the words "playable"/"perfect"/"ingame" in test entries or something? what's the purpose of that?)

Issue Tracker Alignment

We need to scan through the Dolphin Issue Tracker and align articles here with issues. Oldest issue needing alignment: issue 267.

Config Template

  • Improve config documentation on Template page.
  • Update to generate additional error categories (non-on/off values, missing notes, etc.) Kolano 09:18, 3 July 2011 (CEST)

Infobox

  • Clean up publisher/release date info to indicate differing region releases more appropriately (see Fragile Dreams: Farewell Ruins of the Moon)
  • Consider purging emulation irrelevant details.
  • Consider cleaning up info for developers (such as FPS, Rel modules, DTK ADPCM, Size, FPS...) Provide feedback here
    • I think it would be good if such useless information is removed as it could differ from user to user. --Endres 17:12, 31 July 2011 (CEST)
      • These details should not change user to user. Perhaps you were confused by FPS. It's not the emulated FPS, but the games hard-coded internal FPS. These details are mainly of interest to developers, but may also let us more easily identify issues shared across multiple titles. I'm not clear if an exact "size" can be easily established though, as such may be somewhat dependent on the specific disc image tools used (i.e. slightly different headers, etc may slightly effect the size).Kolano 19:48, 31 July 2011 (CEST)
  • Add more infobox options for pages that don't fit the usual molds. For example, System Menu and Broadband Adapter do not need compatibility, so they use the platforms template. And that means loosing out on details they could have. MayImilae 02:53, 24 July 2012 (CEST)

Regarding documentation of game-specific .ini-files

This thing needs to be discussed, so as to see what resources might be available to us (e.g. documentation from the devs) and what, if anything, we can do about it. It is a rather large part of Dolphin, and one that, if properly documented, can be extremely convenient to end-users. A great example of this would be a game like Klonoa, which for all intents and purposes works excellently, but that needs the "EuRGB60 Mode (PAL60)" option switched off to do so, something which most games do not need. In this case, it'd be great to have that option switched on in the game .ini, so that a user wouldn't have to open up the options dialog every single time he or she wants to play that one specific game (compare and contrast with Metroid Prime (GC), that needs "EFB to RAM" to work properly, and which has that option switched on by default in the game .ini).

This has been started at GameINI_Settings/Sandbox. Kolano (talk) 23:10, 17 December 2015 (CET)

Went live out of the sandbox, it's now at GameINI. We may want to update template:Config somehow to inform user that they can update per game settings through INI? Lucario (talk) 02:02, 21 August 2017 (CEST)

Complete list of Dolphin hotkeys

There is apparently no comprehensive list anywhere of all the hotkeys that work in Dolphin. How do we take screenshots without going to the menu, for example? This wiki would be the perfect place for such a list. The only hotkey I know of is Alt-F5 to enable the Wii Remote. Flang 08:05, 23 July 2016 (CST)

In Dolphin, go to Options => Hotkey settings. Since most (if not all) of Dolphin Hotkeys can be user configured, I'm not sure if a list of hotkeys would work well... - mbc07 (talk) 18:51, 23 July 2016 (CEST)
Thank you for pointing me to the hotkeys menu in Dolphin. The way they are layed out in that menu is very confusing for new users like me - Apparently if a key is mapped like (!(LMENU | RMENU) & !(LSHIFT | RSHIFT) & !(LCONTROL | RCONTROL)) & `F1` - that means to press F1. I guess I still think it would be helpful to have a default list of hotkeys available on the wiki, but it's not a big deal. -Flang 08:53, 24 July 2016 (CST)