The elderspark crash thread

Tremayne
Tremayne Posts: 1,708 Chairperson of the Boards
Since I’m hearing a lot of players reporting errors in The Elderspark event, I’m creating this thread to gather all the crashes encountered - by me or anyone else willing to use this template

Node -
Crash type -
Planeswalker - (optional)
Cards/effects involved in crash - (optional)
Crash description - 

Comments

  • Tremayne
    Tremayne Posts: 1,708 Chairperson of the Boards
    edited July 2019
    Node - 2.1 Widespread chaos
    Crash type - App shutdown
    Planeswalker - Koth
    Cards/effects involved in crash - Opponent used unknown loyalty effect, best guess is Massacre. I had a reinforced Verix Bladewing and Greg had a small creature on the battlefield. Vanguard cards, Nahiri (me), Domri and Tibalt (Greg).
    Crash description - Greg used an loyalty effect, which froze the UI completely, menu and battle log unavailable. I returned to desktop in iOS and reopened MTGPQ which made the app crash and restart completely. Node lost.
  • Beclas
    Beclas Posts: 17 Just Dropped In
    Node - 2.1 Widespread chaos
    Crash type - App shutdown
    Planeswalker - Karn
    Cards/effects involved in crash - Opponent used second loyalty effect, Massacre. I had Ugin and a colorless spirit token on the battlefield, opponent had a creature. 
    Crash description - Greg used an loyalty effect, which froze the UI completely, menu and battle log unavailable. After a while the app crashed and closed itself. Node lost.
  • ElfNeedsFood
    ElfNeedsFood Posts: 944 Critical Contributor
    Tremayne said:
    Node - 2.1 Widespread chaos
    Crash type - App shutdown
    Planeswalker - Koth
    Cards/effects involved in crash - Opponent used unknown loyalty effect, best guess is Massacre. I had a reinforced Verix Bladewing and Greg had a small creature on the battlefield. Vanguard cards, Nahiri (me), Domri and Tibalt (Greg).
    Crash description - Greg used an loyalty effect, which froze the UI completely, menu and battle log unavailable. I returned to desktop in iOS and reopened MTGPQ which made the app crash and restart completely. Node lost.
    I had this too.  It happened when the Massacre ability was supposed to reduce my third creature, Etali by -3/-3, it had just killed a Tibalt's Ranger that I had stolen from the Chaos that was in my second creature slot.
  • mrixl2520
    mrixl2520 Posts: 240 Tile Toppler
    Tremayne said:
    Node - 2.1 Widespread chaos
    Crash type - App shutdown
    Planeswalker - Koth
    Cards/effects involved in crash - Opponent used unknown loyalty effect, best guess is Massacre. I had a reinforced Verix Bladewing and Greg had a small creature on the battlefield. Vanguard cards, Nahiri (me), Domri and Tibalt (Greg).
    Crash description - Greg used an loyalty effect, which froze the UI completely, menu and battle log unavailable. I returned to desktop in iOS and reopened MTGPQ which made the app crash and restart completely. Node lost.
    Me three. It's whatever ability causes opponent Domri to destroy his own creatures? 
  • Sherry
    Sherry Posts: 25 Just Dropped In
    I would like to chime in on this thread as well. I had 1st bolas pw. The game froze, then crashed. I was completely taken out of my game. I had 3 charges for that node and lost all of them to this bug.
  • Tremayne
    Tremayne Posts: 1,708 Chairperson of the Boards
    @Sherry - you lost multiple charges on the node?!? Never heard that before and I’m glad I didn’t experience that.
  • BL00DL34F
    BL00DL34F Posts: 4 Just Dropped In
    Node - 4.1 Storm the Citadel
    Crash type - App shutdown
    Planeswalker - Angrath
    Cards/effects involved in crash - Opponent had Tithe Taker on the board. I had Domri, Anarch of Bolas on the board and cast Ob Nixilis's Cruelty targeting the Tithe Taker to exile it.
    Crash description - When I cast Ob Nixilis's Cruelty targeting Tithe Taker, a white spinning orb briefly appeared in the middle of the screen, then the app froze. After about 5 seconds, the app closed and returned me to my home screen. This exact scenario occurred twice, and I lost the node both times.