-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
For bugs, please open an issue on the Issues page. For feature requests, first check if there is already an issue for it on the Issues page, but otherwise, let's talk about it in a discussion on the Discussions page, and then we'll open an issue for it if it's something that is in line with the goals of the project.
In the game, you can create a franchise from a league. If you export that franchise to a new league and then start a new franchise with the newly created league, the game treats it as a new franchise from the first. However, in this app, the franchise represents the continuation of the original franchise into the new franchise, and so forth.
In my case, I like to treat franchise mode like "manager mode." I play through each franchise for 15 seasons. On the 16th season, I play through the draft, but before playing a game, I export the franchise to a new league, start a new franchise, and then play through another 15 seasons with a different team. This app has built-in support for this behavior, but it is not required.
This is something that I would like to and plan to do, but haven't yet had the time to approach. For now, since SMB Explorer has the ability to export the data to CSV files, this app reads the CSV files instead (which is slower, but works for the time being).
Currently, there is no way to do this, although in the future I may add this functionality. One issue with this might be that incomplete season data is exported. As I was working through SMB Explorer, I noticed that some amount of data for retired players seems to be removed, as well as possibly the season schedule for all but the current season. If that is the case, that will be an issue for this app, as it will not be able to match the data correctly.
Can I export my franchise to a new league, create a new franchise with a shuffle draft, and import the new league into this app?
Yes, in theory this is supported. If a player from the free agent pool was previously imported into the app, though, and is later re-introduced into the free agent pool, the app will not be able to match the player to the existing player record, and so it will create a new player. This is something that I would like to address in the future, but for now, it is what it is.
No, this app only supports SMB4. It woudn't take much to add support for SMB3, but I am not prioritizing it at this time.
Once you have imported a player, their name is locked in. This may change in the future to match the team name behavior below, but for now, this is unsupported.
Once you have imported a team from a franchise playthrough, you can change its name and the import logic can successfully match it on the team ID. However, if you end a franchise in the game and export it to a new league (and franchise with the new league), the team ID will change, and the import logic will not be able to match it. There may be a way to fix this in the future, but for now, this is unsupported.
You can, however, update team names from season to season within a franchise playthrough. The app in this case is able to match the team on the team ID, and so it will update the team name accordingly for seasons going forward.
These are not supported at this time.
smbWAR is a metric that I created to measure a player's value to their team. It is loosely based on a combination of bWAR and fWAR, but is not the same (and will likely be improved upon in the future). It is calculated as follows (as of v1.0.0):
smbWAR = ((OPS+ - 95) * #PA * Batting Scaling Factor) + ((SB - CS) * Baserunning Scaling Factor)
where:
-
OPS+is the player's OPS+ (OPS adjusted league factors) -
#PAis the number of plate appearances the player had -
Batting Scaling Factoris a factor that scales the batting component of smbWAR to be roughly equivalent to a player's expected WAR for batting only for a full 162-game season- It equals
0.00021521739
- It equals
-
SBis the number of stolen bases the player had -
CSis the number of times the player was caught stealing -
Baserunning Scaling Factoris a factor that scales the baserunning component of smbWAR to be roughly equivalent to a player's expected WAR for baserunning only for a full 162-game season- It equals
0.0434782608
- It equals
- No positional adjustments are made at this time
smbWAR = ((ERA+ + FIP+) / 2) * #IP * Pitching Scaling Factor
where:
-
ERA+is the player's ERA+ (ERA adjusted for league factors) -
FIP+is the player's FIP+ (FIP adjusted for league factors) -
#IPis the number of innings pitched the player had -
Pitching Scaling Factoris a factor that scales the pitching component of smbWAR to be roughly equivalent to a player's expected WAR for pitching only for a full 162-game season- It equals
0.000478260869
- It equals
I know the scaling factors are arbitrary, but the goal here was to create a value that roughly emulates WAR, without being able to calculate WAR directly (since the game does not provide the necessary data to do so).
Ideally, in the future, SMB Explorer will calculate WAR directly, and this metric will be replaced with the actual WAR value. As of right now, it is a calculated value, and not a value that is stored in the database, meaning this can be changed in the future without any migrations necessary.
Another downside of this is that in some cases with extremely small sample sizes (playoffs, short seasons, etc.), the ERA+ for pitchers (or conversely with OPS+ and a batter) can be extremely high, and so the pitching component of smbWAR can be inflated. This is something that I would like to address in the future, but for now, it is what it is.