Subscriber alex Posted February 2, 2015 Subscriber Share Posted February 2, 2015 Hello, I may have missed something, but i cant find a way to sort players by their KD. Is it actually possible ? If not, could this be implemented please ? What about within the !usersearch command in a new column ? Could be something like: !usersearch kd or even a new command like: !killrating n n is the page you want to see. Thanks. Quote Link to comment Share on other sites More sharing options...
Zelly Posted February 3, 2015 Share Posted February 3, 2015 /killratingFor online players, I don't really know the use of seeing everyone's killrating. http://i.gyazo.com/b934afa8c8858b5f04e37f30f7292071.png Quote Link to comment Share on other sites More sharing options...
Subscriber alex Posted February 3, 2015 Author Subscriber Share Posted February 3, 2015 How to achieve this for offline players ? Against a lua thing that is reserved for players who know it ? Quote Link to comment Share on other sites More sharing options...
Zelly Posted February 3, 2015 Share Posted February 3, 2015 I don't know of a way, unless you manually stored them with lua. Quote Link to comment Share on other sites More sharing options...
Subscriber alex Posted February 4, 2015 Author Subscriber Share Posted February 4, 2015 /killrating command doesnt work for me: "unknown cmd killrating" Quote Link to comment Share on other sites More sharing options...
Zelly Posted February 4, 2015 Share Posted February 4, 2015 g_killRatingDescription:When not set to 0, silEnT will track a player's killing ability using an ELO type statistic similar to chess. Each kill will increase a player's kill rating based on how hard the kill was. Killing unskilled players will result in very few points whereas an unskilled player killing a skilled player will result in more points.See also g_shuffle_rating.Type: bitmaskParameters:1 Use kill rating. A dummy flag since any non-zero value for g_killRating will enable it.2 Make kill rating visible. Players can use /killrating and at the end of each map a message will display the top killers for the map and overall.4 Log files will include the GUIDs of the players involved in kills. This makes kill tracking a lot easier.8 Disable kill rating from the score board. This can prevent players from playing for higher kill rating alone. This does not prevent the "killrating" client command enabled with flag 2 from working.Default: 3You need flag 2 of this cvar I think. There is also a /playerrating command (flag 2) of this cvar: g_playerRatingDescription:When not set to non zero positive value, silEnT will track a player's ability to win against good teams using an ELO type statistic similar to chess. Each win will increase a player's rating based on how hard the opposing team was. Skilled teams defeating less skilled teams will result in very few points whereas an relatively low- rated team defeating a good team will result in more points. Player rating also takes into account the number of players on each team (less points when a very large defeats a small one) and which side tends to win more often on the current map (e.g. Allies tend to win tc_base).See also g_shuffle_rating.Type: bitmaskParameters:1 Use player rating. A dummy flag since any non-zero value for g_playerRating will enable it.2 Make player rating visible. Players can use /playerrating and at the end of each map a message will display the top player.4 Put player rating on the scoreboard instead of the XP.8 Print out extra info at the end of a round that can be used to further refine the playerrating model.16 The same as flag 8 except a lot more info is output.Default: 3 alex 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.