Leaderboard

Crysis 3 is a 32-bit game. I'm not sure which game would be the very first 64-bit only game and it depends a lot of where you draw the line. The first Titanfall, released in March 2014, only came with a 64-bit executable, and might very well be the first mainstream game to be 64-bit only (Call of Duty: Ghosts from November, 2013 predates it). Before 2014, there were a few odd ducklings that were 64-bit only but they were typically insignificant indie games or student projects, such as e.g. Igneous from 2009, and 8-Bit Commando from 2011 which both seem to have been 64-bit only. But 2014 was when the ball started rolling, and 64-bit only games started being released on a massive scale, for one very simple reason: Windows XP went end-of-life in April 8, 2014. You then had Wolfenstein: The New Order and Watch Dogs released in late May, both 64-bit only games, and that trend just continued throughout the year. PCGW's backend data supports this as well, with a lot of pre-2014 multiplayer/live service games being listed as "64-bit only" nowadays as a result of receiving continuous updates throughout the years which eventually saw them dropping 32-bit support entirely. Note that some of PCGW's data for random indie titles is most likely wrong, or have been affected by a later re-release on Steam. We list Cogs and Romopolis, both originally released in 2009, as being 64-bit only for example, but Cogs saw a 2025 re-release that dropped 32-bit support, while Romopolis was actually released on Steam in 2016 and so our data probably doesn't reflect the original 2009 release.

This is an amazing initiative—huge thanks to Doblando en España for bringing full Spanish voiceovers to such a classic game! It’s great to see these gems made more accessible and immersive for Spanish-speaking players.

Today more than ever, (fast) storage space is expensive. One thing that always makes me mad is the insane amount of unused Localizations, game modes (often dead/closed multiplayer modes) that are installed by default - this is literally dead content. Wasted storage. Wasted money. Now back in ye old days, it used to be a gigabyte at best. Not the end of the world, and not exactly worth the time investment. But old habits die hard, and I'm still doing it today. With games becoming larger and larger, storage has become an issue that can thankfully be alleviated. I'm going to list a few interesting examples, then propose a solution and finally suggest a way to integrate it to PCGW's structure. I'll also list a couple of issues with my proposal, potential flaws and uses cases etc. If you have a better idea or any suggestion to make this a thing, you're more than welcome. Please note that all the numbers given are taken from Steam, but GoG, Uplay, EGS & Origin are guilty of the very same thing. Uplay's even worse, as always. Any constructive feedback would be much appreciated - I never suggested a feature before, but this one has been on the back of my mind for at least a year. I feel like it could be very useful to many folks out there. So, let's get to it. Those are easy ones to "clean-up" (more on that later): Batman Arkham Origins. Had a multiplayer mode, servers are down. Delete one folder and the install size goes from 27.06Gb to 18.1Gb. 9Gb (33%) saved Final Fantasy XIII. Well documented, check the PCGW entry for it, you can remove ~20Gb if you don't want the Japanese audio. 57.6Gb to 37.7Gb. 19.9Gb (52%) saved (!!!) Doom 2016. Do you really play the MP or Snapmap modes? That's ~15Gb (11Gb if you only delete the MP) saved. From 69.68Gb to 54.68Gb. 15Gb (21.5%) saved Here's the problem. I can manually delete all localizations, "deluxe edition content", Readme/Support and redists safely from most MT_Framework, UE3 and Ubi games just fine because they use the same naming conventions. All I have to do is search in the root folder for any file with the _ita. suffix for instance and delete it - but that's because I know what I'm doing and I'm willing to take the time to locate and delete those files. Listing that would massively bloat any page of course, and not many users would do it anyways. The best way I can think of to implement a reliable and simple method to delete files that we're absolutely sure are safe to delete goes something like this: Add a "debloatable" boolean to the Other Information infobox, If True, how much can be shaved-off at best. Users like myself could build a database of games we know we can "shave" (much like SK/ReShade compat, with a dedicated page) The end user would download a batch file, hosted here and verified by members based on a template which would include one option for each localization, and a "clean-up" option (remove Readme, Deluxe content, redists if safe) So for instance, I can flag all the localization for Resident Evil 6 and write them down in the dedicated page. I don't have any experience making modular batch files like that however, so someone else would have to make a template. I can then edit that batch to point it to all the files we want to delete. The end user launches the batch file, delete all locales but the one he's/she's using and boom. That's money saved right there. I know there are programs that are much better than Win Explorer's Search feature - if we can feed such a program with a config file it should do the trick too. We'd still need to build a database though. I do realize that I make it sound much easier than it may be, or that it may sound overkill if we're talking about a Gb at best. But for extreme cases like Doom 2016, Far Cry 3/4, FF XIII, the Arkham series, The Evil Within - huge games basically, it would be very helpful and hey, I'm already doing it anyways so might as well share it. There's also games like Battlefront 2 (2005) where you can cut the install size in half. It's about 5Gb (vanilla) if memory serves, about 2-3Gb when cleaned. With that said, if anything I hope that this thread at least brings more attention to this issue. Last but not least, to everyone: Happy holidays! I hope you're all doing well, and ready for more PCGW grunt work for this year to come. "Keep on keeping on".

Dear PCGamingWiki Team, I hope this message finds you well. I am writing to express my concerns regarding the current state of the mod section on PCGamingWiki pages. While I appreciate the effort to provide a comprehensive resource for PC gamers, I believe that the mod section, as it stands, is messy and convoluted. The primary issue is that this section has become a repository for personal preference mods rather than actual game fixes. This not only dilutes the purpose of the wiki but also makes it challenging for users to find essential fixes and improvements. The inclusion of numerous personal mods has led to bloated wiki pages, making navigation and information retrieval cumbersome. In my opinion, the creation of this section was a mistake. It detracts from the core mission of PCGamingWiki, which is to provide clear and concise information on game fixes and improvements. I suggest a reevaluation of the mod section’s purpose and a possible restructuring to ensure that it aligns more closely with the wiki’s primary goals. I look forward to any changes that can enhance the user experience on PCGamingWiki.

Are there good examples?