**Mastery Loadouts**
Due to issues related to the release of Mastery Loadouts, the "free swap" period will be extended.
The new end date will be May 1st.
Options

Aegons Synergy with Proxima (Combo Shield) not working

token555token555 Posts: 22 ★
in Bugs and Known Issues
As the title states, the aegon synergy with proxima is not triggering combo shield. First time getting hit in the match and I am losing my active combo.

Act 6.1.5 ( the crossbones boss map)
Saw it happen in the fight against agent venom, the fight against Proxima and also fight against Electra.

Went into realm of legends to test and it is broken there as well, so Im guessing its universally broken.

Playing on an iPhone X.
I'm on the latest version of the game (25.0)

Comments

  • Options
    vmp1995vmp1995 Posts: 6 ★
    I am the same problem, but with star lord.
    Playing on Android 9
  • Options
    Dr_Z01dbergDr_Z01dberg Posts: 512 ★★★
    Same issue here. Both with Proxima and Star Lord, Aegon still broken.

    Playing on IPhone X with 25.0
  • Options
    -sixate--sixate- Posts: 1,532 ★★★★★
    Same issue, combo shield synergy not working for SL Ægon and Proxima.

    Nate 9 Android 9
  • Options
    Jwebb33Jwebb33 Posts: 6 ★
    Same issue with either champion as a synergy in labyrinth of legends
  • Options
    Russj213Russj213 Posts: 17 ★
    Same issue planning on note 9 Samsung
  • Options
    Russj213Russj213 Posts: 17 ★
    Also found aegon combo shield not working when opponent uses a passive evade aginst him
  • Options
    Yarg2015Yarg2015 Posts: 111 ★
    I am also experiencing the same problem. R5 Aegon on iOS 13 iPhone 11 Pro Max

    Have any of you opened a ticket with Kabam?
  • Options
    BlindChickenBoyBlindChickenBoy Posts: 22 ★
    Same issue, ticket opened yesterday.
  • Options
    RaiserRaiser Posts: 424 ★★
    yeah me too, proxima and aegon in LoL broken
  • Options
    Yarg2015Yarg2015 Posts: 111 ★
    I opened a ticket with video this morning
  • Options
    Kabam ZibiitKabam Zibiit Posts: 7,033
    Hey there, we're aware of this issue and the team is looking into it. We've got a thread going for it here where we will keep everyone up to date.
This discussion has been closed.