Jump to content

Mentula

Community Members
  • Posts

    38
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Mentula

  1. Sure @Sevda. First of all, I can't see from your pictures the number of matches you've played with the players in your list, but I can imagine that the number of matches is small for those players that you believe being far from your expectations. When the number of matches is small, statistics are unreliable; you need many games to get significant data values. Notice that the mod (v0.25.6, the last version at the moment I am writing) allows you to filter out players whose number of games is small (from the Options > Player Filters menu). That being said, I'll do my best to explain the algorithm hereby; you can find more info at the repository page and, if you want to look at the part of the code that handles the rating computation, you can look at this file. Sorry for the long answer, I hope it's clear enough.
  2. @sarcoma let us consider a specific example: "Enemy units killed (value)" vs "Enemy units killed (number)". If you set a weight of 1 to "Enemy units killed (value)", the contribution of this parameter to the rating corresponds to the total value of enemy unit killed, that is, the cost to produce them. For example, with a weight of 1, a player gets 50 points for killing an enemy citizen woman, 100 for a base infantry unit, 150 for a base cavalry unit and so on... On the other hand, if you set a weight of 1 to "Enemy units killed (number)", the system will assign one point for each enemy unit killed, disregarding the type of unit and the cost to produce it. For example, with a weight of 1, a player gets 1 point for killing and enemy citizen woman, 1 for a base infantry unit, 1 for a base cavalry unit... To continue with this example, if you set a weight of 1 to both "Enemy units killed (value)" and "Enemy units killed (number), you will get 51 points for killing and enemy citizen woman, 101 for a base infantry unit, 151 for a base cavalry etc... So probably you might want to consider one of the two parameters only and set the other to 0, but this up to your rating design. The mod's default weight for "Enemy units killed (value)" is 0.1 because in 0 A.D. each enemy unit killed increases a player's score by 10% of the unit's value. For the same reason, the default weight for "Enemy units killed (number)" is 0 because in 0 A.D. a player's score is not affected by the number of enemy units killed (but only by their value). The LocalRatings default weights are the ones that 0 A.D. uses to calculate the total score of a player.
  3. Short answer: I would personally balance a TG by balancing the total ratings of the two teams. However, let me be prudent in giving a definitive answer. One big fact to take into account is that the rating heavily depends the weights you choose. Different weights can give rise to very different ratings. The weights are supposed to change the "meaning" you give to the rating. But once you have decided upon the weights to choose, it's true what you say: the more games you played, the more reliable ratings are. Yes, the amount of spent resources could be a weight to add, thanks for suggesting. Regarding the ratio, ratios can't be used as weights for the following reason: the rating of a player is determined by comparing the player's parameters with the average game parameters, so at some point a division occurs in the calculation. Ratios can sometimes be close to 0 (or to infinity), and we all (well.. many of us) know what happens if a number close to 0 (or to infinity) is at the denominator. Actually, during the early stage of the mod development I have considered including ratios (like k/d ratio, resources sold/bought, tributes sent/received, ...) and results were odd, to say the least. The number 10 is the correct one. The "Exploration Score" (the same one that you can see in the Summary at the end of a game), is obtained by multiplying the percentage of explored map by 10.
  4. Hi everyone, with this new update (v0.25.6) of the LocalRatings mod, one can filter out matches with a given number of players, number of teams, or matches with uneven team composition. For example, one can exclude all 1v1 matches from the rating computation; or, conversely, one can consider 1v1 matches only! See image below. Thanks to sanafur who suggested the update! Download: as usual, you can download the new release (v0.25.6) of the mod from the zip file attached to this post or from the zip file attached to the first post of this thread or from the official page. LocalRatings-v0.25.6.zip
  5. Hello everyone, I'm sharing with you this mod that I made long ago, hoping it is useful to somebody. The mod is named CircularCamera (official page on GitLab) and it provides nine new cameras, each pointing at a fixed position on the map. Each camera can be accessed with a hotkey. See image below. Features Nine new pre-set cameras are available: one points at the center of the map and eight point at the eight corners of the map. Jumping to any of these cameras can be done via a hotkey. Hotkeys can be edited from the Settings > Hotkeys menu. Distance of cameras from map center: the distance can be increased or decreased with CapsLock+Plus and CapsLock+Minus. The default distance from the map center can be restored with CapsLock+R. The default distance from the center, as well as the increasing/decreasing step can be adjusted from the user.cfg configuration file. Hotkeys: search for circularcamera in the Settings > Hotkeys menu: there you can edit all the relevant hotkeys. Mod installation Contribute The public repository is at this page. Everybody is very welcome to contribute, suggest, fork or simply give feedback. Have fun! CircularCamera.pyromod CircularCamera.zip
  6. Dear 0 A.D. friends, I am happy to announce a new release of the LocalRatings mod! Most notably, the new release includes the following new features. The rating of a player and the number of games played appears next to the player's name in the Match Setup page. This will hopefully make balancing games an easier task. See image below. A new Player Filter has been added to the mod: now it is possible to filter out players depending on their rating or the number of games they played. Download and install: you can download the new release (v0.25.5) of the mod from the zip file attached to this post or from the zip file attached to the first post of this thread or from the official page. I wish to thank all the forum users who gave feedback and suggestions. A special thanks goes to sanafur, who suggested the above (and other possibly future) features. Have fun! LocalRatings-v0.25.5.zip
  7. @Sevda @thephilosopher many thanks for reporting. Bug is now fixed; the updated version v-0.25.3 of the mod is now attached to the initial post of this thread. If you have the older version v-0.25.2 installed no problem: just open the mod options menu once and everything will work.
  8. I personally disagree with this interpretation of the rating. First of all, it's true that someone who mostly plays against weaker players gets a higher rating, no doubt. However, I disagree on the interpretation of the rating as a win rate (in any context: 1v1s, TGs, ...). The rating assigned by the LocalRatings mod (the default one, as well as any user-customized rating using different weights) is very distant from representing a win rate. A win rate of 20% means that the player wins 1 out of 5 games, which is not good; on the other hand, a rating (as in the LocalRatings mod) of 20% means that the player's graph in the Summary chart is 20% better than the average graph, which in other words means that the player performs very well (and therefore presumably has a high win rate). In my experience with this mod, a player with a rating of 20% is a strong player; I wouldn't say the same of a player with a 20% win rate. However, let me clarify one thing again: this mod is based on statistics. In statistics any of us can imagine a "limit case" (it could be, for example, a player who only plays with much weaker players). On the bright side... this mod is based on statistics! This means that, generally, a player who plays with different types of players will experience more reliability in the ratings data. This comment actually gives me the possibility of clarifying one thing. Assigning a rating to a player can be something very arbitrary and will never make all of us agree. So, I tend to see the rating of a player as the player's performance over the average, or, if you prefer, their contribution to the game. But this is just my interpretation of it. The lobby's rating evaluation is a system only takes into account the win rate, whereas the LocalRatings mod takes into account scores. In this sense, they don't conflict, they just represent two different things.
  9. Hum that is a bit strange, it could be a bug. It's actually the first time I see it and at the moment it's hard to find the cause. @Sevda I'll send you a private message to investigate (maybe tomorrow, now it's late in my timezone). Thanks for reporting!
  10. The main problem with restricting the sample of replays to a limited amount is statistics. The more replays you have, the more accurate the rating of a player is, therefore it is disadvisable to rely on data extracted from a small (though recent) sample.
  11. It shouldn't be hard to implement such a feature, I can look into that. Perhaps it is also something that developers can consider to include by default in the game. @Sevda of course, you are welcome to use them (or part of them) into your StarGUI!
  12. Hello 0 A.D. friends! Many times I find myself in the situation of having many units under production from several buildings and I want to clear ALL the production queues simultaneously. This can happen for many reasons: maybe I want to get back some resources that had been allocated to units production; or maybe I suddenly need to change type of units being produced if I see that the game steers from the direction I expect. As far as I know (correct me if I'm wrong), there is no explicit hotkey that allows to clear all production queues simultaneously. It is also very annoying to clear production queues by clicking on icons one by one, especially when you have many buildings producing or many units being produced. So, I made a mod for this. The ResetQueue mod (official repository at this page) allows to bind a hotkey for clearing production queues of selected buildings. The default hotkey provided from this mod is Shift+Esc. This can be changed from the Settings > Hotkeys menu. I find this feature very useful and I often use it in game. I hope this feature will be present in a future version of the game. What do you think? Installation Contribute The public repository is at this page. Everybody is very welcome to contribute, suggest, fork or simply give feedback. Have fun! ResetQueue.pyromod ResetQueue.zip
  13. Hello everyone! I hereby present a 0 A.D. mod aimed at evaluating the rating of players. Official mod page on GitLab here. Introduction Before diving into the description, let me introduce the problem this mod aims to solve. In 0 A.D., the ELO system is used to rank players in the lobby. This is good; but is it representative of the players' skills? As you know, the rating system in 0 A.D. only takes into account 1v1 rated games. Team games do not contribute to the ELO score of a player, as well as 1v1 unrated games. Also, the scoring system only takes into account the outcome of a game (victory/defeat) and not the "performance" during the game. Can we do better? This mod uses statistics. It extracts data from all the replays of games you (the mod user) have played. So, if you have played 20 games (1v1s, team games, other..) with a player in the lobby whose name is (for example) strangeJokes, the mod will assign a rating to strangeJokes based on the 20 games you've played with them. The rating system The functioning of the rating system is described in detail here, but in short what it does is: it considers the average performance of the player during the entire game (and not only at game's end). the rating assigned to a player is a percentage: for example, a player with a rating of 5.00 performs a 5% better than other players on average, while a player with a rating of -5.00 performs a 5% worse than other players on average. you can customize the rating system by giving more importance to military, economy, exploration or other factors to the aim of calculating ratings. Keep in mind that this mod is based on statistics; data are taken from your (the mod user) replays. Statistics might not be fully representative of reality; therefore, a player's rating could be inaccurate, especially if you have played few games with that player. The more you play with a player, the more accurate the rating of that player is. Mod installation Explanatory pictures Contribute The public repository is at this page. Everybody is very welcome to contribute, suggest, fork or simply give feedback. Have fun! LocalRatings.pyromod LocalRatings.zip
×
×
  • Create New...