Introducing Jasmine - v2.022

**Preybird** · 09-20-2013, 10:09 PM

I'm getting unable to connect to server messages, not during game but on the challenge screen. Can't search IGN at all due to it.

**FDL** · 09-20-2013, 10:20 PM

Cancelled a game after waiting for an opponent for about a minute.

When I was back at the Challenge screen, I could see myself in a game with Danae and the server said I was already in a game if I tried to join/watch anything.

Win 8/Chrome

**Deja Vu** · 09-20-2013, 10:21 PM

What FDL said.

Good job.

**danae** · 09-20-2013, 10:24 PM

Originally Posted by Fou DeLile

Cancelled a game after waiting for an opponent for about a minute.

When I was back at the Challenge screen, I could see myself in a game with Danae and the server said I was already in a game if I tried to join/watch anything.

Win 8/Chrome

What? You quit that game? LOL. I'm still in it. It says waiting for players but when I try to cancel it says game has already started. 8 minutes going and it still hasn't timed out. I'll exit it now. Windows 7/Firefox

**Natethegreat** · 09-20-2013, 10:33 PM

Thank You SO Much! Awesome!

**FDL** · 09-20-2013, 10:41 PM

Originally Posted by danae

What? You quit that game? LOL. I'm still in it. It says waiting for players but when I try to cancel it says game has already started. 8 minutes going and it still hasn't timed out. I'll exit it now. Windows 7/Firefox

I was still at the waiting for players stage when I quit...

**Mightyoak713** · 09-20-2013, 11:34 PM

Foils look good. At least the ones I got to look at.

**ahueahueahuea** · 09-21-2013, 12:07 AM

I think it's obvious someone didn't build a complete test suite.

**NachyoChez** · 09-21-2013, 01:24 AM

Originally Posted by ahueahueahuea

I think it's obvious someone didn't build a complete test suite.

Triple-A studios with millions in development and beta testing still have bugs upon release; you can't test for everything.

Simple fact of life, there's no test than can equate to the stresses of a live release on the software!

That said, we're looking into the issues with Chrome to see if we can figure out what's causing it. For the most part, simply restarting the match seems to work.