Messed up and confused plugin error.

● ARCHIVED · READ-ONLY
Started by Skurge 20 posts View original ↗
  1. Skurge
    #1 Source
    Hello, I've been trying to fix my project yet again- having to attempt to get it working through an updated version I have a strange error that interrupts the testplay when I boot it up.

    wtf.png

    The problem is, no matter what circumstances I work with- this error shows up no matter what I do.
    Each of these steps I have taken have failed and still bring up the message.

    • Checked plugin list (Not present in plugin tab)
    • Checked js/plugins folder (No such plugin inside folder)
    • Reinstalled the plugin
    • Re downloaded and reinstalled the plugin
    No matter what the case is, even with all plugins turned off- the program still insists there is an issue with or without it being installed.
  2. Aloe Guvner
    #2 Source
    1. When the error comes up, can you press F8 to open the Developer Console and post a screenshot of that error?
    2. Can you post a screenshot of your Plugin Manager list?
    3. Can you go to your project folder, into the /js subfolder, and open the 'plugins.js' file in a text editor? Don't edit it! Just look to see if there is a line with "name":"SRD_FullscreenToggleOption","status":true
  3. Skurge
    #3 Source
    I am unable to bring up the console via F8, the playtest error seems to prevent it from opening.

    This is the list of plugins, ones that are set turned off are ones that have not yet been implemented for use in the project and some are not fully developed.
    wtf.png

    I cannot find the line in my plugins file, that may be the cause of the problem, how it happened I do not know.
    I'm expecting more errors to show after this one is sorted but I cannot until this is out of the way.
  4. Jonforum
    #4 Source
    inject this
    PHP:
    const debugWin = require('nw.gui').Window.get();
debugWin.showDevTools();
  5. Andar
    #5 Source
    Some of your yanfly plugins are in the wrong order, you'll need to correct that as well.
  6. Aloe Guvner
    #6 Source
    @Jonforum do you know the code for that for ES5 / old version of nw.js?
    OP is likely using MV v1.5.2
  7. Jonforum
    #7 Source
    require('nw.gui').Window.get().showDevTools();
    just don't declare in a variable
    Place this code in your first plugin or a new one.
  8. Skurge
    #8 Source
    Current version is 1.6.0

    I wouldn't know where to put that line of code specifically in the file and I do not know what the correct order would be for the yanfly plugins.
  9. Andar
    #9 Source
    Go to yanfly's Website - the order in which the plugins are posted there is the required order for them.
  10. Skurge
    #10 Source
    I can't find a list of the plugins that need to be in order on the web page
  11. Andar
    #11 Source
    The list where he lists every one of his Plugins? Where he said at top that this is the recommended order (although that is old, by now it is required).

    You can't miss that list because you need it to get to his plugin pages...
  12. Skurge
    #12 Source
    OK, I think I got the list in the correct order in the projects current state, all there is now needed to do is to correct the plugin problem with the SRD screen toggle issue.

    I'm not certain where to place this line of code provided or if it will be sufficient to fix the error.
  13. Aloe Guvner
    #13 Source
    Skurge said:
    I'm not certain where to place this line of code provided or if it will be sufficient to fix the error.
    Jonforum said:
    Place this code in your first plugin or a new one.

    This code isn't intended to fix the error, it is intended to learn more about your problem. You said you were unable to open the console by pressing F8, so this code will do that for you.

    Please follow these steps carefully:
    1). Open a text editor (like Notepad, etc.) and paste in the following code.
    Code:
    console.log(Utils.RPGMAKER_VERSION);
console.log($plugins.find(function(a){return a.name === "SRD_FullScreenToggleOption";}));
require('nw.gui').Window.get().showDevTools();
    2.) Save this file as Troubleshooting.js , and add it to your project's /js/plugins folder.
    3.) Using the Plugin Manager, install this at the top of the list. Save the project.
    4.) Playtest the game.
    5.) Take a screenshot of the developer console and post it here.
  14. Skurge
    #14 Source
    The same error occurs and it won't bring up the console :/
    Troubleshooting.js
  15. Skurge
    #15 Source
    I don't know where to go from here, unable to bring up the console but this program insists it cannot find the plugin installed or not.
  16. Jonforum
    #16 Source
    you console plugin(Troubleshooting.js) need to be first in the list of plugin manage, or you can inject code directly inside the rpg_core.js
  17. Aloe Guvner
    #17 Source
    @Skurge If you want, you can PM me your project and I'll debug it. You can remove all assets besides the title screen.
  18. _Shadow_
    #18 Source
    Aloe Guvner said:
    @Skurge If you want, you can PM me your project and I'll debug it. You can remove all assets besides the title screen.
    Yeah, just make sure the solution will be posted here so others will benefit from it in the future. That's the whole point of the forum.
  19. Aloe Guvner
    #19 Source
    After analysis, the cause of this error was identified and corrected (the test play is still crashing but it is a different issue)

    General Cause:
    An old version of the project was deployed into its own folder.
    This caused the deployment files (such as the 'www' and 'locales' folders) to be mixed with the project files.

    Specific Cause:
    The package.json file was overwritten by the deployment and pointed to the wrong files to execute in a test play.
    package.json
    package.json can be thought of as a configuration file for the Node.js ecosystem. RPG Maker MV uses the NW.js framework which combines Node.js and the Chromium engine to deploy the game.
    The package.json in the project folder identifies the file to execute for test play (normally it is 'index.html'). But, when a game is deployed, it points to a slightly different location ('www/index.html'). This caused the wrong html file to be executed in the test play, and this is a chain-reaction
    [wrong html file is executed --> wrong plugins.js file is read --> it tries to load plugins that don't exist]

    Fix:
    The project is still a work in progress, so the deployment shouldn't have happened. The fix was to remove the files created by the deployment and correct the package.json file.
  20. Alisu
    #20 Source
    Have you tried rolling back the version. I hear 1.6 is sort of broken at the moment.