As a baseball or softball team manager, you can generate a roster and keep team stats to share with your players. You can also keep a schedule and use the site to communicate with the team. Send out invitations to upcoming games and know at a glance who will be coming and who will not.

Players can view team stats, schedules, RSVP to games, and leave comments on the site.

The functionality to score live games (in person or on TV) and automatically generate box scores/scoresheets is coming soon.

Check out the tutorial for the complete rundown.

Of course. Once you figure out how to add a new team with the manager tools, you should see a little link at the top to "Change Team." This link will allow to to choose another team to view on the site.

Check with your manager. Only the manager knows that the correct URL for your team is.

Yes. Provided you are using the same e-mail address for both teams, you will be able to view all of your information when you log in. To change the team you are viewing, click on "Change Team" in the top-right corner of the page, just underneath the team that you are currently viewing.

Yes, there are lots of numbers to look at. When viewing team stats, you can hover over the stat names and you'll get a quick explanation of what the statistical abbreviations mean.

Buckle your seat belts.

BaseRuns (BsR) is a baseball statistic invented by sabermetrician David Smyth to estimate the number of runs a team "should" have scored given their component offensive statistics, as well as the number of runs a hitter/pitcher creates/allows. It measures essentially the same thing as Bill James' Runs Created, but as sabermetrician Tom M. Tango points out, BaseRuns models the reality of the run-scoring process significantly better than any other "run estimator".

BaseRuns was primarily designed to provide an accurate model of the run scoring process at the Major League Baseball level, and it accomplishes that goal very well: in recent seasons, BsR has the lowest root mean squared error of any of the major run estimation methods. But in addition, BaseRuns can claim something no other run estimator can -- its accuracy holds up in even the most extreme of circumstances and/or leagues. For instance, when a solo home run is hit, BaseRuns will correctly predict one run having been scored by the batting team. By contrast, when Runs Created assesses a solo HR, it predicts 4 runs to be scored; likewise, most linear weights-based formulas will predict a number close to 1.4 runs having been scored on a solo HR. This is because each of these models were developed to fit the sample of a 162-game MLB season; they work well when applied to that sample, of course, but are woefully inaccurate when taken out of the environment for which they were designed. BaseRuns, on the other hand, can be applied to any sample at any level of baseball, because it models the way the game of baseball operates, and not just for a 162-game season at the highest professional level. This means BaseRuns can be applied to high school or even Little League.

(from http://en.wikipedia.org/wiki/Base_Runs)

Due to the fundamental construction of its formula, BaseRuns models reality, correctly tracking the process of how runs are produced. It takes into account the run-scoring environment in which player statistics were produced, handling baseball and softball at all levels with equal efficiency. A batter who puts together a given stat line cannot be said to have a performance equal to X number of runs unless we know what the run-scoring environment was like. BaseRuns takes care of this.

Consider the value of the single relative to the home run in environments where a huge number of runs are scored (singles are almost as good as home runs) vs. environments where a single run may win a ball game (singles have much less value than a home run). BaseRuns makes the necessary adjustments.

Context truly matters. In a world in which every batter hit a homer, each one would be worth exactly one run because no one would ever be on base. Conversely, in a world in which every batter walked, each walk would also be worth exactly one run.

(from http://www.hardballtimes.com/main/article/base-runs-and-carl-hubbell/)

BaseRuns also handles extreme performances gracefully. Where some of the other run estimators choke, BaseRuns will accurately determine a value for the players who tear it up and those who can't.

While even the simplest version of Runs Created estimates team runs with reasonable accuracy, the multiplicative (A*B)/C structure of the formula is fundamentally flawed when estimating the runs produced by each individual hitter, particularly in the case of hitters with extremely high on-base and slugging percentages. The reason for this is that it is impossible for a player to get on base and then drive himself in -- players' on-base and slugging averages must interact with those of their teammates. Yet RC's simple OBP*TB form assumes that a player's own slugging is interacting with his own on-base percentage, which artificially inflates RC for players who score well in both categories.

...

This is generally not a major issue for most players, as their OBPs and SLGs are not high enough to significantly distort their Runs Created; however, superstars who put up impressive OBPs and SLGs will frequently see their RC artificially inflated by this phenomenon.

...

OPS (On-base Plus Slugging) is similar conceptually to runs created, except that it adds the A (on-base) and B (advancement) factors together, rather than multiplying them. This makes the statistic less accurate than runs created.

(from http://en.wikipedia.org/wiki/Runs_created)

In short, OPS and Runs Created aren't used on monkeystats.com because BaseRuns produces a more "accurate" representation of a player's value.

BaseRuns uses all statistics except for R and RBI, as they are resultant statistics and not component statistics for batters. Given that, BaseRuns does not reward clutch performance.

If you want more geekery, search the web for literature on the subject. There's lots out there.

Basically, the Player of the Game is the player who has the highest BaseRuns for that game. See above for a full explanation of BaseRuns.

The Player of the Game is NOT awarded to the player who had the most R or RBI, and it is NOT awarded to the player who had the most clutch hits, as there is no way to determine this with the given stats. A better POG formula would be based on something like WPA, but there is no way to run those sorts of calculations without entering complete play-by-play data for each game, something that most managers don't want to do.

My name is Jeff. I'm a recreational baseball and softball player, and for years I've been thinking that there should be a better way to manage team stats and schedules.

I was tired of driving an hour to a game only to find out that not enough players showed up to play, and I was tired of receiving impossible-to-read stat spreadsheets by e-mail, if I received stats at all. So I decided to put this site together as a way for managers to centrally manage their teams, to communicate with their players, to ensure they had enough players for each game, and to make stats easily accessible.

All the cool domain names are already taken. Getting desperate, I ran through all the animals I could think of and tacked "stats" onto the end. Strangely, "monkey" was the only one that was available. And it's the coolest animal. So I win.

It's still in development. There's a lot of number-crunching going on behind-the-scenes, especially when displaying statistics or leader boards, and a few of the pages have not been built in the most efficient way. I'm working on it!