-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Calculate and display Elo change on server #7960
Changes from all commits
3d0808e
c570634
c52934a
2c8d3c5
ba216fb
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -70,25 +70,43 @@ export class LadderStore { | |
const formatid = this.formatid; | ||
const p1 = Users.getExact(p1name); | ||
const p2 = Users.getExact(p2name); | ||
room.update(); | ||
room.send(`||Ladder updating...`); | ||
const [data, error] = await LoginServer.request('ladderupdate', { | ||
|
||
const ladderUpdatePromise = LoginServer.request('ladderupdate', { | ||
p1: p1name, | ||
p2: p2name, | ||
score: p1score, | ||
format: formatid, | ||
}); | ||
|
||
// calculate new Elo scores and display to room while loginserver updates the ladder | ||
const [p1OldElo, p2OldElo] = (await Promise.all([this.getRating(p1!.id), this.getRating(p2!.id)])).map(Math.round); | ||
const p1NewElo = Math.round(this.calculateElo(p1OldElo, p1score, p2OldElo)); | ||
const p2NewElo = Math.round(this.calculateElo(p2OldElo, 1 - p1score, p1OldElo)); | ||
|
||
const p1Act = (p1score > 0.9 ? `winning` : (p1score < 0.1 ? `losing` : `tying`)); | ||
let p1Reasons = `${p1NewElo - p1OldElo} for ${p1Act}`; | ||
if (!p1Reasons.startsWith('-')) p1Reasons = '+' + p1Reasons; | ||
room.addRaw(Utils.html`${p1name}'s rating: ${p1OldElo} → <strong>${p1NewElo}</strong><br />(${p1Reasons})`); | ||
|
||
const p2Act = (p1score > 0.9 || p1score < 0 ? `losing` : (p1score < 0.1 ? `winning` : `tying`)); | ||
let p2Reasons = `${p2NewElo - p2OldElo} for ${p2Act}`; | ||
if (!p2Reasons.startsWith('-')) p2Reasons = '+' + p2Reasons; | ||
room.addRaw(Utils.html`${p2name}'s rating: ${p2OldElo} → <strong>${p2NewElo}</strong><br />(${p2Reasons})`); | ||
|
||
room.rated = Math.min(p1NewElo, p2NewElo); | ||
|
||
if (p1) p1.mmrCache[formatid] = +p1NewElo; | ||
if (p2) p2.mmrCache[formatid] = +p2NewElo; | ||
|
||
room.update(); | ||
|
||
|
||
const [data, error] = await ladderUpdatePromise; | ||
let problem = false; | ||
|
||
if (error) { | ||
if (error.message === 'stream interrupt') { | ||
room.add(`||Ladder updated, but score could not be retrieved.`); | ||
} else { | ||
room.add(`||Ladder (probably) updated, but score could not be retrieved (${error.message}).`); | ||
} | ||
problem = true; | ||
} else if (!room.battle) { | ||
Monitor.warn(`room expired before ladder update was received`); | ||
problem = true; | ||
} else if (!data) { | ||
room.add(`|error|Unexpected response ${data} from ladder server.`); | ||
|
@@ -108,37 +126,7 @@ export class LadderStore { | |
return [p1score, null, null]; | ||
} | ||
|
||
let p1rating; | ||
let p2rating; | ||
try { | ||
p1rating = data!.p1rating; | ||
p2rating = data!.p2rating; | ||
|
||
let oldelo = Math.round(p1rating.oldelo); | ||
let elo = Math.round(p1rating.elo); | ||
let act = (p1score > 0.9 ? `winning` : (p1score < 0.1 ? `losing` : `tying`)); | ||
let reasons = `${elo - oldelo} for ${act}`; | ||
if (!reasons.startsWith('-')) reasons = '+' + reasons; | ||
room.addRaw(Utils.html`${p1name}'s rating: ${oldelo} → <strong>${elo}</strong><br />(${reasons})`); | ||
let minElo = elo; | ||
|
||
oldelo = Math.round(p2rating.oldelo); | ||
elo = Math.round(p2rating.elo); | ||
act = (p1score > 0.9 || p1score < 0 ? `losing` : (p1score < 0.1 ? `winning` : `tying`)); | ||
reasons = `${elo - oldelo} for ${act}`; | ||
if (!reasons.startsWith('-')) reasons = '+' + reasons; | ||
room.addRaw(Utils.html`${p2name}'s rating: ${oldelo} → <strong>${elo}</strong><br />(${reasons})`); | ||
if (elo < minElo) minElo = elo; | ||
room.rated = minElo; | ||
|
||
if (p1) p1.mmrCache[formatid] = +p1rating.elo; | ||
if (p2) p2.mmrCache[formatid] = +p2rating.elo; | ||
room.update(); | ||
} catch (e) { | ||
room.addRaw(`There was an error calculating rating changes.`); | ||
room.update(); | ||
} | ||
return [p1score, p1rating, p2rating]; | ||
return [p1score, data!.p1rating, data!.p2rating]; | ||
} | ||
|
||
/** | ||
|
@@ -149,4 +137,37 @@ export class LadderStore { | |
static async visualizeAll(username: string) { | ||
return [`<tr><td><strong>Please use the official client at play.pokemonshowdown.com</strong></td></tr>`]; | ||
} | ||
|
||
/** | ||
* Calculates Elo for quick display, matching the formula on loginserver | ||
*/ | ||
// see lib/ntbb-ladder.lib.php in the pokemon-showdown-client repo for the login server implementation | ||
// *intentionally* different from calculation in ladders-local, due to the high activity on the main server | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Wait, in hindsight I think the only difference is because of ladder decay, which isn't implemented here. Is the only difference here the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That's not the only difference; the numbers for scaling when elo < 1200 are also different.
ladders-remote:
ladders-remote uses 20/80 instead of 10/90, and multiplies by 30 instead of 40. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Interesting! We probably want to investigate the formulas more, later. But that's probably a job for a different PR. |
||
private calculateElo(previousUserElo: number, score: number, foeElo: number): number { | ||
// The K factor determines how much your Elo changes when you win or | ||
// lose games. Larger K means more change. | ||
// In the "original" Elo, K is constant, but it's common for K to | ||
// get smaller as your rating goes up | ||
let K = 50; | ||
|
||
// dynamic K-scaling (optional) | ||
if (previousUserElo < 1100) { | ||
if (score < 0.5) { | ||
K = 20 + (previousUserElo - 1000) * 30 / 100; | ||
} else if (score > 0.5) { | ||
K = 80 - (previousUserElo - 1000) * 30 / 100; | ||
} | ||
} else if (previousUserElo > 1300) { | ||
K = 40; | ||
} else if (previousUserElo > 1600) { | ||
K = 32; | ||
} | ||
|
||
// main Elo formula | ||
const E = 1 / (1 + Math.pow(10, (foeElo - previousUserElo) / 400)); | ||
|
||
const newElo = previousUserElo + K * (score - E); | ||
|
||
return Math.max(newElo, 1000); | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could this just be moved down to where
await ladderUpdatePromise
is?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This allows the loginserver's processing to happen concurrently with the server running and displaying the Elo changes. It's admittedly a small optimization, given that the Elo calc doesn't take much time; up to you if you want to change it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I see! I think this is fine.