Forum Discussion

Re: 4th & -18

@ya_boi_j127 Thanks and that is was the only thing that stood out from it. Did you notice anything weird happen leading up to the play? Was it just a standard interception like any other one?

I've seen something like this reported on the forums once or twice in the last couple years, seems very rare (fortunately). If we continue to get more reports on this post with specific examples on what time it happened along with video examples that can help the QA team determine what triggers this from happening.

I'd be bummed out to see 4th and -18th though after pulling off an interception though, sorry you had to experience that.

5 Replies

  • ya_boi_j127's avatar
    ya_boi_j127
    New Adventurer
    4 years ago
    @EA_Blueberry The only thing I remember was catching the interception then mistakingly hit the lateral button but the ball went to one of my players.

    Other than that, everything else was normal
  • EA_Blueberry's avatar
    EA_Blueberry
    Icon for Community Admin rankCommunity Admin
    4 years ago
    @ya_boi_j127 Do you know if when you lateraled the ball, your player traveled about 18 yards? Sounds like that could be what triggered it.
  • EA_Blueberry's avatar
    EA_Blueberry
    Icon for Community Admin rankCommunity Admin
    4 years ago
    @ya_boi_j127 Thanks. We'll keep an eye out for more reports and good to have this logged. On the bright side, this seems like a very rare bug as it's hardly been brought up. I doubt using a lateral right after an interception every time will cause this so all the stars must have aligned in some way to result in this outcome. Nonetheless, sorry this happened and thank you for coming to the forums to report it! 🙂
  • Neo_Novalis's avatar
    Neo_Novalis
    Hero+
    4 years ago

    I did some tests trying to do a lateral after an INT while recording the plays (I did it by replaying some MUT Solo Challenges). so far, I did not manage to reconstruct the bug, but I have to say that I was not very successful yet in finding a Solo Challenge which allows me to easily force an INT. therefore I was not yet able to collect a broader sample of cases / plays which might help identifying the pattern that triggers this bug. If I find some time, I will continue trying...