Skip to content


Repository files navigation

Blaseball Status

Codeship Status for Mixolyde/blaseballstatus



An attempt to replicate Playoff Status behavior, but for Blaseball.

Published at


  • Replace old test code with new api calls
  • Figure out postseason calculations
  • Figure out new tiebreakers
  • Figure out what's up with tied records getting weird sim results
  • Postseason schedule
  • Handle postseason data live
  • Team rank history over season chart
  • Schedule pages
  • Get a twitter account and button
  • Factor future schedule into magic numbers
  • Move project to a blaseball-specific account on github
  • Reduce API calls during siesta
  • Copy the live ticker to the top of the page
  • Show era and sub-era descriptions

Planned release schedule

  • v0.0.1
  • Wild/Mild league data toggle
  • Live pull data on refresh (thanks, cors-proxy!)
  • Games behind math
  • v0.0.2
  • Data loading indicator and data filling as it comes in
  • Winning magic numbers
  • Party time magic numbers
  • Clinch calculations
  • v0.0.3
  • Auto refresh data in browser
  • Save last view
  • About and info pages
  • v0.0.4
  • New playoff birth rules
  • Group by division toggle
  • Properly calculate games played
  • Automate static data updates during the season
  • v0.0.5
  • Playoff prediction percentages
  • v0.0.6
  • Postseason content
  • Add emoji to team rows
  • Show full team name in wide view
  • v0.0.7
  • Linkable view states with history
  • Add donation button
  • Move web site to a blaseball-specific domain
  • Handle Wild Card decree on-the-fly
  • v0.0.8
  • v0.0.9
  • Display data update time in local time zone
  • Disable buttons on certain views
  • Unit test coverage report
  • v0.0.10
  • Update to api2
  • Find and fix bugs in new version
  • v0.1.0
  • Live Postseason chance updates
  • Team Schedules
  • Get a twitter account and button
  • Move project to a blaseball-specific account on github


Installing Dart

You will need Dart installed and on your $PATH to build and test the app.

On Linux

cd ~
wget --quiet
unzip -q -o -d ~
export PATH=$PATH:~/dart-sdk/bin:~/.pub-cache/bin
pub global activate peanut
pub get

On Windows, get the Windows Dart SDK zip, unzip it somewhere, and add that unzip's bin folder to your PATH variable. You also need to add the Pub Cache bin folder to your PATH, which may be in c:\Users\<username>\AppData\Roaming\Pub\Cache\bin.

You typically need to call the '.bat' versions of the helper tools in Windows.

pub.bat global activate peanut
pub.bat get

Building and testing

You can run all unit-tests with pub.bat run test or a specific test with dart test\test-file.dart.

To serve up the app and test it in your browser run

pub.bat global activate webdev
webdev.bat serve

And go to http://localhost:8080/.

On Windows, there doesn't seem to be a clean way to shutdown the local webdev server, so you may have to kill the process from Task Manager, or with taskkill -f -pid ###.

I find the Windows Git Shell from Github that emulates a lot of Linux stuff to be really useful.

alias killdart='tasklist |grep dart |head -1 |awk '\''{print $2}'\'' | xargs taskkill -f -pid '


The Peanut plugin will automatically build your static web content and commit it to the gh-pages branch. Then you can push the gh-pages branch up to github.

git push origin --set-upstream gh-pages

Your site should eventually get published to


There are two main code components, and three infrastructure components.

Code components

  1. tools/update_stats.dart - a CLI script which generates the json data files for the site and uploads them to an S3 bucket in AWS.
  2. web - All of the web site code that gets published to the gh-pages branch by the dart plugin Peanut.

Infrastructure components

  1. AWS S3 - A public data bucket for holding the json data structures with all of the stats and season data.
  2. AWS EC2 - A very simple server with a cronjob for periodically running tools\update_stats.dart
  3. Codeship - An automated build service which automatically tests the code and deploys the published web site to the gh-pages branch, which is picked up by github and deployed to the site.


Huge thanks to:

Created from templates made available by Stagehand under a BSD-style license.