I think he meant irony...which I lol'd @ btw.
Printable View
So is there actually going to be a finished, live stat system this time? This is at least like the third one "in development" I can remember hearing about, yet nothing ever came of the others. Is there a thread for this one or anything? Progress reports?
Yes there is! App works, just one more layer of security will be added.
Database is finished and currently receives statistics from the app.
The website is currently being produced at first I was looking for a designer, but eventually I end up doing it myself.
Which is good for my practice but probably a little less for your experience. (Doing my best, probably a future overhaul)
On release you'll be able to enjoy fun ranking, daily and weekly challenges, your overall statistics, leaderboards regarding most kills this day etc, Postgame carnage reports and hopefully a few basic achievements but don't hold me up on that last one.
When(?), I'm working as fast as possible, I want to get it out there this month.
Other thread with some more (old) info (http://www.halomods.com/ips/index.ph...-wip-halorank/)
K/D ratio is one thing you should definitely include if you haven't already.
Also, the stuff I mentioned in this post: http://www.modacity.net/forums/showt...l=1#post573960
I made the tracking of games within the database in such a way that I can filter per health type/shield settings and gametype.
So all of these stats are no more than a single SQL at this moment. This to avoid people boosting their stats through no shield games. (These are counted separate)
Based on the current system this can be done at this moment.
But let's layoff further discussing features here until I actually got a decent website to show.Quote:
Player stat page ideas:
CTF win percentage (would have to put requirements in place for games to qualify, such as x number of minutes played in the game, or x% of the game played)
Team slayer win percentage (same as above)
Slayer win percentage
Average rank in slayer / team slayer / CTF
Caps per game average in CTF games
Kills per game average in CTF / in team slayer / in whatever
Assists per game average in " "
Deaths per game average in " "
Also:
Caps per minute (or per hour or per 30 min, since caps/min would be a pretty tiny number)
Kills per minute
Assists per minute
Deaths per minute
You'll know this is the case when a topic emerges for this project. ;)
Just out of curiosity, how are you planning to make this viable in the long-run for the entire community? For example, will the app be compatible with other server-apps from the start? Will server-hosts be able to host their own stats website instead of relying on yours which could potentially go down at some point?
Hopefully we won't be locked into using only your website for stats. If you'd like to keep a global database, perhaps you could make the app send stats to the global database (you) as well as a server-operator-defined stats server that they run themselves.
The app will not support other apps from the start. Since I foresee problems with certain "fun" functions that are offered by other apps. A "deathless player"" fun function or a "speed increase" fun function would basically ruin the credibility of the statistics quite fast. Unless these fun modification are tracked as well.
So a "no" for now, since HaloRank is in start up face, a potential yes for the future.
All stats will be HaloRank exclusive, hold your horses before going in frenzy.
I am considering building an web API for other web developers to use the statistics gathered. This will probably be done after the majority of the website is up and running. (Sharing is caring?)
As for the website potentially going down.
I have quite some bandwidth to use with options to upgrade if necessary, so other than the server
going *BOOM* or me calling quits I doubt the community will be affected.
As for other web developers simultaneously building a stats website with the same raw data provided by the current app.
I don't see the benefit of this for HaloRank, most definitely not in start up face.
Later on it might be fun in order to boost the overall quality of the service. However the data will still be provided through an API.
In general I want to avoid anything which might decrease traffic from the website. Which I believe is normal for anyone in charge of a website, but also because it would go against one of the main ideas behind HaloRank. Having the fun playing and competitive community in one place.
Does this mean the data is too exclusive from start up? Yes, it is. However with the same reason for any website starting up.
With the API a bit later it will overtime become more open.
Does it mean no one else can do it? Create and app today and your good to go tomorrow, I still don't understand why after all this time something similar/better than HaloRank is not already out there.
I had hopes on three different type of stats apps before I decided to go ahead and launch a stats project of my own.
Does it mean I'm a dictator in my own virtual world?
No not at all, a lot is possible in my eyes through debate. Even now I'm working together with other programmers to make HaloRank happen. (Details will be provided upon release.)
Some of you reading this might have received technical questions or requests for opinions in the past.
What's in store for HaloRank in the future?
At some point, probably with the release of the API. I hope to simultaneously create a more open web dev section within HaloRank. This would be for anyone within the community that would like to help out, thinks they can do a better job/improve the website or just has a great idea a new feature for the website. (Credit list in place.)
I hope this answers most of your questions. :eng101:
Now I'm back to coding so I can hopefully provide a demo for CE3.
Isn't this just a remake of halostats?
I'm not familiar with HaloStats, the current site doesn't do much. Can you provide some details on what it is/was?