EVE Alliance Tournament Discussion

 
  • Topic is locked indefinitely.
 

ATXIV Match 123C Statement

First post
Author
C C P Alliance
#1 - 2016-10-16 19:22:26 UTC  |  Edited by: CCP Logibro
Hello Pilots

In match 123C of Alliance Tournament XIV, there were a number of pilots that disconnected during the match, as well as reports of issues from pilots that ships and modules were not responding as they normally should. In this instance, the following rule is applied:
Quote:
The match simulation is taken as is.

This means that regardless of whether the server experiences issues during a match, a player or players experience connection issues or anything else happens that may interfere with a pilots ability to control their ship, once the countdown to start the match has completed the match will run to completion with the final result standing. This is part of the reality of having the contest be run with participants connecting over the internet.

As such, the result of the match will stand. This ruling is not subject to further debate or appeal.

CCP Logibro // EVE Universe Community Team // Distributor of Nanites // Patron Saint of Logistics

@CCP_Logibro

#2 - 2016-10-18 07:23:53 UTC  |  Edited by: Valkin Mordirc
Stealth unlock?


Why is it not up for debate?

Also does CCP not have the ability to check if it was server side rather then client?

I understand the rule and the thought behind it. But if CCP is having instability that's being reported during the time of the AT should some sort of precaution should've been made? I remember seeing Reddit blow up about it during that week.

You guys look at Reddit more then your own forums so I would assume you where aware of it.
#DeleteTheWeak
C C P Alliance
#3 - 2016-10-18 12:28:36 UTC
For this particular type of issue, the rule is pretty definitive.

We do have the ability to check if it was a server issue or not. In this case, it was not a server issue.

CCP Logibro // EVE Universe Community Team // Distributor of Nanites // Patron Saint of Logistics

@CCP_Logibro

Coalition of the Unfortunate
#4 - 2016-10-18 12:48:38 UTC  |  Edited by: Sentient Blade
Big congratulations to Tuskers, all the same it feels like there's a bit of a cloud hanging over the top of it, at the very least because, rightly or wrongly, to an external observer, it looks like CCP dropped the ball (even though it was a major third party issue).

Can't be helped, but perhaps a rule change would be beneficial where it can be shown beyond reasonable doubt that there was some kind of infrastructure outage.

Something to consider for next year perhaps.
Pandemic Legion
#5 - 2016-10-18 15:00:34 UTC
CCP Logibro wrote:
For this particular type of issue, the rule is pretty definitive.

We do have the ability to check if it was a server issue or not. In this case, it was not a server issue.


Sorry, what?

Something happened to cause several people from both teams to lag and or disconnect. If it wasn't a server issue, what other explanation could there be?
Coalition of the Unfortunate
#6 - 2016-10-18 15:29:25 UTC  |  Edited by: Sentient Blade
Mr Rive wrote:
Something happened to cause several people from both teams to lag and or disconnect. If it wasn't a server issue, what other explanation could there be?


One of the ISD mentioned elsewhere that Level 3 fell over. So it was a "server" (router) issue. Just not their servers.
Pandemic Legion
#7 - 2016-10-18 15:44:10 UTC
Sentient Blade wrote:
Mr Rive wrote:
Something happened to cause several people from both teams to lag and or disconnect. If it wasn't a server issue, what other explanation could there be?


One of the ISD mentioned elsewhere that Level 3 fell over. So it was a "server" (router) issue. Just not their servers.


if thats the case then, it was a server issue.

Some clarification would be greatly appreciated on this issue.
Pandemic Legion
#8 - 2016-10-18 16:13:43 UTC
ESPORTS!
Pandemic Legion
#9 - 2016-10-18 17:24:13 UTC
THE LOGS SHOW NOTHING!
Pandemic Legion
#10 - 2016-10-19 12:56:17 UTC
Losing's losing. That's the way it goes.

Please consider to coding a way to stop a system for the next year. I assume since you can already go tidi superfast after 10 minutes you might as well be able to stop time on a node as well. Random single disconnects can happen during a match, but when half of a team plus large numbers of individuals all over New Eden get "socket closed" it is just bad for EVE as esport. Other bigger games already added such things to their client and tournaments. Thanks!

Winner ATXI , 3rd place ATXII, winner ATXIII, 2nd ATXIV - follow me on twitter: @ForlornW

Snuffed Out
#11 - 2016-10-19 19:44:07 UTC
+1 on the pause matter. Other games have it now and they solve issues when they happen. As one of the teams suffered a disconnect logi i feel that we need this.
End of Life
#12 - 2016-10-21 05:38:17 UTC
Also +1 on the pause thing

Also so Logibro - when is the date for AT XV :)
Forum Jump