User talk:Xerxes

Infobox Clean Up

The Commodore VC revision seems like a reasonable way to resolve the issue there. I had intended to try to revise the handling in the infobox code, but it's been a while now and I'm still unclear when I'd get around to it. Kolano (talk) 15:14, 6 January 2017 (CET)

XYZ Region GameIDs

Here's a DLP to pull the full set of currently registered XYZ region GameIDs...

RLTXUG, SAOXVZ, SVHX69, S3IYA4, S3IXA4, RPCX7J, SM8X52, SQVX69, R38X78, R38Y78, SPVYA4, SPVXA4, SFWX69, SFWY69, SFWZ69, RCDX52, RQBXUG, SI3X69, DTLX01, SNKX54, RO8X7D, RRXXUG, R2WXA4, SUXYA4, SUXXA4, RGWX41, RD2X41, R6NY41, RW9X78, G3DX6L, GEXX52, GEXY52, GHSY69, GHSX69, GQWX69, GL5X4F, G3YX52, G3YY52, GXOX69, GHNX71, RNSX69, RN3X78, GTLX52, SAVX5G, RM2X69, R6BX78, RUSX78, RUSY78, RNPY69, RNPX69, R5VX41, RF8X69, RF9Y69, RF9X69, R4RX69, R4RY69, R4RZ69, SELX69, SN4XGT, SEMX4Q, SEMY4Q, RQ6XKM, SHOXKR, SHOYKR, STSX4Q, STSY4Q, STSZ4Q, RPWX41, RPWZ41, STQX01, R6OX78, RUEX4Q, RUEY4Q, SU6XGT, R5IX4Q, RJAX52, RQJX7D, SD2Y41, RWUX52, RHGX6Z, RZHX5G, RWBXUG, RH4XUG, SVXY52, GJDX7D, GJDY7D, RU4X41, SREXNL, SRWXNL, SRTXNL, SRLXNL, RUHX52, RRMX69, R4LXUG, GX3X41, R8UXMR, SG2XUG, RJXXFR, RU5X4Q, RU5Y4Q, R3GXUG, ROXX7J, RSNX69, RUCXRT, RRLX78, RRLY78, RRLZ78, ST4XNX, GYAX78, R2AX7D, SZ2XGT, RNBX69, RXDY4Q, RXDX4Q, R5AX8P, R5OXUG, R8HX4Q, R8HY4Q, R8SX41, R94XMR, RB9X78, RB9Y78, RBEX52, RBRX5G, RBZXUG, RC2X78, RC2Y78, RC3X41, RC8X7D, RCEXUG, RCXX78, RDOX41, RDPX54, REQX54, REQY54, REWXMR, REWYMR, REYX4Q, RF8Y69, RFKX41, RFOX52, RH8X4F, RHQX4Q, RHQY4Q, RJSXUG, RKTXUG, RLUX4Q, RLUY4Q, RLWZ78, RMQXUG, RMRXNK, RMYXUG, RNMXUG, RNNX4Q, RNNY4Q, RNNZ4Q, ROFX5Z, ROYX41, RP9XRS, RRHXUJ, RRQX52, RRSX4Q, RS3X52, RSKX52, RTQXUG, RU7X5G, RUHZ52, RUIX4Q, RUQX78, RUXXUG, RVYX52, RVYY52, GDIX7D, GDIY7D, SKYX52, SKYY52, SKYZ52, GNOX78, RNVXUG, SCYX4Q, SCYZ4Q, GHLX69, GHLY69, GHLZ69, R5PX69, RTFX52, RTFY52, RRAXUG, SJDX41, SJDY41, SJDZ41, RX9X69, RX9Y69, RKPY52, RQ5X5G, R27X54, RHSX36, RHSY36, RB4X08, SU2X54, RMVX69, GGEX41, GGEY41, R6MXMR, RBNXG9, RWAY78, GINX69, G2CX52, GWYX41, GAVY78, GGVX78, GGZX52, GIQY78, GIQX78, GK5X78, GKSX52, GOSX41, GT7X41, GWLX6L, GWVX52, GXLX52, RLWY78, RLWX78, R4NX5G, S3FX69, RR2XUG, RVTXMR, SJFXGR, SLFXKM, R3HX6Z, R7MXFR, R8HZ4Q, RCAX78, RCAY78, RKPX52, RKSXUG, RMZXUG, ROFXUG, RRGX52, RWAX78, RWAZ78, RWWX78, RWZX5G, RXRXRS, RXUX41, RXVXWP, RYQX69, S2PXA4, S2PYA4, S3PX4Q, S6BX4Q, S6BY4Q, SC7Z52, SCYY4Q, SDUX41, SEMZ4Q, SEPZ41, SEPX41, SFXXKM, SG2YFS, SJRXA4, SJRYA4, SJRZA4, SK7XVZ, SKKXHY, SLAX78, SLAZ78, SMOX41, SMOY41, SNLX54, SQIY4Q, SSCXPM, SSPX52, SSPY52, STOX4Q, STRX4Q, STTXGR, SU9X4Q, RGWX01, RQPZ52, RJ9XML, GU3X78, GU4Y78, SPKXPV, R8XZ52, HCGX01, WMWXPV, R8OX54

Kolano (talk) 02:10, 30 November 2016 (CET)

There a way to list this alphabetically so I can keep track of my position easier? I can't do wiki magic lol..

I got it to order by last edit which works too. So nevermind on that one. - Xerxes (talk) 18:29, 30 November 2016 (CET)

There's more of these than I expected starting out and I keep finding more. The X is the most common, used to denote different language PAL releases, so noting those has become pretty mechanical. Sometimes it's used instead of P for the only EU release of a title which is nonsense. The Y/Z are much rarer and are always (? nope) used for even more PAL languages; the logic here seems to be avoiding having one giant menu of languages for a standardized European release. I even found a U in there for a retail Wii game, maybe to denote Australia since that game seems to break the mold of AUS release being the exact same disc as the Brit release. When I'm done looking at all of these and have a good deal of the infoboxes looked at, I'll look into other non-WiiWare U IDs. - Xerxes (talk) 08:47, 8 December 2016 (CET)

These have all been investigated as of right now. - Xerxes (talk) 10:08, 9 June 2017 (CEST)

U Region GameIDs

D4BU01, SESUWR, SS4UWR, D43U01, SIUUNG, SAFUHS, RWAU78, SS7URN, SBSURN, R6KU36, RM2U69, GAFU01, RPFU52, RSCU7D, GPAU01, G97U01, SS3UWR, STAU78, SU3UMR, D95U01, D93U01, D87U01, SS6UHS, WHPUGL

These have all been investigated as of right now. The only ones skipped were the demo discs as that's its own nightmare for another time. It turns out they WERE all Australian releases though, besides one. - Xerxes (talk) 13:20, 9 June 2017 (CEST)

V Region GameIDs

SSEVNG, RKPV52, RU5V4Q, SK8V52, SERV4Q

Publisher ID 28

ID 28 is the JP publisher ID used currently for all four Gamecube Kemco-published titles on the wiki: Egg Mania: Eggstreme Madness, Batman: Dark Tomorrow, Universal Studios Theme Parks Adventure, and Rogue Ops. Sometimes publishers just use different codes in Japan for some reason, and I can buy that, but these IDs are particularly mysterious to me because I can't confirm them, no GameTDB listing at all. They do exist though, they have JP covers and they have redump entries, but since redump uses the four character codes and not the six character I can't check the publisher ID. I trust the IDs that are here in any case because User:DanbSky's contributions from a quick survey are usually correct and sourced, and seem to come from his own collection, which would explain why they don't exist anywhere else (first time they've been documented). But it's probably worth mentioning that I have no way to check if they're correct or not short of tracking down the disc myself. - Xerxes (talk) 12:44, 16 December 2016 (CET)

GameID and GameTDB

Just a quick note regarding GameTDB and GameIDs. They actually provide a nice inventory file /w all their GameIDs in one spot at the top of [1]. It seems to be a bit easier to do searches in. It can also especially be helpful for identifying titles with multiple releases (i.e. different EU language sets), since they tend to be sequential in the listing. Kolano (talk) 18:36, 25 February 2017 (CET)

I didn't know about this, that's cool. I'm gunna have to think about how I'll fit this into my workflow. I think the main site and previous/next IDs feature is a bit more useful for this purpose because of the covers and release info, but ctrl-F on a .txt document is obviously way faster than searches through google's api. - Xerxes (talk) 23:04, 25 February 2017 (CET)

EA

SFWJ13, RZJJ13, R7XJ13, RSXJ13, RPXJ13, RM2J13, SNHJ13, RQGJ13, R4AJ13, RBKJ13, RF8J13, R4RJ13, GLOJ13, GSXJ13, GQWJ13, GXBJ13, GNDJ13, GKLJ13, GAZJ13, G3AJ13, GGIJ13, GUBJ13, G3VJ13, GONJ13, GEYJ13, GH4J13, GFIJ13, RT8J13, RNZJ13, R4CJ13, RHJJ13, RSHJ13, RF9J13, RX9J13, RNPJ13, RVSJ13, RP4J13, R9TJ13, RWOJ13, R7AJ13, RQOJ13, GFAJ13, RNSJ13, GHLJ13, GENJ13, GRZJ13, SEAJ13, GFSJ13, SNVJ13, RFQJ13, R5TJ13, GOWJ13, R5PJ13, G2NJ13, RSIJ13, R43J13, R5XJ13, WS5J13, WS2J13, WS4J13, WSIJ13, WBSJ13, GWXJ13, GXOJ13, GSWJ13, GSTJ13, GNSJ13, GHSJ13, WS3J13, WS6J13, G4PJ13, DSTJ13

GOWJ69, GAZJ69

^is this EA's fault or ours? I'm assuming the J69 are mistakes. - Xerxes (talk) 03:22, 4 June 2017 (CEST)

Mostly seems to be our fault, where it was presumed the JP publisher ID would match up with other regions. I cleaned up some of this, but there seem to be at least a few titles I'm having trouble confirming. A few title may actually use the "69" ID. For instance:

• NBA Street: http://www.gametdb.com/Wii/GNSJ69
• SSX Tricky: http://www.gametdb.com/Wii/GSTJ69
• Harry Potter and the Chamber of Secrets: http://www.gametdb.com/Wii/GHSJ69
• Need for Speed: Most Wanted: http://www.gametdb.com/Wii/GOWJ69 (we list GOWJ13 for this too, but I can't confirm it)
• SSX on Tour: http://www.gametdb.com/Wii/GXOJ69

I'm guessing these may be titles developed by EA studios outside of JP, but that's unclear. Kolano (talk) 20:15, 4 June 2017 (CEST)

The problem is that this is the exact kind of edge case where GameTDB tends to have mistakes, but there's also no other source to double check this against to confirm or deny that. I don't think we'll ever get a straight answer unless someone has the JP releases of these games, dumps them, then checks the ID and updates them here. The worst part is that they may actually be right and so nobody who has these dumped would have a reason to change the IDs, in which case we'd never know for sure. In terms of the wiki, I think it comes down to a decision whether or not to trust GameTDB or assume they're mistakes and make them consistent, but since GameTDB is the most reliable source there's not really much choice here. If you have a more creative solution, I'd be interested in hearing it, because I'm stumped.

Well, I came up with a creative idea. Doesn't Dolphin collect usage statistics now? And haven't those statistics included GameIDs since the start? Could that be used to see if some of these IDs exist or not, just by ctrl-F for these IDs? I mean if nobody's played it nobody's played it, but that's the best I got. - Xerxes (talk) 03:41, 5 June 2017 (CEST)

K, not sure on this.

Regarding the category, it may be helpful, but the capture of details, as here, should help avoid repeated researching which is probably preferable.

I'll also try to see if we can get access to the GameID inventory the dev's maintain from data scraped from Dolphin to see if we can confirm things that way (though there are many bad IDs in that list from custom generated ISOs we may need to be careful of). Kolano (talk) 22:57, 7 June 2017 (CEST)

Well of course there will be homebrew invalid IDs in there, I don't doubt that. I'm not suggesting to just mass add every ID from the usage statistics blindly. My master plan here is to use the power of statistics to confirm IDs. The thing is, because IDs are so different between games, if you know exactly what ID you're looking for, there shouldn't be any confusion. In the EA example above, I highly doubt there would be a homebrew title with the exact same GameID as an EA title, but with J69 suffix instead of a J13 suffix. That's the perfect situation where this would be useful. And of course, validity can be weighted by the amount of unique players who have played a certain ID. If there's only 1 record of it being played, maybe its a little tenuous whether it's legit or not, but if there's 10 or 20, then I think that stands on its own as confirmation.

Using this method for confirmation, since there's literally no other source to confirm Wii games with sketchy GameTDB entries and no cover scans, may actually be the only way to figure out whether these IDs are legitimate or not. This would make the talk page entries pointless since confirmation by hand has already been proven to be near impossible for these titles. I still advocate confirmation by hand when possible and I will continue to do so, as it sheds light on what IDs are possible or not, and I will still fill out the talk pages per your request, but maybe in the future instead of talk pages which historically haven't been particularly effective (nobody's fault), the category would be more practical. It would be one big list of raw IDs to confirm against the usage statistics data, making that process much smoother. What's the alternative? Just open every talk page until you find an Unconfirmed ID section, or use some function to search for that title on talk pages? I didn't even standardize that title until a few days ago, so even without the category I'd still have to go back and retitle all my talk page entries to automate this.

In any case the category actually has its own added benefits; it lets us use wiki tools like DPL to study IDs and their trends, while also being able to remove sketchy IDs from the results and be reasonably certain that the IDs looked at are legitimate. The problem here of course is this wouldn't be 100% useful unless every single confirmed ID had its own separate category of Confirmed IDs as well, but that would be a massive amount of work for little reward, whereas the Unconfirmed IDs category is much easier and, with enough data, functions effectively the same. - Xerxes (talk) 09:20, 8 June 2017 (CEST)

I don't think we'd want to have unconfirmed ID hanging around, so speedy deletion would be preferable, and it can always be recreated later if needs to. You can even open a discussion regarding the still unconfirmed ID in title's talk page if you'd like. The recently deleted ID will re-appear in list of missing ID so you can find out how popular is that "unconfirmed" ID. Again, speedy deletion is preferable because who knows if it's already ranked low (or won't appear) in the list of missing ID. Lucario (talk) 11:05, 11 June 2017 (CEST)

Oh, this functionality already exists? That's awesome. So if I understand this right, when there's a missing ID on the wiki, but it's in usage statistics, this page updates and adds the ID along with showing the all time playcount from the gathered data; or, if it wasn't played, it doesn't appear on the list. Is that right? My only fear with deleting unconfirmed IDs is actually one of degrees. For example, with Epic Mickey 2, the K region ID I'm almost certain exists because there's Korean covers, but I can't find a back scan to be 100% sure that's the right ID; however, the F region ID I'm pretty sure doesn't exist from the evidence I've found. If for example we were to delete both as unconfirmed, yes we can add the K region right back afterwards, but this would actually break the right click wiki functionality in Dolphin for the small subset of Korean Dolphin users. Maybe not a big deal for one game, but I've found a LOT of unsubstantiated IDs, and if we were to go through and start deleting them and seeing what happens I'm afraid of the end user impact of that. That's one reason I opted for a slower approach with a category. - Xerxes (talk) 11:50, 11 June 2017 (CEST)