Aemony

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.

Yes, see for example this game as an example: https://www.pcgamingwiki.com/wiki/Hotline_Miami_2:_Wrong_Number The list of DRM-free games on Steam have over 1500 other titles that can be used as examples of how this stuff can be covered: https://www.pcgamingwiki.com/wiki/List_of_DRM-free_games_on_Steam

So to summarize: Steam client == the digital distribution client used to download and install games. This client alone is not regarded as DRM from the perspective of PCGW nor have been since around 2017-2019. This corresponds to the Source column of PCGW's availability table. Steam DRM == the actual DRM component provided by Valve to game developers, and which are embedded as part of the game executable and applies various forms of piracy and tamper protection to the executable. This is tracked as "Steam" within the DRM column of PCGW's availability table. Steamworks API == the "Steam API" used by games to communicate/interface with the Steam client to unlock achievements and such. This is technically not DRM per se (it doesn't inherently have a dependency on the Steam client) but common misuse of it by game developers can result in it acting as DRM (not allowing the game to be launched without the Steam client running). This is tracked as "Steam" within the DRM column of PCGW's availability table when it acts as such despite using a steam_appid.txt file to provide it with the App ID of the game. DRM-free == A Steam game is DRM-free if it fulfills both of these requirements: the game does not have the Steam DRM wrapper embedded in the game executable and the game does not have the Steamworks API act in a DRM-like capability when provided with an appropriate steam_appid.txt file. If a Steam game fulfills both of these requirements, meaning they can properly be launched separately without the Steam client installed or running on the system, it's marked as DRM-free within the DRM column of the availability table Our main issue isn't with the way the templates are treating this -- it's with people filling out the fields without improper testing (which only education and training can resolve) and legacy data provided and inserted from PCGW's younger years before we separated the client/launcher from the DRM tracking (which can only be resolved by someone going back and retesting all of the games).

There is no need to split anything as the way it’s being tracked is already fine enough. The issue isn’t with how PCGW handles it — it’s with how users, and typically in the past, filled out the information and that issue would remain regardless of what change was implemented. Steam DRM refers to the DRM component of the game. It doesn’t refer to the Steam client (the launcher) at all. And regardless of its efficiency, it’s still DRM and treated as such by PCGW. As I mentioned, we don’t care about the efficiency of a DRM solution. If it’s DRM it’s DRM, regardless of how reverse engineered and easy to remove it eventually becomes. And to clarify PCGW does not consider the Steam client as DRM, nor have we done that since around 2017-2019.

The Steam DRM wrapper is DRM -- there's no question about that. It's however not a proper full-blown anti-piracy solution because of the basic and standardized protection measures it employs. As Valve themselves says, it protects against extremely casual piracy (and tampering) and wouldn't prevent a motivated actor. But that's all besides the point for PCGW -- the site doesn't make a distinction between a "successful" DRM and a "so well documented and reverse engineered it's functionally useless" DRM. They're both equally treated as DRM on PCGW. That thread is insanely out of date and harkens back to the very early design and guidelines the site had over a decade ago. The modern approach and coverage of DRMs and stores (where Steam/Epic/etc games can be flagged as DRM-free) were introduced later sometimes around 2017-2019 or so. As I said in an earlier post, there's not a lot PCGW can do about this to improve it further as we've already built and implemented everything that's required to flag DRM-free titles on Steam/Epic/etc as such since years ago. Your issue, at its core, is with older unmaintained game pages and potentially incorrect DRM tracking within them and there's nothing the PCGW staff can really do about. Those pages and DRM claims needs to be gone through by an owner of said games, and then verified and updated/corrected where possible. And it is pretty much all of the game pages that would need to be gone through as most of them almost certainly lack an actual reliable reference to the DRM claim being made. And when it comes to that kind of job, PCGW is a community project where literally anyone can edit the game pages so anyone would be able to take on that kind of project upon themselves and go through and do it. The staff itself, however, will pretty much never have the time to do anything like that since their focus is on other areas.

Hi, PCGW already makes that distinction where possible, however the incorrect DRM tracking stems from editors assuming that a specific store-provided DRM option is used for a game at the time the article was created, which is often months or years before the release of the game. The intention is for editors to always follow up and validate the claim upon release, if possible. The ”store DRMs” that we supports refers to those store-provided DRM options, e.g. Steam DRM for Steam, EOS/EGS based DRM for Epic Games Store, EA’s DRM for EA App, etc. So they do not technically refer to the storefronts themselves, but the clients/underlying platform used to enforce said DRM. This is also why PCGW support flagging a DRM such as ”DRM-free*” (with a star/wildcard), in scenario where digital distribution releases (e.g. Steam games) requires a few manual steps to ”access” its actual DRM-free nature (e.g. steam_appid.txt for some Steam games). PCGW also note the ”default store DRM” assumption discrepancy over on the DRM-free lists: https://www.pcgamingwiki.com/wiki/List_of_DRM-free_games Basically, there’s not a lot PCGW can do in this regard than what we already do. P.S.: That Reddit thread is inaccurate and only concerns games that uses the Steamworks API but does not use Steam DRM to protect the game. Such games don’t have a dependency on the Steamworks API client — they only have a dependency on knowing the Steam App ID which the embedded Steamworks API should engage in. These are supported and tracked on PCGW as ”DRM-free*” (star/wildcard) due to the manual methods involved. For games actually protected by Steam DRM, the method will have no effect at all.

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.

Ultimately how people use it is up to them, but as Sarge touched upon ”minor” edits are typically edits that their author do not think need additional inspection. I think Wikipedia makes the distinction between a ”major” and a ”minor” edit by whether the meaning/gist of a paragraph changes overtly. If it doesn’t change in a meaningful way, marking an edit as “minor” allows other editors to filter out them when going through the recent changes on the site. I believe all edits for all new users default to being “major” as such, due to ensuring existing editors do not overlook them. However within the user’s preferences there should be an option that controls whether to mark the edits as minor or major by default.

It was just TryMedia's digital distribution DRM. TryMedia would also be managing SafeDisc in its final years, so it can be described as sort of SafeDisc's digital brother. Anyway, those types of "unusual" DRMs that provided alternate monetization methods, such as a trial mode and the like, was common in the early ages of digital distribution when publishers and developers tested the waters of what worked and what didn't. Even StarForce had their own variant of the trial DRM protected title, through their StarForce FrontLine ProActive solution.

Archive.org has it archived through two different sources (I've verified the two files are identical): https://archive.org/download/ftpwizworks_250620/ftp.wizworks.com.zip/ftp.wizworks.com%2Fpatches%2Fjnicklaus5%2Fjack51up.exe https://archive.org/download/LEVEL0298R/LEVEL0298R.iso/Updates%2FJack Nicklaus 5%2FJACK51UP.EXE One of them also carries an update for the fourth game: https://archive.org/download/ftpwizworks_250620/ftp.wizworks.com.zip/ftp.wizworks.com%2Fpatches%2Fjnickluas4%2Fjack41up.exe That source can be browsed here: https://ia803200.us.archive.org/view_archive.php?archive=/0/items/ftpwizworks_250620/ftp.wizworks.com.zip JACK51UP.EXE

Hi, I snuck in and added support for the oculus/meta keywords to that template, so they should now work 🙂