Kicked from Dreadnought Queue

Bug Report Section Matchmaker
1

Arch queued for a Dreadnought Sector - Poseidon Complex. At 12GS/day, it’s highly desirable.

 

We were kicked from the game against STORM halfway through by a server problem and drew out of the tournament despite being substantially ahead in battle.

 

https://www.youtube.com/watch?v=0sQIOIWQb00

 

Fortunately we had a second wing attacking that sector. We queued up, and eleven seconds before the battle started, a ninth player joined our wing. It forced us out of the queue and caused us to forfeit.

 

We were kicked from the game and queue a total of TWO TIMES. There were no systems in place to protect this, and as a result a corporation that never fought a match received the GS sector we put FOUR attacks into.

 

https://www.youtube.com/watch?v=bQxZCIg2vy4

 

RDS got the sector on freebie thanks to servers. This is beyond infuriating and needs to be addressed _ immediately.  _I am advocating to reset the sector and reset the tournament with the past registered teams for tomorrow. Perhaps there is a better solution, but the current result is not the right one.

 

Please get the word out on this as quickly as possible.

Thank you,

 

NuclearHail

2

:frowning: unfortunately quite a few corporations through the day got the same problem, and were kicked out of the match

3

:frowning: unfortunately quite a few corporations through the day got the same problem, and were kicked out of the match

 

We’d even prepared for that by having a second wing. Except that got kicked too. 16 players got screwed out of both dreadnought battles and Arch got screwed out of the GS sector.

 

Perhaps they should reset the entire map and just let everyone try again tomorrow.

4

+1.

 

Arch was ready and prepared to fight for the rightful ownership of the sector, which got basically given for free due to server problems and to the lack of a better dreadnought queue system. This issue does need to get addressed ASAP, or the new sector conquest won’t be functional.

5

Please create a full bug report and attach the log files.

6

It was temporarily problem