Foundations Jumpstart Error

Hey, thanks for the report! We're looking into this. So far, we can tell that many people are able to play fine, but some people are hitting a problem that looks like the one you describe. We don't know exactly what's happening yet, but we suspect there's a problem with how one or more packets are configured

Edit: Ok, we know what's happening and are working on deploying a fix. Basically, some of the packets got filled out with the wrong card IDs, so they're causing errors.

The problematic packets are:
- Legion
- Grave Robbers
- Stoked
(Note: For some of these the card isn't a 100% pull, so you may have a version of these packets that works fine)

If you are affected, please go ahead and resign and choose a different set of packets. We'll be sending automated refunds via the inbox for affected players, so you'll get your entry fee back.

Sorry about this, and we hope to have the packets fixed soon

Edit Edit: We have now fixed the offending packets, so all should be safe in the land of Jumpstart.
Again, if you are in the broken state, this just fixed new packets, not the ones you have, so please resign and pick again. There will be a refund in your inbox shortly

To get ahead of the inevitable "Why didn't you QA this?" question, we did!
But.
The bug is that some of the packets got configured with the Pioneer Masters version of a card, rather than the Jumpstart 25 version (there are a few cards that overlap between the sets). This is unfortunately easy to do in our tools, and, worse, it won't show up in most of our QA passes, because most of those passes are done in a version of the game that has access to Pioneer Masters, so it wasn't throwing this error. Only the final testing is done in an environment that is more locked down. Testing is lighter there, particularly over features that have already been fully tested, so we didn't test every packet, and must have missed these.

This is obviously a hole in our process, and we're discussing the right way to fix it.

That's very strange, and I'm not immediately seeing what would be going wrong. Can you try going to Settings -> Report Bug -> Validate Bundles and see if that cleans anything up?

At this point I think you'll need to contact CS. They may be able to force-kick you from the event, and, if not, we would need more information to track down what's going on

Hrm. If you PM me your user#1234, I'll get someone to look into what's going on. You're in an interesting enough stuck state that it's worth digging in.