Okay, haha, I officually have NO idea what I did wrong, but now I can't even play MV anymore. When I try to run a game, I get a message saying that my node.js is too new, and it doesn't run.
This... isn't happening to anyone else, so clearly I did something real bad somehow. I've uninstalled and reinstalled the game on Steam, and it's still not working. Yeesh. I've got a long night ahead,looks like.
Ah, I had that problem, but dont worry, it's not hard to fix. (I struggled with this updating process for like 2 days lol, I became a master at it, and thus I wanted to share it and help fellow devs.)
Basically whats happening is, when you replace the files with the new ones, there are 2 things that are causing the problems with STEAM being unable to fix these.
1) The files names are the same, so the new ones, when mixed with the old ones, do not work correctly. So STEAM incorrectly thinks that some are them are ok when they are not. SO it doesnt replace files that appear to be ok (because of the names)
2) Though STEAM tries to make corrections, the one fatal flaw is, it doesnt delete things for you. So if you have a file that causes things to break, it will never delete things that arent suppose to be there. (I had mine broken for a little, but then realized I had extra files, I incorrectly assumed STEAM would fix this with a validation check, it doesn't!)
THANKFULLY! There is an easy fix.
Just go to the original folders......
I assume you are using PC and you just messed with the folders I told you about.
Simply delete everything out of the folders (nwjs-win, nwjs-win-test, nwjs-linux)
and after you delete all files, just tell STEAM to revalidate the files, this should replace the files with the correct files, since now they dont exist, it will force steam to replace them all with the correct files (this will also eliminate any files you incorrectly may have added.)
AND you should be all set..... to try again lol.
Just follow these steps again if it breaks lol. (Also, you can make backups if you like, but this fix is so easy its not really needed, but do what floats your boat)
/////////////////////////////
Ah also! You might want to do the NW.JS fix I mentioned at the bottom (known issues, its an easy fix, this could be causing the problem, just have to delete a couple files)
This may not relate to what you've mentioned, but
I was trying to use Visustella's impact and horror plugins, and it told me that I needed pixi to get it work, so I simply downloaded the latest version and installed it with plugin manager. That worked.
I'm at work so can't check my MZ now, but you mean a pixi is already included in MZ?
Absolutely it is. Its hiding out in the js->lib folder of your game.
Works lovely for me too, not that I've done any extensive testing with my project. I do have the issue someone said above though, here's the script I use for fullscreen;
Code:FSInitStart = SceneManager.initialize;
SceneManager.initialize = function(){
FSInitStart.call(this);
Graphics._requestFullScreen();
};
It doesn't work now, is there a quick fix? Thanks ^^
Ah I see there may be some issues with how people do certain things and thats to be expected.
I just use a yanfly script to change the dimensions of my game to 1280 x 720 and I didnt have any issues.
I use like........ 50+ scripts from 7+ different developers (35+ or so are Yanfly lol) with no issues (I am sooooo happy about that, I got lucky I guess).
I'm sure there are some work around to most of these issues.