(Resolved) SRD Super Tools causing Maximum Call stack size Error

● ARCHIVED · READ-ONLY
Started by VideoRelaxant1 8 posts View original ↗
  1. sigh... I'm terrible with things like this

    The best thing in the world, is when SRD refuses to help with problems... with his own plugins...

    Anyway, this is the issue, in order to get the plugin to WORK, it has to be on top, but when it is on top...

    Screen Shot 2018-08-29 at 12.22.39 PM.png


    I know i've been... demanding on these threads, for the little time i've been active, but I really have no clue what is causing it, all of my plugins are organized by creator, and all "--------------------------" plugins are off, that is what caused this issue the last time. There is no duplicate SuperTools.

    so... help:kaocry:




    please?
  2. Give us a screenshot of the console output (F8) with the entire error sequence
  3. using mac it's a bit different i think i'm not sure but is this what you are looking for?
    Screen Shot 2018-08-29 at 1.26.42 PM.png
  4. (edit: sorry for double posting, i forgot... i'm not very active here, so I'm not used to the layout or functions yet)

    let me try getting rid of the keyboard plugin, just in case
  5. What version of MV are you using? I don't remember what error I got but I know when things updated to 1.6 that SRD's Super Tools stopped working for me. My solution was to stick with 1.5.1 on that game I was developing.

    Probably not the answer you were hoping for, but that's what I had encountered with SRD's plugins.
  6. I'm using the steam version of 1.6.1
    would it be dangerous to revert to 1.5 if possible
  7. Meike said:
    This is the thread with the changlog for 1.6.1 https://forums.rpgmakerweb.com/index.php?threads/rpg-maker-mv-v1-6-1-stable-release.96715/

    And this thread has instructions on downgrading (it's in a spoiler tag) https://forums.rpgmakerweb.com/index.php?threads/rpg-maker-mv-1-5-2-ßeta.92016/

    I'm not too familiar with the ups and downs of the two versions, but both were stable releases, so it should be fine to revert if you really need to.

    I reverted to 1.5.1, and it fixed the issue.


    Thank you for your help