SRL Archive - SRL Stats

With support for graphs! :D

They seem to have some problem with threading. (One title showing up in another if loaded at the same time… I blame matplotlib) - Fixed

Ratinator, this month:


MSI, this month:


Monkeybeer, this month:


Monkeybeer, this month to MSI:


Total:


Note that if you refresh it every 10 minutes, you'll actually see the bar of this current day grow. :D

Yeeeeey!

It looks awesome, Wizzup :)

EDIT: Actually, it doesn't look awesome, it needs better graphics, but it IS awesome!

lolz I made the post for being an MLG legit leacher. But seriously, I'm gonna start learning to script now that finals are over and I'm starting to feel pretty selfish for being a leacher. :duh:: Anyways, looks cool Wizzup?.

Added some more features.

Syntax: (IN THIS ORDER)

• If you want to specify a month: add /month/<month#> (Leaving this empty will default to current month)
• If you want to specify a year: add /year/<yearhere> (Leaving this empty will default to current year)
• If you want to specify a script: add /script/<scriptid> (Leaving this empty uses all scripts)
• If you want to specify a user: add /user/<userid> (Leaving this empty uses all users)
• If you want to specify a type: add /type/<typehere> (Leaving this empty defaults to 'amount')
Valid types: (amount, minutes)

http://stats.villavu.com/graph/commits/month/1/year/2011/script/21/user/56/type/minutes

Suggestions for making the graphs ``prettier'' are welcome.

Looks awesome!

Question:

Are there any plans to have it like the old stats was where you can re-activate a player if they deactivate for any reason.. such as getting stuck in a random?

From: gratz
Looks awesome!

Question:

Are there any plans to have it like the old stats was where you can re-activate a player if they deactivate for any reason.. such as getting stuck in a random?

I had this idea where you could pass a specific player per commit, so you could keep track of what player commit what; but this isn't implemented yet. It could probably be a base for ``resetting'' players. But I think that should be a separate system for now. I didn't know the old stats could do this?

From: Wizzup?
I had this idea where you could pass a specific player per commit, so you could keep track of what player commit what; but this isn't implemented yet. It could probably be a base for ``resetting'' players. But I think that should be a separate system for now. I didn't know the old stats could do this?

In the old stats.. what was the site? free hostia? I believe

anyway, lets say I was running this script with this proggy:

http://villavu.com/forum/showthread.php?p=688267#post688267

At the time reflection was just getting fixed and most of the randoms didn't work very well.. so the script would log out and disable the character

In the freehostia site there were check boxes next to every account, when it would log off from a random I'd login it on my other computer, do the random, put him/her back at the bank and click the check box and press "apply"

If the box had a check in it, it meant the character was running.. if not it means it was disabled for whatever reason

I'd leave em on over night and come back do all the random events and put them all back up lol



edit:

http://villavu.com/forum/showthread.php?t=47111

this is also another script which the check box thing worked very well on

Would be nice to have more types: 'hours', 'days', 'months', 'years' :)

From: Wizzup?
I had this idea where you could pass a specific player per commit, so you could keep track of what player commit what; but this isn't implemented yet. It could probably be a base for ``resetting'' players. But I think that should be a separate system for now. I didn't know the old stats could do this?

MSI has a player remote that does exactly this. It could probably be edited to work with SRL's player type and added to SRL if you wanted to keep it as a separate system. It's also accessed through Simba rather than online.

Oh and by the way, the graphs look awesome. :)

Could we get graphs of scripts vs scripts?

eg

MSI Essence Miner vs Wizzup Essence Miner

(Essence variable from MSI & W.E.M.)

Or just a graph with the top scripts per commit?

~RM

http://www.youtube.com/watch?v=egrwaLFsn0Q

From: cycrosism
http://www.youtube.com/watch?v=egrwaLFsn0Q

How is that relevant to the topic?

From: Zyt3x
How is that relevant to the topic?

Its proberly not, its cool tho

I think it would be nice if you made it possible to edit the script page of the scripts you own, so that the user that owns MSI can make it look nicer than it is atm.

Also please include link to the person who made the script in the script site. So http://stats.villavu.com/script/21 would have a link to http://stats.villavu.com/user/80 and so on… :)

From: Wizzup?
Added some more features.

Syntax: (IN THIS ORDER)

• If you want to specify a month: add /month/<month#> (Leaving this empty will default to current month)
• If you want to specify a year: add /year/<yearhere> (Leaving this empty will default to current year)
• If you want to specify a script: add /script/<scriptid> (Leaving this empty uses all scripts)
• If you want to specify a user: add /user/<userid> (Leaving this empty uses all users)
• If you want to specify a type: add /type/<typehere> (Leaving this empty defaults to 'amount')
Valid types: (amount, minutes)

http://stats.villavu.com/graph/commits/month/1/year/2011/script/21/user/56/type/minutes

Suggestions for making the graphs ``prettier'' are welcome.

Why not use POST variables?

From: Nava2
Why not use POST variables?

Yeah, using POST variables for a normal GET requests sounds awesomely cool. Especially if you're doing REST.

From: Wizzup?
Yeah, using POST variables for a normal GET requests sounds awesomely cool. Especially if you're doing REST.

After reading up on what REST is, I guess what I meant was why not use a means of passing through URLs, I mean this works, but its kind of ugly in comparison. Not to mention limiting via having to pass in a specific order.

(The REST article was an interesting read btw)

Again, I am merely putting in suggestions, I haven't looked how you implemented this. As such, it may be easier/better this way code side.

P.S. I like the idea of being able to plot script vs. script. :) Should probably be done through a regular graph though rather than bar graphs. This is simple with matplotlib though .

I'm just stating that POST variables don't make sense here. You don't ``post'' to a graph / image request. I could use GET variables like ?year=2010&month=1, but I really prefer this. Plus, it's not like people will have to fill in the link manually anyway.