Leaderboard
Popular Content
Showing content with the highest reputation on 2021-12-04 in all areas
-
4 points
-
3 points
-
3 points
-
2 points
-
2 points
-
2 points
-
The cape is what we need. The current cape models in the game are unsuitable unfortunately.1 point
-
There is also distortion on the neck at the torque.1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
It could be too. I interpreted your message as saying this is a ceremonial item. But as a prop it is also plausible. The idea of beautiful clothes?1 point
-
We should start a new thread about improved rating system. However, an idea is that rating gain could be a function of the player's score. For example, rating gain = A * ln(B * score + 1) Where A and B are some constants to be determined as appropriate. This model has the advantage of no ridiculous rating gains from just one game, due to the property of logarithm (f''(x)<0). The +1 is necessary so that a player with 0 score does not get a negative infinity rating. Using this model, taking A=1 and B=1, a 9000 score player would gain 9.1 points, a 30000 score player would gain 10.3 points; a 800 score player would gain 6.9 points. You may argue that this is unfair as the 30000 score player did much better than the 800 score player. So let's consider some function that takes account of the player's individual performance and the overall performance of their team: f(player score, team average) We can deduct points if a player plays too badly with respect to their team, and reward the overperforming players. So we can have a comparing term player score / team average or, player score - team average And then we operate on the result of this comparison to give a rating change. One such model is rating gain = A * exp(B * (player score / average score of their team)) - C C is a threshold constant, which determines whether someone gains or loses points after comparing with their teammates. The advantage of this model is that a player in the losing team who played very well can still gain a lot of rating in spite of their noob teammates. Suppose a 1800 player is paired up with 3 cosmic noobs, the 1800 player can still gain quite a lot of points if he scores 20000 and the noobs score 5000 each. On the other hand, a noob player in the winning team may still lose points.1 point
-
Some people do, then you upload the patches to Phabricator. Re binary files support could use this https://git-lfs.github.com/ Well I can't do any of this if we don't agree migrating to git is necessary.1 point
-
Pro Git Industry standard Co-authoring of commits Submodules? With different access Supported by maintained platforms (Gitlab, Gitea, Github, Bitbucket, Azure Devops) Already used by most (if not all) mods Assuming you want to extract diffs from branches once we have to drop Phabricator because it becomes a security flaw (or doesn't work anymore, currently we need to use hacks on the macOS and Linux VMs for certificates to work. Needs for a VCS for me: Require the least sysadmin possible Be common enough to lower the entry barrier by having resources to use1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
1 point
-
I was a little bored, so... A concept for the Norse' wonder, Temple at Uppsala: (It still requires; a proper coloring. The tree, chain, pool and runestones. And probably a simplification on its polygons). I designed it both based on the few information available online https://en.wikipedia.org/wiki/Temple_at_Uppsala (and particularly the artistic depiction https://upload.wikimedia.org/wikipedia/commons/d/df/Olaus_Magnus_-_On_the_Glorious_Temple_Devoted_to_the_Nordic_Gods.jpg, although it lacked of proportion in some parts of the structure). And clearly inspired too by the actually known different models of "Stavkirker" (stave churches). I hope it can be helpful. 1735522378_UppsalaTemple.dae1 point
-
0 points
-
Yes, but soldiers dont hit buildings in this situation, they try to capture. This is often more successful.0 points