Introducing the Ottoneu Toolbox

After releasing the Ottoneu Draft Tool last year, I’ve gone back to the drawing board to make a more robust application for playing Ottoneu baseball. The results of those efforts are the creation of the new open-source application, the Ottoneu Toolbox. The latest release can be found here.

The Toolbox retains the functionality of the Draft Tool from last year, but also provides users the ability to also create their own Ottoneu values based on projections either uploaded by the user or (with entered FanGraphs credentials), automatically downloaded from the FanGraphs website.

Currently, only values for points leagues (FGP or SABR) are supported, but I hope to have other game types in the future.

For draft monitoring. several new features have been added since last year’s iteration:

  • 4x4 and 5x5 leagues supported.
  • Ability to show/hide rostered players
  • Ability to set target players with target salaries
  • Ability to remove specific players from lists
  • Display of salary information (average salary, last 10 add, roster %)

As with last year, the executable provided from the release page is unsigned, and Windows Defender will tell you it is unsigned, but will allow you to run it. As the code is open-source, you are free to clone the git repository and run it from the command line if you prefer.

Again, my goal is to provide any tools free, to lower the bar to entry for anyone who wants to play Ottoneu. If you want to support the work, you’re welcome to contribute to my ko-fi page, but it’s not required for tool access, and I hope to keep it that way.

See you on the field!

10 Likes

As an update to this, some users are experiencimg difficulty getting projections to load either through the automatic download or the custom upload. I need to investigate the automatic download issue, but for uploading projections, please use the fix in the v1.1.1-beta release. I will try to diagnose and fix the automatic download issue as soon as possible.

5 Likes

Automatic downloads are functionally fixed. Unfortunately for the time being, the downloads with Chrome or Edge are not done headlessly until I can do further investigation. Firefox downloads are still done headlessly. These fixes are available in the v1.1.1-beta2 release.

2 Likes

An update: a new release is available v1.1.2 with minor bug fixes. This version also notifies the user on startup if a newer release is available so this space doesn’t need to be monitored. The latest release can be found here.

1 Like

Any updates on the upload requirements? It’s blank on the wiki and no matter how I format the csv data or what order it is in etc I can’t seem to get anything to upload (for player projections). Been trying a mix of all relevant points league metrics and name and playerid. It references a log file but I haven’t quite found where to access that file to dive into what the holdup is, haha. I figure this will work for this year as well if I upload 2024 projections

Yes, the current release (1.2.7) will support 2024 projections. The log file should be called toolbox.log and be located in the “logs” directory in the same folder that you run the application from. There may be a useful message in there.

Make sure your csv file has headers that contain minimally the following (order and case insensitive):

Batters:
Name,Team,G,PA,AB,H,1B,2B,3B,HR,R,RBI,BB,HBP,SO,SF,SH,SB,CS,AVG,OBP,SLG,PlayerId

Pitchers:
Name,Team,W,L,QS,ERA,G,GS,SV,HLD,IP,H,R,ER,HR,BB,SO,WHIP,FIP,PlayerId

If you are still having issues, feel free to reach out for more help. Thanks!

1 Like

Sweet, I wasn’t including many categories outside of points scoring ones for my league so that might be it. Fangraphs put a stop to their downloads since the original post right? I don’t think any of them will work unless you pay for an actual membership. To get around it I’ve been trying to copy and paste the full 3700 ish (hitters) from the web into excel and clean it up and add playerid from there. Wondering if it is worth it to just pay for the graphs membership haha.

1 Like

post the dataset if you’re able to clean it up. sadly i’m having the same problem :frowning: