Showdown Bot is the simplest way of creating custom MLB Showdown cards. Simply enter a player's name, season, and image. The Showdown Bot takes care of the rest.
(Optional) pyenv or virtualenv
MLB Showdown Bot is available on PyPi
pip install mlb-showdown-bot
MLB Showdown Bot can be run directly from the CLI
showdownbot --name "Mike Piazza" --year 1997 --context 2001
Example Python use:
from mlb_showdown_bot.showdown_player_card import ShowdownPlayerCard
from mlb_showdown_bot.baseball_ref_scraper import BaseballReferenceScraper
name = 'Mike Piazza'
year = '1997'
set = '2001'
# GET PLAYER DATA
scraper = BaseballReferenceScraper(name=name,year=year)
statline = scraper.player_statline()
# CREATE SHOWDOWN CARD
showdown = ShowdownPlayerCard(
name=name,
year=year,
stats=statline,
set=set,
print_to_cli=True
)
# CREATE SHOWDOWN CARD IMAGE
showdown.card_image(show=True)
At minimum, the bot takes a player's NAME and SEASON as inputs. The first step is identifying which player the user is trying to create a card for.
Included in the Bot's files is a mapping of Player Name (ex: Jacob DeGrom) -> Baseball Reference Id (ex: degroja01). The Bot will use this mapping if the entered name matches ONE player in the mapping file.
Because there have been around 20,000 unique players in the history of the MLB, there are cases of multiple players sharing the same name (ex: Frank Thomas (1951-1966) and Frank Thomas (1990-2008)).
To solve for this, the bot first searches the phrase "baseball reference {name} {year}". (Ex: "baseball reference frank thomas 1994"). Using Google's indexing algorithm, the bot chooses the first search result and derives the player's unique baseball reference id from it.
The bot uses Baseball Reference as it's source for player data. Baseball Reference stores statistics for all of the ~20,000 players to make an appearance in the big leagues.
Stats are extracted from the the baseball reference page for the player id selected in the previous step. Stats like batting average, home runs, and defensive metrics (tzr/drs) are extracted only for the chosen season(s). For pitchers, opponent batting results are used (ex: batting average against).
Some of this player data is unavailable for certain years or timeframes. Below is a list of unsupported time periods:
If the selected season occured after 2015, sprint speed is also extracted from Baseball Savant. A player's average sprint speed is used to determine in-game SPEED.
Overrides give additional ways to customize a player's card. They are applied by adding text after the player's name. These are the available overrides:
The stats scraped in the previous step are used as inputs to determine the player's MLB Showdown card for the selected season. The player's in-game abilities are derived using the probability of outcome for each result on an MLB Showdown chart. More about that process is detailed below in the Card Methodology section.
To create the card image, the Pillow library is leveraged to dynamically create the final image. The user can add optional enhancements like selecting an image and adding graphics like Special Editions (ex: Super Season, Cooperstown Collection) and image parallels.
The following steps are used to select the most accurate MLB Showdown card stats for a player:
Each of these steps work by a using baseline opponent to project in-game outcomes. A baseline opponent represents the approximate average pitcher or hitter a player would face in-game. The baseline stats are represented by a dictionary that includes Command, Outs, and number of chart results for each category (SO, BB, HR, etc). Baseline opponents differ for each MLB Showdown set.
Chart(
is_baseline = True,
set='2001',
command=7.10,
values={
'PU': 0.00,
'SO': 0.85,
'GB': 1.12,
'FB': 1.15,
'BB': 5.10,
'1B': 7.83,
'2B': 1.60,
'3B': 0.25,
'HR': 2.10,
}
)
These baseline opponents are vital to determining the final output of the player card. Adjusting these values will change which chart the bot decides is the most accurate. Because the actual baselines used to create the original sets are unknown, these are estimations based on set averages and testing against WOTC cards. The goal is to find the baseline weights that most closely resemble the original sets from 2000-2005.
These baselines are also dynamically adjusted when a card is created outside of the original WOTC era. This is done by comparing the MLB averages during the original set's year vs the card's year.
For example when trying to create an Aaron Judge 2024 card in the 2001 style, the baseline opponent pitcher be adjusted to have better stats than the original from 2000 due to pitching being better in 2024 compared to 2000. This means Aaron Judge's card will be be better in order to match his real statline now that his opponent is better.
A player's chart is generated by populating each result category.
The number of results (out of 20 slots) assigned to each category are calculated using this formula:
(category_real_life_results_per_400_pa - (baseline_opponent_advantages_per_20_rolls * baseline_opponent_category_results)) / my_advantages_per_20_rolls
Important caveats:
For Expanded sets the formula is slightly adjusted to account for results > 20. A sub-21 slot value is calculated in order to dictate what each slot between 1-20 is worth. The purpose is to be able to assign a probability to results over 21+ for projection purposes caused by the use of strategy cards. This can change depending on the set and player type. For example 2005 hitter 1-20 slots are worth 0.975 (1.0 would be the default). The remaining 0.5 slots are distributed between slots 21-30. The method of distribution can be linear, linear decay, or geometric progession depending on the set, player type, and player command.
Here is an example of slot values. Note the actual numbers have more decimal places and add up to 20.
1-20: 0.95
21: 0.250
22: 0.200
23: 0.160
24: 0.128
25: 0.102
26: 0.081
27: 0.065
28: 0.012
29: 0.002
30: 0.000
Now that a chart has been generated for each Command/Out combination, the bot has all the required datapoints needed to determine accuracy.
The player's Command and chart values are used to estimate the player's in-game statline for 400 Plate Appearances. That statline is then compared to the player's real life statline per 400 Plate Appearances. Some stat categories are given more weight than others (ex: OBP accuracy is usually weighted more heavily than SLG accuracy). Both real and in-game statlines are displayed in website and CLI outputs.
All Sets Use these categories of comparison for accuracy:
For expanded sets after 2002, WOTC used a linear scale to help determine command based on real OBP. This is different than other sets that allowed more low command, high out cards (ex: 2C, 19 Out). See the graph below for a scatterplot of 2004 pitcher command vs real OBP. Most pitchers follow the same formula with the exception of a few outliers.
The Bot follows a similar formula but allows more flexibility and probability of these outlier command/out combinations (ex: 1C, 20 Out) as long as the expected OPS accuracy meets a certain threshold. Usually these outlier charts will have their baseline accuracy reduced by 1-5% to reduce the volume of outliers. It will also adjust the scale across Eras where league avg OBP values change compared to the Steroid Era. The estimated command is then used as an accuracy category.
To determine final accuracy an accuracy percentage is calculated per category and then weighted to create a score out of 100%.
Here is an example for 2004 Base Set Steve Trachsel (based on 2003 statline):
| Category | Actual | Showdown | Accuracy | Weight |
|---|---|---|---|---|
| Est. Control | 3.1 | 3.0 | 98.4% | 30% |
| OBP Against | .320 | .328 | 97.7% | 30% |
| SLG Against | .445 | .433 | 97.4% | 20% |
| OPS Against | .765 | .761 | 99.5% | 20% |
| Overall | - | - | 98.2% | - |
The chart with the highest aggregate accuracy is chosen as the final chart returned by the bot.
To display one of the other chart outputs, add the optional chart_version/ argument on the CLI or the Chart option on the website. It allows the user to use any of the other charts from the Top 5 most accurate list. Use the --chart_version argument if in the CLI or choose an Chart > 1 in the Stats Version section of the website.
Each player can have a maximum of 2 position slots for WOTC sets (2000-2005). That is expanded to 3 positions for CLASSIC/EXPANDED sets.
For a position to qualify, the player has to make at least 7 appearances or at least 15% of games at that position. For multi-year/career long cards, 25% of games must be played at that position. The positions are then limited to the top 2 slots (3 if CLASSIC or EXPANDED set) by number of appearances.
In order for utility players to qualify for IF, they must have played each positions at least once in a single season or 15% of games for multi-season. To achieve IF+1 they must have a combined infield defense rating of +6. The rare IF+2 is achieved by having +10 or more. For example 2015 Marwin Gonzalez is eligible for IF and qualifies for IF+1 due having a combined +7 (1B+0, 2B+2, 3B+2, SS+3).
In WOTC sets (2000-2005), 2B/3B/SS can be combined to conform to 2 position slots. When combined, the average of the 2 positions will be used as the final value. Positions will be combined only if their in-game defensive ratings have a difference of 2 or less. For example if the player has SS+4 and 3B+1, they will stay separated.
In-game defensive ratings are calculated based on either Outs Above Avg (OAA), Total Zone Rating (tzr), Defensive Runs Saved (drs), or Defensive Wins Above Replacement (dWAR). The bot will choose which metric to use depending on the year:
All these metrics work by comparing a certain player to the average replacement at that position (0). For example a +10 TZR is an above average rating, while a -7 TZR is below average.
The player's in-game rating is calculated with a percentile within a range. The player's in-game rating is calculated based on that percentile multiplied by the highest rating for each position (Ex: 3B: +4, SS: +5, LF/RF: +2).
Ex: David Wright 2007 (+12 DRS)
* 3B Rating = Percentile * 3B In-Game Max
* 3B Rating = 0.8 * 4
* 3B Rating = 3.2
* 3B Rating = +3
For multi-year cards, the bot will take an average or median depending on which metric is used. Below is the breakdown for each metric.
If the multi-year card spans across available metrics (ex: a card using 2014-2022), it will use the metric available for the entire period.
Pitchers fall under the following categories
In-game SPEED is calculated differently depending on the year.
The combination of SPRINT SPEED/STOLEN BASES is then converted to a percentile based off a range (the same way that defense is calculated). That percentile is then multiplied by the maximum in-game speed.
For example, the range of SPRINT SPEED is from 23 ft/sec to 31 ft/sec. If a player's SPRINT SPEED was 27ft/sec, they are in the 50th percentile (0.5). If the maximum in-game speed was 25, then this player's in-game SPEED is equal to 25 * 0.5, which rounds to 13.
Eras can also effect speed. In Eras with a high average speed (ex: Dead Ball Era) speed will be slightly reduced compared to modern eras. The purpose of this is to maintain a balance of speed across time periods where SB numbers fluctuated.
When the card is using SB, a set based multiplier is used to match the original WOTC values. Ex: For a player with 26 SB per 650 PA, 31.72 would instead be used in the 2001 se (1.22x). For 2000/2001 sets, if variable speed is enabled the multiplier is changed to 1.05.
2000: 1.21
2001: 1.22
2002: 1.12
2003: 0.962
2004: 1.0
2005: 1.0
CLASSIC: 1.0
EXPANDED: 1.0
If the card uses SB and the player's speed is over 20, an separate linear scale is applied for values over 20. This results in a more evenly distributed set of players with 21-28 speed than the traditional 8-20 scale allows for.
The formula for 21+ speed works as follows: starting_point_over_20 + (elite_spd_percentile * remaining_slots_over_20). This starting point will change across sets (ex: 2002 starts scaling back at 22, 2005 starts at 21, 2001 Variable Spd at 20). The percentile uses 22 SB/400 PA as the minimum (that's around the required SB to get to 20 SPD) and uses 100 SB as the maximum. That means if you stole 100+ bases per 650 PA, you will get the maximum speed (28). 28 is the maximum speed, so if a player has over 100 SB/650 PA (ex: Rickey Henderson 1982) they will stay at 28 SPEED.
Here is an example using Scott Podsednik's 2004 stats in the 2005 set (63.8 SB/650 PA):
SPEED = 21 + (elite_spd_percentile * remaining_slots_over_20)
SPEED = 21 + ( (SB - 22) / (100 - 22) * (28 - 21) )
SPEED = 21 + ( (63.8 - 22) / (100 - 22) * (28 - 21) )
SPEED = 21 + ( 0.535 * 7 )
SPEED = floor(21 + 3.75)
SPEED = 24
** Pitchers are automatically given a SPEED of 10.
Innings pitched is calculated based a Pitcher's innings pitched / games played (IP/G). The components of that equation will change depending on the pitcher's type (STARTER vs RELIEVER).
Ex: Nestor Cortes (2021) (RELIEVER)
Stats:
G: 39
GS: 12
IP/GS: 5.5
IP: 123.2
IP = (IP - (GS * IP/GS)) / (G-GS)
= (123.67 - (12 * 5.5)) / (39-12)
= 57.67 / 27
= 2.09
= 2 IP
Icons were a feature introduced in 2003 MLB Showdown sets.
This is the list of available icons and how a player is eligible:
** Some of these thresholds are slightly different than the original game.
A player's point value is calculated by summing up a player's value provided in the following categories:
Hitters
Pitchers
A player's point value in each category is calculated by multiplying the WEIGHT given to the category by the PERCENTILE the player placed in.
The WEIGHT is the number of points provided if the player achieves the 100th percentile in that category. The percentile is calculated by taking difference between the player's stat and minimum values for a category, and dividing it by the difference between maximum and minimum values assigned to the category. The WEIGHT represents how many points a player will receive if they are in the 100th percentile in the category. NOTE: WEIGHTS change across sets.
This calculation is performed for each category. The categorical point values are summed into the player's final total point value.
Ex: Derek Jeter, 550 PTS (2003 Set, 2002 Stats)
Projected Showdown Statline:
BA: .293
OBP: .366
SLG: .445
OPS: .811
PA: 730
1B: 140
2B: 25
3B: 2
HR: 23 (20.4 per 650 PAs)
BB: 76
SO: 107
SPD: SPEED A (18)
DEF: SS+0
ICONS: None
Points (OBP) = WEIGHT * PERCENTILE
= 150 * 0.56
= 84.1 pts.
Points (BA) = WEIGHT * PERCENTILE
= 70 * 0.64
= 44.89 pts.
Points (SLG) = WEIGHT * PERCENTILE
= 170 * 0.45
= 75.96 pts.
Points (HR) = WEIGHT * PERCENTILE
= 50 * 0.42
= 20.76 pts.
Points (SPD) = WEIGHT * PERCENTILE
= 65 * 0.80
= 52 pts.
Points (DEF) = WEIGHT * PERCENTILE
= 65 * 0.0
= 0 pts.
Points (Total) = Round(52 + 20.76 + 75.96 + 44.89 + 84.1)
= 280
There are additional weights/logic applied across the different sets to try to match to the original WOTC sets.
Multi-year or career long cards can be created on Showdown Bot using the year input. Here are some examples:
Card methodology will slightly change if the user enters a multi-year card. Differences include:
The original MLB Showdown game was built during the steroid era. This means the card formula is based on the Steroid Era run environment, where hitting was more dominant than pitching. In the year 2023 pitching is now stronger, and hitters are more focused on hitting home runs at the cost of more strikeouts. These evolutions are common throughout baseball history, and the Bot's eras feature helps adapt cards to be normalized across these different periods.
Each Era adjusts the baseline opponent to better represent the run scoring environment of that period. This means cards will produce more accurate due to them facing the average opponent of their era rather than the average opponent of the Steroid era. In the newest Showdown Bot release, this will now adjust dynamically year to year. If the user manually selects an era, the adjustment will use an average of league stats across years.
For example, below are 2001 set baseline pitcher attributes during the Steroid and Statcast eras.
| Attribute | Steroid Era (2000) | Statcast Era |
|---|---|---|
| Control | 16.0 | 16.7 |
| Outs | 3.0 | 3.13 |
| SO | 3.75 | 4.46 |
Because the average control and outs are higher in the Statcast Era, hitter charts will be improved in order to reach their expected season stats. Hitter chart strikeouts will decrease as well due to the pitchers having more results on their charts.
There are also slight other adjustments across eras, including reducing speed slightly for eras where stolen bases were extremely high.
As of the 3.0 update, Showdown Bot now supports all players from Baseball Reference, including the Negro Leagues and pitchers from the 19th century. Data for these players is not fully available, so the Bot does it's best to fill in gaps through estimation. Any estimation will show a '*' next to the category in the breakdown section.
Here are the stats that the Bot will estimate if unavailable:
Pitchers
Hitters
shOPS+ takes a player's projected in-game OPS and normalizes it across the entire set in that year (26 players/team). It adjusts a player's OPS slightly to account for a typical Showdown manager's tendency to draft higher Onbase/Control cards. A score of 100 is league average, and 175 is 75% better than the league average.
For example, Yandy Diaz's 2022 CLASSIC card (10 Onbase) had a projected .838 OPS, which was 48% better than the 2022 MLB average after being adjusted to account for higher control pitching. As a result, his shOPS+ was 148.
Calculation:
((PLAYER_PROJ_OBP / LEAGUE_AVG_PROJ_OBP) + (PLAYER_PROJ_SLG * COMMAND_ADJUSTMENT_FACTOR / LEAGUE_AVG_PROJ_SLG) - 1) x 100
How does the Command Adjustment work?
The Command Adjustment Factor is a way for shOPS+ to account for normal Showdown draft tendencies. Managers tend to weight gaining the advantage over number of outs on their player's chart. One player's stats against the "avg" player in a set may not match the typical card drafted in a real Showdown draft setting.
For example, let's compare Mike Clevinger vs Blake Snell in the CLASSIC set.
These 2 cards have very similar projected OPS against (Clevinger having the slight edge at .622 vs Snell's .625), meaning their non-adjusted shOPS+ numbers are similar (Clevinger at 116, Snell at 114).
Most Showdown managers however would see a larger difference between these 2 cards, as Mike Clevinger's +4 Control performs significantly better against higher Onbase opponents, especially with no 2B on his chart. shOPS+ accounts for that, applying a 1.04 adjustment factor to Clevinger's SLG and a 0.94 to Snell. This results in a larger disparity between the 2 pitchers, with Clevinger ending with a 120 shOPS+ vs Snell's 108.
Use Editions to add style variety to your cards. There are currently 6 different Editions available on Showdown Bot.
Cooperstown theme is available on all sets. It replaces the player's team logo with a the official Cooperstown Collection logo, changes the template color in 04/05 sets, and some certain players adds new player art.
Custom player art is available in 2003, 2004, and 2005 sets. CLASSIC/EXPANDED sets will use the official Cooperstown color scheme in the chart.
Super Seasons highlight outstanding single season performances throughout baseball history. A custom super season logo may replace the player's team logo, and certain years add a list of up to 3 accolades. 2004 and 2005 sets feature a special red template, as well as a grid pattern in the background of all showdown library sourced player images.
Below are the possible accolades, ordered by priority. Multi-year cards follow a similar pattern, however will aggregate cross-year accolades together (ex: 7X ALL STAR).
** Note if the accolade's text is too long and does not fit within the image, it will excluded.
1. AWARD WINNER: If the player won any of the following awards, they will show up first in the accolades. The exception is sets that include icons (03,04,05), where awards are deprioritized to the end.
2. AWARD PLACEMENT: If the player was in the Top 3 for MVP or Cy Young voting, it is prioritized second.
3. LEAGUE RANKING: Prioritized third is league rankings within the metrics below. These are ranked first based on placement, then based on the ordering below.
HITTERS
PITCHERS
4. STATS: If the player does not have enough awards and accolades, their stats will be used. See below for ordering and minimum requirements.
Some stats include a historical cutoff, meaning if the player's stat is greater or equal to that number it will be included.
HITTERS
| Stat | Season Min. | Season Historical | Career Historical |
|---|---|---|---|
| HR | 30 | 60 | 500 |
| RBI | 100 | - | - |
| HITS | 175 | 240 | 3000 |
| BA | .300 | .390 | - |
| OBP | .400 | - | - |
| SLG | .550 | - | - |
| dWAR | 2.5 | - | - |
| OPS+ | - | - | - |
| bWAR | - | - | - |
PITCHERS
| Stat | Season Min. | Season Historical | Career Historical |
|---|---|---|---|
| WINS | 14 | - | - |
| SAVES | 20 | - | - |
| ERA | - | - | - |
| WHIP | - | - | - |
| bWAR | - | - | - |
Here is an example of how the Bot ranks accolades for 1999 Chipper Jones:
| Rank | 2000-2002 Sets | 2003-2005 Sets |
|---|---|---|
| 1 | NL MVP | 3RD IN NL HR |
| 2 | SILVER SLUGGER | 3RD IN NL OPS |
| 3 | 3RD IN NL HR | 3RD IN NL WALKS |
| 4 | 3RD IN NL OPS | NL MVP |
| 5 | 3RD IN NL WALKS | 4TH IN NL OBP |
| 6 | 4TH IN NL OBP | 4TH IN NL SLG |
| 7 | 4TH IN NL SLG | 4TH IN NL TOTAL BASES |
| 8 | 4TH IN NL TOTAL BASES | 5TH IN NL WAR |
| 9 | 5TH IN NL WAR | 2ND IN NL OPS+ |
| 10 | 2ND IN NL OPS+ | 7TH IN NL 2B |
| 11 | 7TH IN NL 2B | 7TH IN NL RUNS |
| 12 | 7TH IN NL RUNS | SILVER SLUGGER |
| 13 | 10TH IN NL BA | 10TH IN NL BA |
| 14 | 110 RBI | 110 RBI |
| 15 | 181 HITS | 181 HITS |
Note that in the final version for the 2004 set, NL MVP is shown despite it being ranked 5th. This is because the prior accolades would have been cut-off in the image!
Replaces a player's MLB team with their birthplace country. Adds a custom background for all sets that is inspired by WOTC promo cards. For automated images, there will be some World Baseball Classic player images available.
List of supported countries:
2004 and 2005 sets feature a special red template, as well as a grid pattern in the background of select players. CLASSIC/EXPANDED sets feature a new gradient design for the outs portion of player charts.
All Star Game logos are available on all sets for all seasons since 1980. Since 2021, custom background art and is available and will continued to be updated every year.
Rookie Season replaces a player's team logo with a custom rookie season icon. Some players in CLASSIC/EXPANDED sets also have special edition flashback card art shown above.
The Holiday theme adds a simple Christmas Tree inspired border to any card. This includes user uploaded photos, automated images, and silhouettes.
Adds postseason logo to images. Only available when the Postseason period is selected.
Showdown Bot now includes new sets that modernize the look and play of MLB Showdown!
The CLASSIC/EXPANDED set designs takes elements from classic MLB Showdown sets and add a modern twist, resulting in a streamlined design that will look great with any background image. Chart and Command colors will change from team to team, creating a blend of 2000/2001's color with 2004/2005's simplicity.
These sets are split between Classic and Expanded styles, with the goal of offering modern cards to every type of Showdown fan. The Classic style is most compatible with 2000/2001 sets, while Expanded fits with 2002-2005 sets. You will see a visual indicator of the card style in the bottom left of each card.
The Classic Style is made for the OG Showdown fan who prefers the 2000/2001 sets. In this style, hitters have lower Onbase numbers (between 4-12) but better charts. It uses the 2001 set as a starting point, but alters the original formula to fix gaps while maintaining compatibility.
Changes from 2001 set:
The Expanded Style is made for the new school Showdown fan who prefers the 2002-2005 sets. In this style, hitters have higher Onbase numbers (between 7-16) but less impactful charts. Charts also expand past 20, creating possible results outside of the normal 1-20 range. It uses the 2005 set as a starting point, but alters the original formula to fix gaps while maintaining compatibility.
Changes from 2005 set:
There is now an additional option for Dark Mode, available on all sets. Works with any player!
Image Parallels add unique and bold designs to make Showdown cards pop! They work on all automated images and across all sets.
Available Parallels:
Stay tuned for more image parallels coming soon!
The periods option lets you choose the exact period of stats to use for your Showdown card.
These are the available options:
This is the default period, and will include all games within the selected season(s). Excludes postseason.
Includes postseason stats from all rounds. Future update will let the user filter to certain rounds (ex: World Series).
Certain stat inputs are unavailable for the playoffs. The following stat inputs will use regular season values:
Filters data to only games within a date range.
NOT available for multi-year cards.
Certain stat inputs are unavailable for exact date ranges. The following stat inputs will use full regular season values:
Filter to stats from a particular split on baseball reference. See player's "Splits" pages for available values. Name must match exactly.
Certain stat inputs are unavailable for splits. The following stat inputs will use full regular season values:
The More Options menu provides additional customizations to your Showdown Cards
Adds border to image. If auto image, player image will bleed into the border. Otherwise fills in the border with the player's team color.
Dark Mode will change the following sets chart colors to black:
It will also change the background color for compatible image parallels (ex: Team Color Blast)
Adds a text box with the player's year for the following sets:
Adds a year abbreviation (ex: '96) to the following sets:
For 2004/2005 sets, changes the year abbrevation on the bottom right to be the year + 1. For example if the card's original year is 2022, the text shown will be '23.
Removes all team logos.
Will change the team color to their secondary color for all card art assets and charts.
Replace the player's name with their nicknames sourced from here. Users can choose any of the first 3 nicknames, order will match the order provided by baseball reference in the link above.
Expands speed options for 2000 and 2001 sets to use the full range of numbers between 8 and 28.
Tips for uploading your own custom images:
1500x2100 for normal cards. For bordered cards, use 1644x2244.300 PPIThe Showdown Library is a backend system used to:
It leverages the combination of Firebase's Realtime Database and the Google Drive API to deliver realtime Showdown Cards without the need for on-demand processing.
When a user submits a card on Showdown Bot, it will check to see if the user requested card is stored in the database, and if so will return the card and corresponding image in less than a second.
There are some cases in which the Bot will leverage the data from Showdown Library, but will still need to generate an image live.
List of reasons it will not used pre-stored image:
The Showdown Explorer tool leverages the power of the Showdown Library to provide the user with the ability to discover and explore cards from 1900-Present.
In depth walkthroughs and guides will be linked here in a future update.
You can clone this repository and run it locally on your machine. Be sure you have went through the prerequisites before proceeding.
Here are the high level steps:
After installing and handling any package errors, you can run Showdown Bot from the command line or locally in a browser.
Command Line
python mlb_showdown_bot --name "Mike Piazza" --year 1997 --set 2001
Flask App (opened via Browser)
python app.py
You can reach out to the developer of MLB Showdown Bot through email mlbshowdownbot@gmail.com
Follow MLB Showdown Bot Twitter for updates and card posts!
FAQs
Create custom MLB Showdown cards
We found that mlb-showdown-bot demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.
Security News
Research
Socket researchers found a malicious Maven package impersonating the legitimate ‘XZ for Java’ library, introducing a backdoor for remote code execution.