- Aug 12, 2017
- 707
- 1,948
Hello,Hey pk2000,
Regarding the pixi.js stuff, I have four questions:
1) Your instructions in this thread's first post is to put the "pixi-patch.js" file in the "libs" folder.
Did you mean the "lib" (with no "s") folder? Because I cannot find any folder called "libs."
2) When you tell us to "replace the default pixi.js with the versions v4.5.6 or v4.8.9," are you saying that we should replace the "pixi-patch.js" file we placed in the "lib" folder with the version v4.5.6 or v4.8.9 "pixi.js" file?
3) It seems that there are newer versions of pixi.js as seen in thisYou must be registered to see the links. Should we use those versions instead of the ones you have provided?
4) Last but not least, the zip files you provided for version v4.5.6 or v4.8.9 each contain both a "pixi.js" and a "pixi.js.map" file when they are extracted. Should we copy both files ("pixi.js" and a "pixi.js.map") into the "lib" or "libs" folder?
Thanks for your help!
1) It wasn't a typo if a game has "lib", instead of "libs" it was moded by the developer... in that case place them in "lib" (unless you want to mod the index.html and point to the correct location of the files)
2) The pixi.patch is loaded automatically after pixi.js. For upgrading you need to replace the "pixi.js" file with the newer version.
3) Those are for pixi 5 (are compatible with MZ and not MV) ... but if you want to use them you should "upgrade" the engine to MV Game Engine 1.6.2.1
You must be registered to see the links
4) the map files are not needed (MV gives a loading error but you'll see that only on the debug console)