Waluigi's AI is Broken

Discussion in 'Waluigi' started by Survivian, Oct 11, 2016.

  1. Survivian

    Survivian The Rando-Est of Brandos Minus Backroom

    Messages:
    98
    Location:
    My House
    B- FC:
    3957-3720-8220
    Main:
    I don't know if anyone else has had this problem, but whenever you go up against any AI Waluigi, if he is not directly above the ledge when he's offstage, he doesn't recover.

    He still has all of his jumps and he could've been hit high and out with tons of time, but he just tumbles to his death.

    Again, I may be the only one with this problem, but I wonder if other people have the same issue.

    (If anyone else has evidence of this, please post a .gif or a video as I have no capture card or any good equivalent.)
     
  2. Darxmarx

    Darxmarx The Learning Star Warrior

    Messages:
    537
    Location:
    Pop Star

    B- FC:
    5117-0129-8473
    Main:
    First off, welcome to the forums! Enjoy your stay and stuff ~

    BrawlEx characters with noticeably different movesets tend to not recover well. Rarely do the current versions of Mewtwo and Waluigi even use their upB.
    Everyone playing the current Minus build has these characters with broken AI, so you're good. I would post evidence if I could, but all people have to do is quickly fight a Mewtwo or Waluigi CPU to find out for themselves.
     
  3. Survivian

    Survivian The Rando-Est of Brandos Minus Backroom

    Messages:
    98
    Location:
    My House
    B- FC:
    3957-3720-8220
    Main:
    Alright. Glad to see I wasn't the only one with this problem.

    Can't wait for them to fix this bug once the full 4.0 version comes out.
     
  4. Mario3785

    Mario3785 Enjoyer of Ironic Memes

    Messages:
    60
    Location:
    'Murica
    Main:
    Yeah, the same thing happens to me. Makes fighting Waluigi and Mewtwo a little too easy...
     
  5. Pin Clock

    Pin Clock Project Leader Minus Backroom

    Messages:
    1,014
    Location:
    Jersey
    We were aware of this before release but ran out of time to fix.

    It will be fixed for 4.0f.
     

Share This Page