Unable to choose second pack: Jumpstart: Jump In!
I played a few games of the jumpstart event, Jump In!. On my third deck choice, I was able to choose my first packet, but not my second.
On the packet selection screen, it showed that I had chosen the "Warriors" packet as "Packet 1" and the "Rock and Roll" pack as "Packet 2" but still requested I choose a packet. I tried choosing again, and it showed "Packet 3" over "Elves", and again I selected the other packet, "Roiling", and it showed "Packet 4". No resolution would get me out of the screen and into games, so I exited.
After re-launching MTGA, I can open Jump In! and select Choose Packets. When I do, it shows my first choice on the left, but no options for my second choice.
-
BUG.jpg 234 KB -
4DECA5C7-1443-4A2B-B0CD-13D9ED9912B8.png 2784 KB -
Log20211014_182232.log 1722 KB -
jump in bug.jpg 102 KB -
Log20211014_182232.log 1722 KB -
jump in bug.jpg 102 KB -
Log20211014_182232.log 1722 KB -
jump in bug.jpg 102 KB -
UTC_Log - 10-14-2021 17.26.58.log 5860 KB -
UTC_Log - 10-14-2021 16.00.54.log 11975 KB -
Captura de pantalla (97).png 1000 KB -
Log20211014_152409.log 7 KB -
Log20211014_133135.log 7 KB -
Screen Shot 2021-10-14 at 1.37.07 PM.png 3222 KB -
Log20211014_184130.log 2143 KB -
PackStuck.png 1719 KB -
Log20211014_093642.log 1769 KB -
jump in bug report2.png 683 KB -
jump in bug report.png 1165 KB -
Log20211014_115111.log 5 KB -
jump in bug report2.png 683 KB -
jump in bug report.png 1165 KB -
Log20211014_115111.log 5 KB

-
teod19#94666 commented
Same issue.
-
techtool317#25219 commented
Same issue.
2021.10.0.1052.893514
-
Lord OttomBottom#44096 commented
Same issue. Was able to play through once then issued occured after play and claiming prize after win.
Windows 10
2021.10.0.3913.893514
Repro'd 4/4 after initial playthrough.
Steps:
1. Choose Jump In as your game option from the match list.
2. Pay fee to start
3. Choose your first deck half
4. Choose your second deck half, notice that at this point, the second half will be selected but you cannot continue.Notes:
On initial iteration of error, the second half deck choice (Packet 2) would allow me to choose one, click confirm, then allow me to choose another half deck with Packet 2 still chosen (shown as Packet 3).
Once I restarted the application, Only packet 1 from the last login would appear with no second packet options would appear.
-
Orangehunter795#90999 commented
Here's some pictures of the bug. Notice that after selecting my second pick, the "Confirm Pick" button is grayed out, and it won't let me click anything to continue, except the remaining picks. After selecting the next and the next, it still won't let you click "Confirm Pick." It's impossible to continue or cancel.
-
Sykrosis#67697 commented
PLEASE FIX.
-
Sykrosis#67697 commented
PAID FOR THE NEW "JUMP IN" EVENT, CANNOT SELECT 2ND PACK.
UPON CLOSING AND REOPENING, MY FIRST PACK IS SELECTED BUT WILL NOT DO ANYTHING FURTHER. CANNOT PROCEED TO PICK 2ND PACK AT ALL, ALL OPTIONS GREYED OUT. -
last.pe#70076 commented
Same here, stuck at the second pick, on mobile Android.
-
Berethian#68934 commented
Same here. *******.
-
claire#05587 commented
Same, I tried this on desktop, it stuck and I couldn't confirm the second packet. Switched to android, the second packet choices didn't appear at all. Checked back on desktop, can select packets and confirm but it doesn't move forwards (see screen)
-
Red Irish#01583 commented
I thought exiting out would solve it, but now it is just frozen on the first choice.
-
Vikingligr#16773 commented
Exactly the same for me
-
wobby#45590 commented
Jump In Event can’t select second pack
-
Orangehunter795#90999 commented
Same issue.
-
RampantGryphon#08242 commented
Similar issue for me too, though I was able to get one game in first.
-
BvBPL#03280 commented
I am experiencing the same issue.
-
Knight_99#25377 commented
Got that too, went out and back in and can't get past first selction of packet
-
armor2184#55160 commented
I had the exact same issue. This was my second event and now it is stuck on the second packet selection. I even restarted the client (PC) in an effort to correct the issue.
-
SpicyMato#96546 commented
Me, too. On Android.
-
cbear#35319 commented
Same here
-
FunkyDuffy#52248 commented
Same issue.