Template talk:Gameid

From RPCS3 Wiki

Including the pagename in forum thread link

I've encountered a problem with the way I was linking to the forum threads. Previously, I was including the game name in the link before the game ID using {{#regex:{{PAGENAME}}|/\s/|+}} to improve accuracy of the links (I took the game name straight from the page name). This worked for the most part until I hit games that have different names for different versions (for example: Ratchet & Clank: QForce and Atelier Shallie: Alchemists of the Dusk Sea). For lack of a better solution, I've simply removed the page name from the link which is fine for now. This reduces the accuracy of the links but I haven't seen it fail or link to a wrong thread yet.

But if that does occur, we'll have to consider renaming the threads to fix the issue. --MrHulaHoop (talk) 14:48, 11 February 2018 (UTC)

Using plainlinks and adding commas

With the way the template has been implemented now, there are no commas separating 2 GameIDs. The GameIDs are instead separated by the external link arrow. While this does get the job done, using commas between GameID would be aesthetically better. While implementing this was easy, I did hit a roadblock in cases where GameID was called consecutively. For example, {{gameid|id=BLES01225, BLUS30727|ird=Yes}}{{gameid|id=BCAS20185|ird=No}} would result in BLES01225(IRD), BLUS30727(IRD)BCAS20185. There wouldn't be a comma between BLUS30727 and BCAS20185. There's no way for the templates to identify what is coming before or after them in wikis so that isn't a possiblility. The solution would require user to manually enter the comma in such cases like {{gameid|id=BLES01225, BLUS30727|ird=Yes}}, {{gameid|id=BCAS20185|ird=No}}. While this seems fine, the more formatting we make the users do, the more things that can go wrong.

Also, I intend to add another parameter to allow users to add GameIDs that aren't present in the compatibility list. A wiki should list all possible GameIDs and currently we're unnecessarily restricted. Those IDs will be plaintext and will have to be separated by commas. So I think we will inevitably have to switch to commas and give the user the responsibility to add commas between consecutive GameID templates unless a better solution is found. --HerrHulaHoop (talk) 23:09, 1 October 2018 (UTC)

So, I've implemented the items mentioned above. Games are now separated by commas instead of the external link arrows. As mentioned above, when the template is used consectively, users will have to add a comma and space manually. But on the bright side, with these changes the oid parameter has been made to record game IDs that aren't present in the compatibility list. Let's see how it goes. --HerrHulaHoop (talk) 12:26, 2 October 2018 (UTC)