Saturday, April 25, 2009

Tool Times Two

My Brute Manager v0.4 had finally been released with a whole slew of extra features! And shortly after that, El Bruto Manager was released--which is just My Brute Manager for the Spanish version of My Brute, El Bruto.

9 comments:

  1. I have uninstalled and re-installed v.0.4 several times with no success.

    ReplyDelete
  2. Success with what? Is it not working? Is something broken?

    ReplyDelete
  3. The manager doesn't appear at ALL. I have uninstalled and re-installed the script multiple times and made sure there aren't any older versions and it still doesn't appear. Not that I also set my browser to keep no history of anything.

    ReplyDelete
  4. That sucks, I'm sorry its not working, I testing my browswer with a 'don't remeber anything' stripped config and it still worked.
    Hopefully you can help me figure out what's wrong, from start to finish, here's all the requirements for MBM to work:
    *Go To Tools>GreaseMonkey, make sure enabled is checked
    *Go To Tools>GreaseMonkey>Manage User Scripts and select My Brute Manager, make sure towards the bottom left of the page, Enabled is checked and that the list of included pages has 5 pages listed
    *Go To Tools>Options>Content, Make sure enable Javascript is checked.
    *Go to the Cell (.../cellule/) page of a brute
    While on that page:
    *Go to Tools>Error Console, click the "Clear" button
    *Refresh the Cell page
    *Go back to the error console, 5 warnings are expected from http://data.mybrute..... But there should not be any other errors.

    If any one of those things does not behave as I describe, let me know, we've found the problem.

    ReplyDelete
  5. I got this:

    Error: config_brute_levels.split is not a function
    Source File: *path*/gm_scripts/my_brute_manager/my_brute_manager.user.js
    Line: 134

    var brutelevels=config_brute_levels.split(";");

    ReplyDelete
  6. Awesome!! I know exactly how to fix that! I'll get cracking on it right now.

    ReplyDelete
  7. Okay version 0.4c should fix your problem, give it a try and let me know!

    Thanks a lot for your help!

    ReplyDelete
  8. Great! I'm glad. And thanks again for helping me find that error, especially so it's fixed before v0.5 inherited the problem.

    Enjoy!!!!!

    ReplyDelete