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
Rankings Issues #154
Comments
weird, i'll take a look
sourcemod's rounding ughhh, i'll fix it though
49.993 = 100% = 49.993 I thought you knew we use a weighting system :/ |
anyways ok this new ranking method is a really big mess, i'll rewrite it all |
Is anybody currently using the ranking system, if so, what are the outlying issues with itself and chat? Like, will it sort of work? |
i think you won't gain points and rank calculation will be broken. chat itself is fine afaik |
But the link between shavit-chat <-> shavit-ranking is that they both rely on each other correct? |
shavit-chat relies on shavit-rankings, but not vice versa |
Here's a working version of shavit-rankings made by zipcore: https://pastebin.com/raw/iuz6bgky He tried to fix the plugin just so it works, but the rankings are killing the mysql database so it's unusable, but maybe this can help you in the future. |
I'll look into it soon and try optimizing the plugin, thanks. |
oh and this in shavit-core:
replace with:
and this
with this:
It's because the points are reseting on join and mapchange. |
I think this is the next big think you should start working on because everyone is waiting for a fully functional rankings plugin that delivers all the necessary features (and doesn't suck). I don't think you have to rewrite your plugin since it's very good and I gave you a (almost) fully working version of it (credit to Zipcore). The only think you have to do is to optimise it, because for some reason it's killing the database within 10 seconds. xD |
I'll rewrite it because I don't like the way I did things before, no worries! Rankings are basically the last thing I need to do before the timer is out of beta :). |
Closing as I made my own issue with a new design: #465 |
The text was updated successfully, but these errors were encountered: