Connection ErrorBad RequestSession ExpiredSign in requiredForbiddenNot FoundToo Many RequestsServer ErrorBad GatewayService UnavailableGateway TimeoutHTTP Version Not Supported
Session Expired
Your session has expired. Please log in to continue.
Sign in required
You need an account to do that. Sign in or create one — it only takes a minute.
Request Failed
We encountered an issue while processing your request.
Please check your internet connection and try again.
EXAMPLE: PLAYER 1: 10 days, 12 stats, 10 Castles, 10 Mercury, 10 Gold PLAYER 2: 10 days, 10 stats, 10 Castles, 20 Mercury, 10 Gold According to the classic approach, who won? Answer: PLAYER 1. According to the formula, who won? Answer: PLAYER 2. Here's the calculation: Points = ((Days_p + (0.5 * Stats_i) / 396 + (0.25 * Mercury_i) / 200 + + (0.125 * Gold_i) / 1000000 + (0.0625 * Castles_i) / 48) * 1000) / Days_i PLAYER 1 = ((5 + (0.5 * 12) / 396 + (0.25 * 10) / 200 + (0.125 * 10) / 1000000 + (0.0625 * 10) / 48) * 1000) / 5 = 1008 PLAYER 2 = ((5 + (0.5 * 10) / 396 + (0.25 * 20) / 200 + (0.125 * 10) / 1000000 + (0.0625 * 10) / 48) * 1000) / 5 = 1010 Question: who will be considered the winner? What should we rely on? We need to either 1) align the formula and the classic approach, or 2) remove one of them altogether. Or both ratings will be taken into account, and there will be different winners for each rating (this somehow bothers me personally).
Kyle: The answer to this question is given in post #240
P.S. I hope all these "revisions" and rule adjustments apply only to the first stage. For the rest, it will already be a kind of tournament constitution, violation of which will be strictly suppressed. Of course, problems will still "emerge" along the way, but they will be new ones, i.e., nothing that has already been resolved will be changed; instead, something new will be added...
That's absolutely right. Since this is my first experience running a tournament, especially such a large one, not everything can be foreseen at once, and there are "subtle" moments in any business that cannot be immediately seen, and therefore, cannot be taken into account.
After talking with Kyle, it was decided to allow resubmission of saves so that everyone would be on equal footing. And also a strong request: when sending saves, please indicate in the subject line the name of the save (for example: GL_1-1_1_K0Lb@zzeR.CGM), so that the anti-spam bot does not accidentally delete your email.