Aemony

I do not expect this to be implemented since the ”release history” parameter of the introduction template is intended for that purpose. Like, it wouldn’t just be about GOG as Steam, Microsoft Store, and even Epic sometimes sees similar re-releases. Right now there’s multiple ways of handling these re-releases: * Introduction template’s release history parameter, for straight re-releases on modern platforms. * Separate year-dated article for the re-release, for re-releases that also sees larger/more noteworthy changes.

I've dropped the "support" part of both Metal and Mantle (precursor to Vulkan). Note that the parameters remain unchanged so they'll still be called "metal support" and "mantle support". This hits the nail on the head -- all of the render APIs are handled the same right now: if you set an API to "false" or "unknown" it'll be hidden from the page to minimize the amount of unnecessary data that is shown for visitors. This is in contrast with many other templates, yes, but it is correct and works exactly as intended for the API template/table.

That already exists: https://www.pcgamingwiki.com/wiki/List_of_Windows_64-bit_games#Native_support_.2864-bit_only.29

I have left your posts alone, but hidden, over the last couple of months in an attempt to see if you were actually able to improve your attitude. So if you want someone to blame, blame me instead of people with no involvement into the matter. And that said, I do not approve of threats, either to myself or others, so I will be upgrading your wiki ban to an actual full ban, affecting your community privileges as well as your SSO account. You are not welcome here while having this kind of attitude so I recommend you forget about contributing to the PCGamingWiki project and finding another community project to engage with instead.

Chances are that if it's "DM-worthy", it's not actually relevant or something that the staff will consider. Examples that gets semi-frequently brought up and shut down are: Attempts to purchase the site. Attempts to "partner" and submit "guest posts" on the site. Advertisement partnerships (handled by GG Software/Nitro by Overwolf, so if it concerns that you can reach out to them at sales@ggsoftware.io). Other similar advertisement partnership by random third-party corporations. Third-party application developers wanting to partner with PCGW for similar purposes. Third-party mod/tool creators wanting to be granted some exclusive exception to the wiki policy. Users wanting to implement or promote a change that they suspect will be unfavorably received by other users or staff members. Then there's the common stuff that don't really need to be brought up through DMs: For problematic content on the Community site, use the Report function to call moderators' attention to it. For problematic content on wiki itself, see the code of conduct for details on how to report it. For feature suggestions and changes, either post about it publicly here or on the Discord server so the community can pitch in. For general assistance with articles and the like, the aforementioned Discord server is the most appropriate place for that to take place. So really the only stuff that is relevant for DMs is stuff like security vulnerabilities and the like that might be best kept secret, in which case you can DM me or one of the active staff members on the Discord server about it and one of us will carry it forward to the appropriate resources.

I have updated your wiki username. Sadly there is no automated or even user-exposed manual method of doing this. MediaWiki (the wiki system we use) does not really have user renames built into it so we have to rely on a third-party extension to do so, and as there is no built-in proper way of handling this there also hasn't been built any automated way that links up to the SSO account management page.

This is a community-driven project so there's no need for DMs in 99% of all situations that pertains to the site and project.

This have now been implemented, however affected pages will need a refresh or two before it starts appearing. There are currently no plans to do this since we don't do it for UE4 or UE5 either, with the sole exception being the HDR row which isn't applicable for UE3.

I’ve added support for it. How is usage of Rewired tested, by the way? Is it the presence of a specific DLL file or some other way?

Denuvo is intentionally opaque in its workings so if you're still experiencing the issue you're better off trying to reach out to their support through the support form.

I can’t tell if you *have* patches you want uploaded or if you *want* patches to download…? Anyway, there’s a FilePlanet archive.org mirror with a ton of content: https://archive.org/details/archiveteam-fileplanet

Follow the instructions and link here: https://www.pcgamingwiki.com/wiki/PCGamingWiki:Account#I_cannot_sign_in_on_the_wiki_due_to_an_invalid_username.3F.21

You are not signed in on that screenshot. Check your username — it may contain invalid characters (e.g. a mail address): https://www.pcgamingwiki.com/wiki/PCGamingWiki:Account#I_cannot_create_an_account_due_to_an_unexpected_error

Looking into it a bit more, Call of Duty: Ghosts, released in November 2013, might actually be the first mainstream 64-bit only game.

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.