Moderator
Sorry, there is only one "hidden" parameter and it doesn't provide any extra data. It just displays the same data in a xml format.
I can't comment on keeping outdated records in our database. If we did have those, it wouldn't be a good idea to allow everyone to access them. It would generate way too much load on the already overloaded server.
cmon Antti, I fully expect a new bot command within the near future
example:
!track norfair e6 2008-12-11
TBot: NorfaiR was #36 on Bumpy Road with a time of 00:34:66 on December 11th 2008
Glas, you were right, the nightly check was screwing up! I wouldn't have even noticed had you not said anything. Thanks for the heads up!
It's working fine now, and has appropriate limitations that limit the hit on the server to levels thatimagine) are no larger than they'd normally expect. I really don't want this thing to create even a small spike on their server load, and I'll continue to tweak/limit it as needed, or even keep the daily checks limited to those who personally request them. But for now, I think it's able to run as described without causing problems, and I have a limit of daily 50 automatic hits to the server as a cap spread out over 16 hours, just in case.
Yes. It will (now, thanks) keep a log of your improvements so you can go back and get a good picture of your track performance over time. I consider this the best of both worlds tooOriginally Posted by GlasWolf
I'm working on creating per-track charts, and I just took a look at the charts that Stulley linked, and I like them.
Stulley, I'm glad you like it! I'm honored, since I've found your tool to be so insanely useful! Mine wouldn't exist had it not been for yours! I'm storing snapshots in mysql since I was sad to see all my old records disappearing. I'm concerned about the XML request too. I've been doing everything possible to cache data, even deadlast's records, so the impact is as transparent as possible. (And yes, the forums are slower, so neither redlynx nor I are taking too much of a hit here.) But it's definitely geared towards on-demand snapshots of your current status for later comparison.
http://highcharts.com/demo/ holy smokes that looks cool. I may just use that! I'll also happily work on some ideas if you have any. I have no qualms about sharing the source for it, aside from the fact that it's grown organically from a pretty utilitarian start (so I know I could have written it much better). One thing I'm curious is how you calculated records from deadlast!
I have this in place now:
90/deadlast's rank = points per track
user points = 100-(rank*points per track)
This works really well to estimate how much you've gained, but when you add the numbers up, they're coming out larger than what you're actually getting. I could just be rounding them too much.
Beyond that, any ideas you have for it are most welcome, and I'll glady play with any ideas to make it better. There's a growing list! Thanks all for the positive/constructive feedback, and long live T2SE
Moderator
If we did have the data and I had simulated that query on the database, the software would have had to read over 500 megabytes of data from the hard disk and query would have taken over ten seconds. And if we did have the data, you would have been #194.Originally Posted by NorfaiR
So no, don't expect that command to be implemented.
Haha, excellent
Well, the good news is that I don't have the most popular Xbox Live Arcade game on the market, so my server is ready to start taking requests
Updates:
Added a view for per-track history. It's going to improve a lot, but at least this way you can see your improvements by track. No chart yet, but implementing one will be fun.
Fixed the daily check, optimized it to hit the server as rarely as possible, and to spread the check out to 3 times per day, with a current maximum of 30 daily XML requests, each at least 10 seconds apart. Each user's scores are checked once per day.
Fixed a bug where the snapshots were breaking into two incomplete snapshots due to the timestamp changing during the request.
Shrunk the columns a little by abbreviating the track names (T1, D19, etc).
Also saw to it that the latest snapshot will show up in your list as soon as you make it, particularly on your first load, when it was most confusing.
Other little things not worth noting.
http://www.bagill.com/trials/
Better and better. The only feature that's missing now is the display of rank and points over time. This will be the same process as the per-track stuff, but with an even simpler display of date, rank and points colums. Unlike the per-track this would have an entry almost every day. Easy enough to introduce in the UI anyway; just one more history icon alongside the rank/points row.
Talking of the icon, I made a transparent version so it doesn't clash with the background - it's here. You can barely see it against the dark green, but -->
Also, if you're looking for completely over the top features, I was thinking about a graph of your rank over time marked with the points at which you recorded one or more new records. The idea came from the youtube views graphs, and the format would be identical. I think it would be difficult to implement though.
Charts are (somewhat) implemented. Let me know what you think!
Seconds are now implemented, but not shown in standard format, mm:ss:xx. Also, Thanks for the new inspect icon, Glas, It's in place.
And thanks Stulley for the javascript chart choice! I like this one a lot, and implementing it has been interesting.
I may make some stylistic changes as part of an overall revision, but right now the appearance seems to be pretty good for our purposes.
I've put the old grid of data below so you can read it plainly if you find the the chart confusing, and I'll be implementing this style for the overall history as well. Some of the charts are pretty underwhelming, and some are crazy. My YSNP history is pretty cool, for instance.
I have it set up so it's only reading from your saved history, so they may be up to a day behind your latest progress. If this is an issue for you, save a snapshot, then look at your chart for your most current scores. I have it this way so we don't have to hit redlynx's servers for per-track stuff.
I still have a lot of possible changes in mind, so if anyone can suggest anything, let me know. I've been using this thing daily, and I hope others will use it as well.
And, dang it Glas. I was going to point out that I'd surpassed you! #170 and #169, not a bad spread!
It's more or less perfect now, I was actually going to suggest keeping the grid data alongside the chart. Fantastic job. I was thinking the other day about how to represent a track like YSNP where faults and time both play a part, but couldn't really come up with anything. Maybe using a third axis for faults? Good luck implementing that though.
I'm actually going through the tracks in reverse rank order, which is far from the most efficient way to improve my ranking. It does keep things fresh though, rather than just playing Diablo over and over...
Some notes to RedLynx:
1) When you get to implementing stats for Trials 3/Trials PC X-treeeme/Trials Kitchen Sink Edition: copy this.
2) True fan.
Oh yeah, the rank/points graph is really cool. I'd like to see the corresponding dates but I'm guessing you left it off because it looks cluttered?
