Stan`

Found the guilty line https://github.com/StanleySweet/replay-pallas-api/commit/e085022fc93e7a6578a82d18c7a3df21970a2d5e Explains the weird link between deviation and rating. I hope my friend's @Stockfish's mouse is okay, they are clicking at least twice as much as any one @borg- has a terrible rating because he lost the three matches on the site (His rating is 900? the '?' being for provisional)

I'm not sure but I think it's normal due to the very low amount of matches. At the beginning you have a deviation of 350 which probably boosts your rating at each each match, now your deviation is closer to 45. But at least the dates are in order now Another thing is that there aren't many matches. The code responsible for this is there https://github.com/StanleySweet/replay-pallas-api/blob/main/src/instant-glicko-2/Glicko2Manager.ts#L64

Only the first one remains. The replay matchid is used to avoid duplicate replays. Ha I messed up the sorting should be fixed now.

Pushed some updates, you now have the glicko rating on the player profile. Also added the game rating info I have to that graph. I didn't exclude 1v1 from local ratings as for now those are two different things. People with the contributor badge can upload replays. I haven't set up the scrapper yet, not sure if there I should create a specific thread for it and whether it's a good idea.

IIRC @vladislavbelov worked on it some time ago.

Found this little thing that might solve the issue (it's also what lichess uses), but I need to convert the rust code to TS https://github.com/gpluscb/instant-glicko-2/tree/f34fd27aba57c21b0554a6ccc2b6a26559a0f5e7

Regarding determining if a player has lost or not, would the percentage Building Lost + Units lost work? Lowest Percentage wins? (This would be done only for 1v1 and if there is no state set to won)

That could work I suppose. I can also add a big button for admins to recompute it. I'll try to implement it. Should we unlike lichess start at 1200 ?

Another issue we have is that unlike on lichess, one can upload replays in any order, so I suppose I should recompute the whole thing each time someone adds a new replay for all players (since a changing rating for someone would change everybody that ever played against them)

Okay. Do we count replays with no winners as draws ? https://github.com/mmai/glicko2js They say there that You should not update the ranking after each match. The typical use of glicko is to calculate the ratings after each tournament (ie collection of matches in a period of time). A player rating will evolve after a tournament has finished, but not during the tournament. So I'm not sure it would work well in our case

Separate ratings for both? Or one ? Should it keep the 1v1 then? Sure I'll wait for the input

Sounds fine (we can still compare it with the in-game rating) I don't know the maths though, so I'll need some help with that. Also I need to know which replays would be concerned or how many elos one would have. There is rated/non rated Teams locked NvN AI's Some matches don't have informations about who won and should probably be excluded. If I can gather a good enough specification, I can make the code.

Indeed, thanks for the report(s)! I do have the game's elo from the names, would you like to see a graph about that ? Plotted by date something like Game Rating Evolution?

Published some updates to the dark mode, a few fixes and a new graph.

For now yeah. I may reconsider in the future but I don't like the idea of having the api left unrestricted

live version at https://replay-pallas.wildfiregames.ovh

Did you use \ in your changes ?

This video explains it well https://youtu.be/C8YtdC8mxTU?t=976

The top of the barrel is flat, but the rest is smooth shaded. I added some extra barrels, the leftmost without any smooth shading.

Of course we have smooth shading Oo. Else barrels would look much worse. Units too.

I suppose @wowgetoffyourcellphone is in charge now

Okay few things from looking at the DAE in that zip. You need two UVs in order to be able to use AO. The fact it doesn't crash for you makes me think that either you got an error message, or that you might not have set the material quality to 10. Second is wasted UV space, you want to have as little black spots as possible, you can probably rearange things so that those curved pieces take less space And yeah you can boost the margin a bit.

Can you show me the generated ao and the second uv map layout. Not sure i'll be able to access blender. Also if you export the roughness map you need to invert colors. That's what I meant by 1-roughness.

The problem is the existing voices wouldn't be enough to train a model. So until legislation is in vigor, I'd be really careful in using AI in anything else than mods.

Yeah you can actually do that just with git log --format. But the problem is here is that not everything is relevant, you don't want to see 200 autobuild commits Nor fixes for art typos. Just the art commit itself. They can sometimes be grouped. That's why we (used to) do it by hand.