Difference between revisions of "RumbleStats"

From Robowiki
Jump to navigation Jump to search
(clean up, add back Twin Duel example)
m (regenerate with ANPP enabled, even tho it won't be rendered)
Line 5: Line 5:
 
To use it for [[Diamond]] 1.8.22 in the General 1v1 RoboRumble, you'd do the following:
 
To use it for [[Diamond]] 1.8.22 in the General 1v1 RoboRumble, you'd do the following:
 
* <tt><nowiki>{{subst:rumblestats:roborumble|voidious.Diamond 1.8.22}}</nowiki></tt>
 
* <tt><nowiki>{{subst:rumblestats:roborumble|voidious.Diamond 1.8.22}}</nowiki></tt>
* '''{{RumbleStatsDefault|link=http://literumble.appspot.com/BotDetails?game=roborumble&name=voidious.Diamond%201.8.22|rumble=RoboRumble|scorelabel=APS|score=90.33|rank=2nd|win=984|loss=1|plrank=2nd|glicko2=N/A|pwin=99.9|vote=14.26|score2label=Survival|score2=97.95}}'''
+
* '''{{RumbleStatsDefault|link=http://literumble.appspot.com/BotDetails?game=roborumble&name=voidious.Diamond%201.8.22|rumble=RoboRumble|scorelabel=APS|score=90.33|rank=2nd|win=984|loss=1|plrank=2nd|glicko2=N/A|pwin=99.9|vote=14.26|anpp=95.13|score2label=Survival|score2=97.95}}'''
  
 
For Twin Duel, the Survival and APS are swapped in the output:
 
For Twin Duel, the Survival and APS are swapped in the output:
 
* <tt><nowiki>{{subst:rumblestats:twinduel|voidious.twin.LuminariousDuo 1.13}}</nowiki></tt>
 
* <tt><nowiki>{{subst:rumblestats:twinduel|voidious.twin.LuminariousDuo 1.13}}</nowiki></tt>
* '''{{RumbleStatsDefault|link=http://literumble.appspot.com/BotDetails?game=twinduel&name=voidious.twin.LuminariousDuo%201.13|rumble=TwinDuelRumble|scorelabel=Survival|score=81.07|rank=1st|win=20|loss=4|plrank=5th|glicko2=N/A|pwin=83.33|vote=4.35|score2label=APS|score2=69.35}}'''
+
* '''{{RumbleStatsDefault|link=http://literumble.appspot.com/BotDetails?game=twinduel&name=voidious.twin.LuminariousDuo%201.13|rumble=TwinDuelRumble|scorelabel=Survival|score=81.06|rank=1st|win=20|loss=4|plrank=5th|glicko2=N/A|pwin=83.33|vote=4.35|anpp=88.68|score2label=APS|score2=69.34}}'''
  
 
The ranks are calculated dynamically, based on where the scores would put the bot in the current rankings (ignoring other versions of the same bot).
 
The ranks are calculated dynamically, based on where the scores would put the bot in the current rankings (ignoring other versions of the same bot).

Revision as of 05:17, 27 March 2013

A MediaWiki extension by Voidious that leverages the API access (append &api=True to URLs) on Skilgannon's LiteRumble instance to make it really easy to include rumble stats in your version history.

Example use and output

To use it for Diamond 1.8.22 in the General 1v1 RoboRumble, you'd do the following:

  • {{subst:rumblestats:roborumble|voidious.Diamond 1.8.22}}
  • RoboRumble ‒ APS: 90.33% (2nd), PL: 984-1 (2nd), Survival: 97.95%

For Twin Duel, the Survival and APS are swapped in the output:

  • {{subst:rumblestats:twinduel|voidious.twin.LuminariousDuo 1.13}}
  • TwinDuelRumble ‒ Survival: 81.06% (1st), PL: 20-4 (5th), APS: 69.34%

The ranks are calculated dynamically, based on where the scores would put the bot in the current rankings (ignoring other versions of the same bot).

Parameters

The first parameter is the rumble category, which can be any of:

  • 1v1 Rumbles: roborumble, minirumble, microrumble, nanorumble
  • Melee Rumbles: meleerumble, minimeleerumble, micromeleerumble, nanomeleerumble
  • Team Rumble: teamrumble
  • Twin Duel Rumble: twinduel

The second parameter is the full bot name and version, such as would be put on the RoboRumble/Participants page.

Templates

By default, the extension uses Template:RumbleStatsDefault, which is formatted as shown above. You can create your own formats, as well. Check out Category:RoboRumble Stats to find out how, and to browse existing templates.

Important usage note!

Please be sure to add the "subst:" tag when using this, otherwise it will be querying the RR server for the stats every time the page loads. Also, be mindful when doing repeated previews of a page after you insert this tag, as it will query the RR server every time until you submit. The RR Query API has some modest rate limits, so if this gets too much use in a short timeframe, the tag will just render an error string and you'll have to try again later.