PA Stats now fully works with 59549. I think. Also you need to update the alerts manager to make it fully work.
something drove it out of memory roughly 5 minutes after I went offline. The heap dump I just took is only 54mb in size though :S It's up again
I think the 8 players with pa stats game is a possible cause. Opening a few tabs of that page at the same time puts a very heavy load on the server. Might be related to what happened. Seems it doesn't like that many players in one game. Soooo many events. I guess I really should start to optimize a bit more :S
Can PA Stats capture the location of a notification to measure when the first build events happen on a new planet? It could be really interesting to be able to see when games go interplanetary.
It does already. I am just missing the time so far to use it. If you know javascript I can explain you the dataformat and you can write something. Though for "when are they interplanetary" you can just check the army composition for orbital stuff.
I am a web developer and I have looked around in the client code a bit. I just haven't been able to justify putting time in this while I was on a contract. I am thinking about becoming active in modding now though. I know we can look at composition, but it may be interesting to have a chart showing planet ownership over time. We could track build/destroy alerts to see who owns which planets and which ones are unclaimed or contested. If this would be worth doing, there should probably be some discussion on how that should be represented on the web page.
read this post from me for ideas I had: https://forums.uberent.com/threads/rel-pa-stats-59549.50690/page-9#post-841225 The coolest thing might be a base layout with a time slider that shows planets as well. The page currently works like this: 1. Maybe Init from a data-blob that looks like this: http://nanodesu.info/pastats/report/get/events?gameId=11675 2. If the game is live have 2 listeners for new events like this: Code: $(document).on("new-players", function(event, data) { for (var i = 0; i < data.value.length; i++) { var p = data.value[i]; armyModel.addPlayer(p.playerId, p.name, p.pColor, p.sColor); } }); Code: $(document).on("new-army-events", function(event, data) { for (var i = 0; i < data.value.length; i++) { var evt = data.value[i]; armyModel.addEvent(evt.playerId, evt.spec, evt.time, evt.watchType); } ... So if you could write something that uses this kind of interface I could add it to the page without much issues I think.
Released a new version that mostly fixes internal problems. If this works out okay I'll start working on matchmaking next. ... Finally
So known bugs for now: - If you watch a live game and let the page open for a few minutes after the game ended and press F5 there will be some errors in the list of players. - It does not respect the lock for live game data anymore. Both are rather easy to fix I think.
Just a thought. It would be useful to have someone explain a little how to read the data. Perhaps little things, that could help the player in understanding macro mistakes, and correct them.
Hmm, true. I think @brianpurkiss wanted to do a new video due to the matchmaking, maybe he could ...?
Other thing. You surely know better than me, but recently I had to put some info graphic on a site, and we investigated the options available. Damn you can do nice things using jQuery and other libraries. Specially crossing data enriches the charts and what you can get out of them. Like Google Analytics, as soon as you start crossing things, it's like a revelation. Anyway, Assuming that the data are published in real time (perhaps they are delayed?) I've also noticed that when a game is live, I could use PA Stats to look into my adversary status.
More analysis would definitely be cool. Did I already mention my wish for 48h days? The delay is 5 to 10 seconds. If you don't want people to see your stats while you play you can disable the display of live stats in the settings or right above "START ANNIHILATION"
Yeah some really impressive demo's on the d3 library https://github.com/mbostock/d3/wiki/Gallery which is the basis for the rickshaw library Colin uses in pa-stats this would be hella cool http://mbostock.github.io/d3/talk/20111018/azimuthal.html