UWP, otherwise known as Universal Windows Platform, is big news for PC gamers. By bringing by the Xbox One and Windows 10 closer together, Microsoft has enabled for more Xbox exclusive to be brought to PC. However, the cost of that is using the Unified Windows Platform and casting away Win32. According to Microsoft’s latest statements, UWP may spell the end of unbridled modding for PC games.
As expected of a unified model for both Windows 10 and mobile devices, UWP is more restrictive than regular Win32 or .NET applications. When Microsoft first revealed their plans for games built on their new model, there was some concern about what that would mean for modding. While Microsoft has allayed some concerns, it looks like modding will have to go with a curated model, with approval from Microsoft needed.
“The mods where we’ll probably have some discussion, is… if I go in and change the executable in a way—if I actually go in and reorder the code or inject code paths the developer didn’t originally intend, [then] the problem is, [we] don’t know if that modification is to fix a broken game, or to add some kind of phishing tool to the game so that now it’s capturing my passwords as [your’re] typing them into Chrome…”
This sounds a lot like Steam Workshop where mods are somewhat curated and are limited in their functionality. This means while skins or character mods might be allowed, more hardcore ones like what Skyrim has seen might not be allowed. Simply put, modifying the executable and changing any code paths won’t be allowed. This severely curtails what mods can do. Honestly, Microsoft has two incompatible goals with a wall-gardened store in UWP and good old open Win32. If Microsoft wants to truly cater to PC gamers, it’s probably best to restrict UWP games to games that are Xbox exclusives and let the rest of us mod as usual.
I think there should be an “override” function to enable executable mods. Put it behind a serious warning screen, saying that you’ll lose out on protection from malware, and that it’s for advanced users only. Then rather than putting effort into patching holes enabling people to modify executables regardless, put effort into patching holes enabling them to be modified without the user going through that warning screen and approving it.