Please note, that this version of the modified core is based on the original core v1.6.2. Make sure,
that your project uses this core version is working properly before replacing it with the modified
core, because this will cause an implicit upgrade/downgrade to the RPG Maker MV core v1.6.2.

1. Update NWJS Version of RPG Maker MV
   1.1. Download NWJS v0.94.0 from https://dl.nwjs.io/v0.94.0/
        Here are 4 versions available, depending on what you need. The RPG Maker MV is using NWJS in
        a 32bit version by default. That means that games (in test and in deployment) will run as a 
        32bit process. Also, the MV has two separate versions (on Windows) for testing (i.e., running
        the game from within the Maker) and deployment. The game will run as a 32bit process if the
        32bit NWJS version is used and as a 64bit process if the 64bit NWJS version is used. The 
        Maker itself will continue to run as a 32bit process in both cases. If you are not using 32bit
        libraries in your project for which no 64bit versions are available, you should use the 64bit
        NWJS version.
        The variants (for Windows) can be distinguished by their name as follows:
        64bit version with developer tools: nwjs-sdk-v0.94.0-win-x64.zip
        32bit version with developer tools: nwjs-sdk-v0.94.0-win-ia32.zip
        64bit version without developer tools: nwjs-v0.94.0-win-x64.zip
        32bit version without developer tools: nwjs-v0.94.0-win-ia32.zip
        The "SDK" in the name shows that this is the version with developer tools. This is the set of
        tools that can be opened using the F12 key. Because the Maker does have different versions for
        testing and deployment it is useful to have the "SDK" version for testing and the "NORMAL" 
        version for deployment. This would also mean that pressing F12 in a deployment version has no 
        effect. In any case should the 64bit version preferred to the 32bit version.
        Naming for Linux is similar. However, the Windows installation of the Maker has a folder for 
        the Linux deployment version only.
   1.2. Open the installation folder of the RPG Maker MZ
        (z.B.: C:\Program Files (x86)\Steam\steamapps\common\RPG Maker MV)
        In Steam: Right-click -> Properties -> Local Files -> Browse
   1.3. Steps for Windows:
        1.3.1. Changing the deployment version
               1.3.1.1. Rename the folder "nwjs-win-test" to "nwjs-win-test.bak" to have a backup available
                        if necessary
               1.3.1.2. Create a new folder named "nwjs-win-test"
               1.3.1.3. Extract the contents of the folder "nwjs-sdk-v0.94.0-win-x64" from the downloaded ZIP
                        file into the newly created folder "nwjs-win"
               1.3.1.4. Rename the file "nw.exe" to "game.exe"
        1.3.2. Changing the deployment version
               1.3.2.1. Rename the folder "nwjs-win" to "nwjs-win.bak" to have a backup available if necessary
               1.3.2.2. Create a new folder named "nwjs-win"
               1.3.2.3. Extract the contents of the folder "nwjs-v0.94.0-win-x64" from the downloaded ZIP 
                        file into the newly created folder "nwjs-win" (or the contents of the folder
                        "nwjs-sdk-v0.94.0-win-x64" from the corresponding ZIP file, if the "SDK" version is 
                        used for deployment).
               1.3.2.4. Copy the folder "www" from "nwjs-win.bak" to "nwjs-win"
               1.3.2.5. Copy the file "package.json" from "nwjs-win.bak" to "nwjs-win"
               1.3.2.6. Rename the file "nw.exe" to "Game.exe"
               The following steps 1.3.2.7 to 1.3.2.10 are only necessary if the "SDK" version is used here,
               because the "NORMAL" version does not contain these elements.
               1.3.2.7. Delete the folder "pnacl"
               1.3.2.8. Delete the file "chromedriver.exe"
               1.3.2.9. Delete the file "nacl_irt_x86_64.nexe"
               1.3.2.10. Delete the file "nwjc.exe"
   1.4. Steps for Linux:
        1.4.1. Changing the deployment version
               1.4.1.1. Rename the folder "nwjs-lnx" to "nwjs-lnx.bak" to have a backup available if necessary
               1.4.1.2. Create a new folder named "nwjs-lnx"
               1.4.1.3. Extract the contents of the folder "nwjs-v0.29.0-linux-x64" from the downloaded ZIP 
                        file into the newly created folder "nwjs-lnx". The *.tar.gz files for Linux can be
                        opened with any ZIP tool, like any other zip file.
               1.4.1.4. Copy the folder "icon" from "nwjs-lnx.bak" to "nwjs-lnx"
               1.4.1.5. Copy the file "Game.desktop" from "nwjs-lnx.bak" to "nwjs-lnx"
               1.4.1.6. Copy the file "package.json" from "nwjs-lnx.bak" to "nwjs-lnx"
               The following steps v1.4.1.7 to v1.4.1.14 are only necessary if the "SDK" version is used
               here, because the "NORMAL" version does not contain these elements.
               1.4.1.7. Delete the folder "pnacl"
               1.4.1.8. Delete the file "chromedriver"
               1.4.1.9. Delete the file "minidump_stackwalk"
               1.4.1.10. Delete the file "nacl_helper"
               1.4.1.11. Delete the file "nacl_helper_bootstrap"
               1.4.1.12. Delete the file "nacl_irt_x86_64.nexe"
               1.4.1.13. Delete the file "nwjc"
               1.4.1.14. Delete the file "payload"
   1.5. Steps for Mac
        In this case the contents of the ZIP file "nwjs-osx-unsigned.zip" would need to be changed, but the
        packaging of the NWJS version for MAC is a little unclear and I don't have a Mac for testing. It 
        should be similar to the previous steps.
   1.6. IMPORTANT: It is important (especially when using the "SDK" version), that in the "package.json" file
        the content of the "name" is not empty or the game wouldn't start properly.
        1.6.1. Open the file "package.json" from the project folder in a text editor and change this line:
                   "name": "",
               to 
                   "name": "rmmv-game",
The active NWJS version can be checked in the Console tab of the developer tools (to be opened with F12) by
entering the command "process.versions" (followed by Enter). This will show a list of all active versions.
The NWJS version can be found under "nw" or "node-webkit". To retrieve the version directly the command
"process.versions["nw"]" can also be used.

2. Update PIXI
   2.1. Download PIXI v4.8.9 (file "pixi.js" or "pixi.min.js") from:
        https://github.com/pixijs/pixijs/releases/tag/v4.8.9
        The file "pixi.min.js" has the same content as the "pixi.js" file but in a compacted form to save
        storage space. The is no functional difference between the two files. Functional as well as regarding
        performance, the difference is (if noticable at all) minimal.
   2.2. Open the folder "./js/libs/" in your project folder and backup the file "pixi.js" to be able to revert 
        back if necessary
   2.3. Replace the file "pixi.js" in the folder "./js/libs" in the project folder with either the downloaded
        file "pixi.js" or with the downloaded file "pixi.min.js" (renamed to "pixi.js").
The active version of PIXI will automatically be written to the console in the developer tools (to be opened
with F12). It can also be checked by opening the file "./js/libs/pixi.js" in the project folder. The PIXI 
version is written in the header comment of the file.

3. Update the RPG Maker MZ Core Files
   3.1. Open the subfolder "./js" in your project folder
   3.2. Create a backup of the "rpg_core.js" file, to be able to revert back if necessary
   3.3. Copy the file from the "Core" subfolder of this package in the "./js" folder in your project folder
        (replacing the existing one).


You can contact me via my website at https://radibor78lp.de which is in German but you can find a link to my Discord 
as well as links to donate some money via "Pay Me a Coffee" or "Paypal" in the menu on the left, if you want to support
my work.

Have a nice day!