- Feb 26, 2014
- Reaction score
- First Language
- Primarily Uses
That has an almost guaranteed chance of bricking my game as the nw.js version is tied to the current version of MV you are using. It even says in the OP of the thread, version 1.6 or greater.oh, it wasn't that deployed it worked, but instead when I used the browser to test it worked. Even if you use 1.5.2 and update the nw.js version of your game, https://forums.rpgmakerweb.com/inde...upgrade-nwjs-and-chromium-67-68-64bits.96908/
It should work, also after you deploy it.
But you are not wrong, the best was if I made it also work for 1.5.2 and under, but since when I worked on it, I was using ES6 terms, it got that issue of only working for 1.6 and up. I will try to get some time to still work on this, I was doing it, but it was taking way too much time for me to fix it, do you mind trying the suggestion above maybe?
Your plugin may work fine by doing this but the rest of my plugins will break and cause crashing with one random error after another with no solution in sight.