1. Welcome to the Wargroove support forums. Please check the support FAQs before posting: http://wargroove.com/support

Wargroove Modding Beta: Known Issues and Fixes

Discussion in 'Support' started by Katzeus, Aug 8, 2019.

  1. Katzeus

    Katzeus Chucklefisherman Chucklefish

    Hello everyone,

    Wargroove's long awaited modding update is now available for PC on a beta branch on Steam. We'll be patching the new versions based on reports of issues. We'll try to keep any bug reports updated inside this thread to make it easier on everyone to get an overview of where things are at.

    To opt into the modding beta enter the password caesarisagoodboy. The branch is called public-beta.

    If you're have technical questions check the documentation first, and please only post suspected bugs here make it easier for the developers and players to better review outstanding issues.

    Also take note - modding your game can introduce a player made bugs, so take care of your data and back up your files before opting in!

    Reporting Tips
    • If you're reporting a crash, please be as detailed as possible about what you were doing when it happened. This will help identify the issue much, much faster.
    • Please include your computer details!
    • For any other issues as well, please be as detailed as possible about what you were doing in game so we can try to reproduce
    • Even if the issue has been reported, if you have new details please share!
    Below is a list of issues which we've identified since launching the modding beta. If you're having a problem in this list marked 'need more details' it would be helpful to provide more info - we're still working on reproducing/determining a cause for these issues. If your issue isn't listed here then please be as detailed as possible reporting it so we can review. Always check you have the newest game/system updates before reporting an issue to make sure it hasn't already been fixed!

    Current Version (Beta): 1.32
    The version number is displayed inside the Options menu, at the top left of the screen. Make sure you have the latest version before reporting issues. The game may have been updated.

    Color Key:
    Fixed - This issue should be resolved in the recent update
    In Develop - Fixed or have a solution in development for a future update.
    Investigating - We have reproduced or confirmed this is an issue, but are still developing a solution
    Need More Details - We're aware of the issue, but don't yet have enough information to reproduce/fix

    Below are some reports from this thread, consolidated to make it easier to scan if an issue has been reported or to find common threads between reports for the same issue.

    These reports are not confirmed bugs, this is just a list of report posts formatted for readablity. If your issue is not listed here that doesn't mean it's not being read/acknowledged! If an issue is determined not to be a bug it will be removed from this list to keep it readable.
    We plan to continue to collect reports and identify issues to include in updates, but we'll need player reports to be as detailed as possible in order to properly identify/fix bugs. Our priority obviously will be any bugs which impact gameplay like crashes.

    There are still some issues which have been reported, but are not listed above. This is usually because we haven't seen enough reports/gotten enough details to identify it for escalation. If you've having an issue not listed here please report it with as much detail as possible so we can evaluate it.

    If you have a crash bug, please attach your crash log (located at %APPDATA%\Chucklefish\Wargroove\log.txt).

    Save file location: %APPDATA%\Chucklefish\Wargroove\save\

    While some issues have threads dedicated to them - posting details either here or in the corresponding thread would be helpful - we'll do our best to make sure any new info/workarounds are communicated in both places to make sure players can find that info easily.

    If you're reporting a bug which was originally reported outside the forums please make sure to add a link to the original post - we may need to contact that player directly for more details.

    We're going to continue monitoring these and any newly reported problems, so please provide as much information as possible for any issues you may run into! Hope you enjoy this update - we're looking forward to seeing what mods the community comes up with! Thanks everyone!!
    • Innocience

      Innocience Lucky Number 13

      Once activated mod containing unit with codex entry crashes game when said codex entry is selected but mod is deactivated.

      Description / How to reproduce:
      I made a mod which adds another unit alongside a codex entry to the game.
      Starting a match and looking at said codex entry works fine while the mod is active.
      After starting a new match without the mod, singleplayer or multiplayer, the codex entry of this unit still remains.
      Selecting the entry again without the mod being active crashes the game.

      Attached are the log file from the crash as well as the packed mod that causes the crash.

        Attached Files:

        Shubeans likes this.
      • kingoftheconnors

        kingoftheconnors Void-Bound Voyager

        Spectators don't automatically load mods if entering the game partway through

        Description / How to reproduce:
        I wanted to spectate a match between two other modders playing the absoultely awesome Age of Wargroove mod. If you enter the lobby before the game starts, spectating mode runs perfectly; HOWEVER, if you try entering the match after it has begun, the game will (presumably) not load the assets for the mod and the game will crash, even if the mod is up-to-date, or even if you've already entered the game and you're simply re-entering it.

        Attached are the log file from the crash as well as the exact state of the packed mod that causes the crash.

          Attached Files:

        • kingoftheconnors

          kingoftheconnors Void-Bound Voyager

          Campaigns don't update properly when changing mod versions.

          Description / How to reproduce:
          Create a mod and use it for a campaign. Then make a new version of the mod and try to edit that same campaign again. When the campaign tries to update its mod, it would give a box saying "Unknown Error" and then if you try pressing OK again, it crashes.

          If, after the first error, you press "cancel", you can go back into the campaign and even start it, but it will have uninstalled the mod, even though it says the mod is active in the mods list. You are required to turn the mod off and then back on to get regular editing capabilities with the mod once again (this scenario is what is being played out in the first log file).

          If, after the first error, you try to cancel the upgrade and press okay, you will get an error and a crash (this scenario is played out in the second log file).

          Attached are the log files from the crashes as well as the exact state of the packed mod that causes the crash.

            Attached Files:

          • Shubeans

            Shubeans QA Wizard Chucklefish

            Thanks for reporting these issues over, even if no one is responding we are gathering them!

            Spectator and Codex issues should now be fixed, along with a few other issues:
            " If you specify multiple weapons for a unitClass in the unit.yaml, game will crash saying weapon is not found."
            "Wargroove isn't updating the cache properly while updating mods that come packed with maps."

            Campaigns not updating has been logged and should hopefully be fixed in the next update,
            thank you for reporting :)

            Share This Page