⚠ BEFORE POSTING YOUR ISSUE:


1. Check if it exists already in BUGS/ISSUES UNDER INVESTIGATION
2. Read and use our REPORTING GUIDE before posting your issue
3. Follow our Support Ticket Guide to prevent misunderstandings with the Support.

Not able to use Rick Rude hard mode blitz

CaseyPlatinum
CaseyPlatinum Member ✭✭✭
edited January 2021 in BUG REPORTS

I have a 4ss Rick rude tech. I’m not able to put him in the hard mode blitz.

the blitz shows Any Rick rude.


also it says minimum 7. Is this correct for hard mode ?


Tagged:

Comments

  • Blade72
    Blade72 Member ✭✭

    Same here. Think it's a copy from hard mode where it requires a hall of fame Rick rude with wrong picture

    Think the hard is all messed up because since when did hard require 7 superstars?

  • Same thing here. It shows 3sb Rude, but the selection screen doesn't show any superstars as eligible.

  • TheBear41
    TheBear41 Member ✭✭✭

    Seems like an issue to me as well!

  • Same issue here. Is it suppose to show HOF Rick Rude instead? Also how come so many superstars required for normal and hard?

  • JackStone
    JackStone Member ✭✭

    Surely the 7 required for Hard Mode is a little much too.

  • NateDogg833
    NateDogg833 Member ✭✭

    I am also having the issue with Rick Rude in the blitz. 7 members required for hard mode is a little much. Shouldn't this be 5 superstars required?

  • TheNextAD
    TheNextAD Member ✭✭✭

    @Firpo I don't know what's going on, but now Rude's icon is gone....

    rudegone.PNG


  • This content has been removed.
  • freezerburn
    freezerburn Member ✭✭

    Anyone going to acknowledge this? Losing possible play time in a timed event.

    The slot for Rude is not working in normal and hard modes.

    Also 7 superstars is a bit extravagant.

    Pls advise asap. Thanks!

  • Rude works now in hard mode

    Screenshot_20210126-162852_WWE Champions 2021.jpg


    Still requiring 7 though

  • Stagger Lee
    Stagger Lee Moderator Moderator
    edited January 2021

    This is fixed. Thanks to those who helped get this fixed.

This discussion has been closed.