Greasy Fork

A couple of months ago, I wrote a script for a multiplayer web game that is far ahead all the existing ones in both quality and content, however I have great competition with the other existing scripts. I managed to get to second place on the entire site for this category, (unable to beat #1 yet because of google search only showing the top #1) however recently I started to fall to third place. I was being beat by a script with less than half of my daily installs, pushing my to #3, and crushing my ability to get installs. I think this is a bug, as it started to happen only recently. I need a solution fast, I am losing potential installers.
Link to my script: https://greasyfork.org/en/scripts/452934
Link to all other scripts: https://greasyfork.org/en/scripts/by-site/venge.io

@hacker09 @JasonBarnabe please help. It is happening again

I don't think this is a problem, if ratings and total installs are also part of the equation it would make sense that although you had more daily installs you are not on the top/2 position.

If you have enabled the daily total installs filter then yeah that's probably and issue.

Jason is the only one who can fix this.

@JasonBarnabe, someone forgot to add sorting by "Relevance" in by site search, right, Jason? :)

@hacker09 This only started happening recently though. I was always second, even though I had only 3 ratings. Now this is happening, and I can't grow my script

I hope jason comes on here quick

Welp. It happened. My script got pushed down to #3. That was quite unfair. I'm now really in 3rd place, my daily installs are now lower than them. Please look into this.
@JasonBarnabe

As far as I can tell:

1. The install counts are stored correctly.
2. The install counts are displayed correctly.
3. The search results were sorted based on an outdated number of installs.

I believe I've fixed #3. https://greasyfork.org/en/scripts/by-site/venge.io now shows the scripts in an order consistent with the displayed number of installs. I'm not sure if it recently started happening, but it could have been based on the timing of the last script update.

Thank you Jason! It works now. It started happening recently, and now it isn't. Everything is back into place now. Also about outdated - I'm not sure there could have possible been any outdated install counts - I checked the install counts on same days on all scripts and there still could've been no way it was possible. Thanks again!