Grid2 no longer working after I deleted the AddOn-Folder while the game was running #948


Closed
  • austria_nope_no_kangaroos created this issue Feb 10, 2021

    Hello, I hope you guys can help me because without Grid2 im lost :(

    What version of Grid2 and game type (classic or retail) are you using ?

    I am using version r533 (Downloaded here: https://www.gnarlyguides.com/wotlk/addons/grid2/). I am playing on a private server (Whitemane).

     

    What game client version (windows or mac) and language are you using ?

     The version is 3.3.5a, im on Windows10 and language is english.

     

    What steps will reproduce the problem?

    Just starting the game. Let me explain what (I think) happened. Grid2 worked perfectly fine. Then I had some interface problems (not Grid related) and a GM told me to try to remove all addons to see if that fixes it. I did so but idiot me forgot to close the game before that. So I removed all the addons from the game folder with the game still running, which most likely screwed things up.

      
    Did you try having Grid2 as the only enabled addon and everything else disabled?

    Yes, still same issue.

     

    Was it working in a previous version? If yes, which was the last good one?

    This version worked fine before I screwed it up.

     

    Do you have an error log of what happened? If you don't see any errors, make sure that error reporting is enabled (`/console scriptErrors 1`) or install [BugSack](https://mods.curse.com/addons/wow/BugSack).

     

    I get these Error messages in chat upon Login and/or Opening the Grid GUI:

      

    Please provide any additional information below.

     I can open the GUI as usual but all the indicators are gone (the list is empty). However, when I cast a Heal on myself grid shows it, so there has to be data somewhere. Also when I create a new indicator it is gone as soon as I relog. Can you guys please help me?

     

  • austria_nope_no_kangaroos closed issue Feb 10, 2021
  • austria_nope_no_kangaroos posted a comment Feb 10, 2021

    I somehow managed to fix it myself. After resetting several times it suddenly works


To post a comment, please login or register a new account.