(I've originally posted this on the RPG Maker Web Forums in 16th of September 2016)
Project Centennial (Desktop App Converter) is a Windows Bridge. This is a tool to bring Win32 and .NET apps to the Universal Windows Platform (and to the Windows Store if you want to).
Why would I want to bring my RPG Maker project to UWP with this?
Right now, you would need it to bring your project to the Windows Store (more on that later), but you can utilize APIs that are available to UWP (Live Tiles for example). As they continue to develop it, more UWP features will be available to Win32/.NET programs as well as porting more types of software(such as VB6).
How it works?
It works like this:
- Using a PowerShell script, you take the gameâ€™s installer and install it on an isolated environment.
- After being transferred, it will execute the installation, along with tracking the files placed by the installer.
- After installation, the file will take the tracked files and build the AppX file.
What do I need to use it?
- Windows 10 Pro or Enterprise with the Anniversary Update (Build 14393 and higher)
- 64-bit Processor with support of Second Level Address Translation (SLAT) (You may see it as Intel VT-x or AMD-V on your computerâ€™s BIOS or UEFI).
- Windows SDK for Windows 10 Anniversary Update
- Make sure that saves and settings are store away from the gameâ€™s folder. The game will be stored on a hidden file on the Program Files and writing on that folder will fail.
- If you are storing info on the Registry, do not use HKEY_LOCAL_MACHINE! Quoting the document:
â€œAny attempt by your app to create an HKLM key, or to open one for modification, will result in an access-denied failure. Remember that your app has its own private virtualized view of the registry, so the notion of a user- and machine-wide registry hive (which is what HKLM is) does not apply. You will need to find another way of achieving what you were using HKLM for, like writing to HKEY_CURRENT_USER (HKCU) instead.â€ See the document on the link (at the end of the post) for more information.
- Users only need Windows 10 (any edition, 32 or 64bit PC) with the Anniversary Update installed to install and run Project Centennial apps.
Iâ€™d like to note that this may not be accurate.
- RPG Maker MV: It should work, as long as all rpgsave files are saved away from the gameâ€™s folder (if possible). I recommend you instead convert the game to UWP app with Visual Studio or Intel XDK, since you can access UWP APIs from the get go.
- RGSS based engines (VXAce, VX, XP): Same thing with saves and settings saved with MV. Most of the Ruby/RGSS scripts should work, no modifications necessary.
- RPG Maker 200x: Unless you can get the engine save away from its folder, it will not work well. The game will still work, but you can't save at all.
Q: I use scripts that use DLLs written in C++. Will these also work?
A: If it is compiled with Visual Studio, check which version was compiled. Not all versions work with it (due to static and dynamic linking support). See the linked document for more info.
Q: What about .NET programs?
A: If your game ships with a .NET program, check the document linked, to make sure it will work.
Q: Script X crashes my game when trying to read a specific file. What to do?
A: I donâ€™t know why exactly, but the script may be trying to read file in a way that is not permitted on files stored there (such as in V.M. of .D.T.â€™s Version/Build Number script, where it tries to binary read a file). If possible, either re-tool the reading code or remove it. Some experimentation is needed.
Q: Do I need to build an MSI file for the installer?
A: No. You can use installers that build an exe installer (You can use MSI installers too). Just make sure that it has a silent installation command line argument (/S for example).
Q: Can I publish the game to the Windows Store after conversion.
A: Yes, but not now. The policies of the Store havenâ€™t been updated yet (although they have launched a sign up page for Windows Developers).