RPG Maker MV Cook Tool

● ARCHIVED · READ-ONLY
Started by AceOfAces 92 posts Page 5 of 5 View original ↗
  1. ShadowDragon said:
    to bad that win7 cannot use the update version as I stick for 7 for a while :), but if there is an updated that fixed
    the removed button, would that one still work on win7? or also not?

    otherwise I stick with the version I have that seems to work.
    Technically, you can. By compiling the source code with .NET 6, you can have a working version of the update. You simply need to change this line in the csproj file for RMMVCookTool.GUI:
    Code:
    <!--Change it to net6.0-windows-->
    <TargetFramework>net7.0-windows10.0.18362.0</TargetFramework>

    And this line in Directory.Build.props file (in the root of the source code folder):
    Code:
    <!--Change it to net6.0-->
    <TargetFramework>net7.0</TargetFramework>

    Then run this on the command line:

    Code:
    dotnet publish "<path to the csproj file>" -c Release -a x64 (or x86, if you are on 32-bit Windows).

    Link to the source code:
    GitHub - FirehawkV21/RMMVCookTool: Compiles an RPG Maker MV's Javascript files to binary.
  2. I see to many files and folders, which I assume only need the folder?
    but than again, I never used the command line or how to set that up.

    so I have no clue what exactly to change as I like the ready to use
    software.

    but I will check later once I get back to see if I can get it to work, as I dont
    have VS-2022 or know how to compile stuff.

    otherwise, I hope you can make this version as final for w7 people? :)
  3. Not a week after the release of R4 Update 2, R4.00 Update 3 was released. This update re-works the compiler job so it can detect compiler errors and stop the job. This update was back-ported to .NET 6 for anyone that can't move over to newer versions of Windows. The legacy release will only be available on Github (LegacyWindows).
  4. Used the current version of MV Cook Tool and ran into this error along with just a black screen:

    Error.png

    Any help would be greatly appreciated!

    Also, I was able to isolate the error by removing all the plugins and putting them back in one at a time. Apparently, the error occurs the moment "Eli Book" is added.

    I will say that deploying a blank project and using your Cook Tool does work without any issues. I believe this is only with Eli Book at the moment. It won't let me go on until this is fixed. The project itself has no issues when deployed and played by itself - just when the Cook Tool is used.

    Thank you for an awesome product!
  5. bass2yang said:
    Used the current version of MV Cook Tool and ran into this error along with just a black screen:

    View attachment 274603

    Any help would be greatly appreciated!

    Also, I was able to isolate the error by removing all the plugins and putting them back in one at a time. Apparently, the error occurs the moment "Eli Book" is added.

    I will say that deploying a blank project and using your Cook Tool does work without any issues. I believe this is only with Eli Book at the moment. It won't let me go on until this is fixed. The project itself has no issues when deployed and played by itself - just when the Cook Tool is used.

    Thank you for an awesome product!
    Hello!
    At the moment, this is an issue where the JSON embedded on the plugin gets malformed. I have reported this bug to the dev, but I haven't heard back from him yet. I am looking into a better fix, but a possible workaround is to find JSON.parse in it and comment it out. This may introduce some odd issues.
  6. AceOfAces_Mod said:
    Hello!
    At the moment, this is an issue where the JSON embedded on the plugin gets malformed. I have reported this bug to the dev, but I haven't heard back from him yet. I am looking into a better fix, but a possible workaround is to find JSON.parse in it and comment it out. This may introduce some odd issues.

    Thank you for your quick response.

    The lines in question are Eli_Book.js line 909 and line 914:

    904 this.parameters.engine = JSON.parse(parameters.engine) 912 this.parameters.playtest = JSON.parse(parameters.playtest)

    I also tested the project without using the Cook Tool (with those lines commented out as suggested) and it seems to be working fine at the moment in a regular, deployed project.

    I deployed it again with the Cook Tool and ran into different issues. I was able to get to the Start screen but lost the Exit menu command from CT_Bolt's Exit Command (CTB_ExitCommand.js), and all walking/stepping animations are not working. Other animations seem to be fine (Chests, fades, transitions, attack/item animations from the database). I'll keep digging around - I will also try to revert back to a lower version of NWJS to see if that does anything and report back.

    EDIT:
    So I reverted NWJS to 49.2 and it still had the same issues (no exit command, no stepping/walking animations, still need to comment out the JSON.parse statements).

    I understand this is an NWJS/NWJC issue converting from .js to .bin and not your Cook Tool. I do appreciate your help on this matter. Unfortunately, it's taking way too long to try to find out which plugin is the issue because currently I have to deploy the game, convert the .js files, edit index.html and rpg_managers, and then run the test; there isn't a good way for me to just remove the .bin file one by one.
    I had considered going into the plugins.js file and editing each plugin as "false" to turn it off after deployment, but since it is already compiled by that time, I can't do much with that, either.

    Maybe I can isolate groups of plugins at a time and slowly pinpoint it. It won't take as long but will still require some time.

    Again, a blank project has no issues which leads me to believe that this is definitely a compiled plugin issue. NWJS 72, 63.1, and 49.2 all worked fine during my tests.

    Thanks!

    EDIT 2:
    I was able to improve my workflow just now by selectively finding plugins that deal with animation in general and I was able to isolate VE_CharacterFrames.js as the issue for halting all stepping/walking animations. Removed it and it walking/stepping animation works now.

    Summary of Issues for .js files being compiled to .bin:
    Eli_Book.js lines 904 and 912 that uses JSON.parse()
    CTB_ExitCommand.js not showing up in menu
    VE_CharacterFrames.js affecting all stepping/walking animations

    Thanks!
  7. Some updates regarding the tool:

    1. As of September 12th, the tool has been superseded by it's successor, RPG maker Cook Tool Deluxe. The new tool is an expanded and enhanced version of this tool, coming in with new utilities as well. You can take a look here.
    2. From this point forward, this tool will receive compatibility and bug fixes.
    I'll continue to provide support for cases like JS plugins not working, but most of the work will go towards the new version. I am planning a few updates for the original, tho.
  8. Hello @AceOfAces_Mod i've got some self made errors (i solved them because i never read the instructions apparently) but this error pops up after trying to execute the cooked game.

    1696644305996.png
    This translates to
    Error loading extension
    Could not load background script "".js

    Am i missing something?
  9. Erif said:
    Hello @AceOfAces_Mod i've got some self made errors (i solved them because i never read the instructions apparently) but this error pops up after trying to execute the cooked game.

    View attachment 279328
    This translates to
    Error loading extension
    Could not load background script "".js

    Am i missing something?
    Hello!

    It appears that it's an unintentional bug in Cook Tool Deluxe's Metadata Editor (kind of). Since Deluxe has a few new entries on it, nwjs requires these (specifically, entries for background and main script) to be filled. These shouldn't be required for the game to work. I'm pushing out a hotfix for this.
  10. alright, here's hoping it works!
  11. @Erif I pushed out the hotfix for the tool. Simply select the project (or load the recipe file if you did), open the metadata editor and hit save, it will fix the issue for you.
  12. @AceOfAces_Mod
    1696688789115.png
    Now it works! Amazing tool! Thank you so much!