Stardew Valley Dashboard

Transforming 100+ wiki pages into 3 compact and concise dashboards

Data Visualization

Challenge

Currently, most existing data visualizations for Stardew Valley are limited to basic statistics or side-by-side-comparisons of individual crops. Those tools typically lack interactives and fail to account for contextual factors such as crop availability, fertilizer use, regrowth cycle, processing options, or variations in crop qualities. As a result, players miss opportunities to explore more nuanced or diversified strategies that could increase profitability and enjoyment.

Solution

We created three dashboards that act as “at-a-glance” guides for the various qualities of in-game items. Item lookup is now much more efficient than navigating the widely-used Stardew Valley Wiki.

Motivations

As a group of avid gamers and data enthusiasts, we love to see the numbers go up, especially when playing one of our favorite games, Stardew Valley.

The premise of Stardew Valley is that the player has inherited a farm and must grow various crops in order to earn money for other aspects of the game. The goal of this project was to help Stardew Valley players build budgeting and economic management skills through interactive data visualization of the game’s farming mechanics.

Currently, most other data visualizations for Stardew Valley are limited to basic statistics or side-by-side-comparisons of individual crops. Those tools typically lack interactives and fail to account for contextual factors such as crop availability, fertilizer use, regrowth cycle, processing options, or variations in crop qualities. As a result, players miss opportunities to explore more nuanced or diversified strategies that could increase profitability and enjoyment.

Lava Eel InfographicThis infographic uses a more narrative approach in explaining the game's mechanics
Starfruit InfographicThis infographic prioritizes numbers and figures

Prior to this project, the other members of my team explored conveying the game's mechanics through infographics. However, while robust, we quickly realized this might be a bit unwieldy for the large number of items present in the game. Price-determining factors are not applicable to all items, nor do they apply equally. So these layouts would not be modular enough.

Research

Initially, this project focused on crop pricing. We conducted EDA to establish trends in availability and effects of gameplay mechanics such as processing to increase in-game profits.

We preseted charts created in Tableau to three participants and asked them a series of question to guage understanding. All participants were Stardew Valley players with varying levels of experience, ranging from newbie to advanced. Participants were selected via professional and academic networks, with the intent of capturing a representative cross-section of target users. Participation was voluntary, and each participant signed an informed consent form prior to the session. This form disclosed the scope of the study, confidentiality provisions, and confirmed whether the session would be audio/video recorded.

Participants

Participant 1 Participant 2 Participant 3
Age Early 20s Late 20s Mid 20s
Familiarity First played a year ago 5 years of experience First played about 2 years ago
Expertise Newbie Advanced Casual
Tools Used Previously Stardew Valley Wiki Stardew Valley Wiki, YouTube guides Stardew Valley Wiki, Stardew Valley Planner

Our participants were all college-educated women with various experience with Stardew Valley and familiarity with in-game farming mechanics. Furthermore, they have all employed third-party tools help make gameplay decisions.

EDA in TableauSome examples of charts shown to participants in order to guage baseline understanding of game mechanics and test assumptions

User Testing

I. Test Measures

During the usability testing, we measured several key metrics to understand users’ perception of our design:

  1. Time on Task

    We recored how long it took each participant (in seconds and/or minutes) to complete tasks such as finding the most profitable crop in a given season while using our infographic versus an existing external wiki guide in order to quantify how intuitive and efficient our dashboard was to use. A shorter time generally indicated that users could quickly understand and navigate the interface.

  2. User Satisfaction

    During each session we used Likert-scale questions and open-ended questions to gauge users’ overall satisfaction with our design. This included whether the dashboard was frustrating to use or if they would use this dashboard when they play Stardew Valley. Other feedback included suggestions for iterations that would increase overall user satisfaction.

  3. Comparison to other tools

    Since Stardew Valley players often rely on external guides such as the Official Stardew Valley Wiki to access detailed in-game profits information, we asked participants to compare our dashboard to the wiki by completing the same tasks with both tools. We wanted to know whether they found our dashboard more visually appealing and easier to navigate in comparison to finding the same information through the wiki pages.

II. Findings

Overall the participants struggled to interpret some of the labels of the graphs and the overall structure of the visualizations including unclear axis titles and terminology. Less advanced players expressed more confusion and less certainty over the purpose and functions of the visualizations. All participants spoke their questions aloud while working through tasks, suggesting persistent ambiguity around how to get started or interact with the data effectively. One participant was unsure if clicking would reveal more information and didn’t initially realize the dashboard was interactive. Another initially missed that the visualizations required scrolling and expected immediate results from clicking the icons.

Despite initial confusion, none of the participants found the visualization difficult to use overall. Participants 1 and 3 expressed enthusiasm for the tool’s potential future uses of the visualization. Participant 3 specifically mentioned that using the visualization for information was preferable to using the Stardew Valley Wiki. All participants expressed a desire for the visualizations to have additional context and data available. Participant 3 suggested information for other items in the game. Interestingly, it took participants a minute longer on average look up information via Stardew Valley Wiki than it did our visualization for the purposes of crop comparision despite prior familiarity with Stardew Valley Wiki.

Approach

After conducting the usability tests, we decided to significantly modify our designs to better align with our vision and satisfy user needs. Instead of embedding Tableau graphs, we switched to Observable, which offers greater flexibility and a wider variety of visualization options. This change was also motivated by the issues participants encountered during testing, particularly when using Tableau’s default filters, which caused confusion.

In addition to updating the visualizations, we introduced a fixed side column that displays relevant key information, allowing users to quickly reference essential facts without needing to view the charts. This was a direct response to participants’ desire for quicker access to important crop-specific data, such as the number of harvests per season. Both the basic facts column and the selection column remain fixed on the screen, while the graph section is scrollable. This limited scrolling enables users to explore data in detail while still keeping the broader context in view, addressing participants’ difficulties in navigating between crop comparisons.

Stardew Valley WikiThe Wiki page involves lots of scrolling, and the summarized information can be cryptic
Stardew Valley DashboardOur approach to organizing the data undeniably takes inspiration from Stardew Valley Wiki, but our research informed some omissions as aesthetic choices

After presenting the current version of the dashboard to the same participants we tested with prior, the same tasks as before were completed almost instantaneously. Participants also expressed much excitement in using and exploring this version of the tool and stated it was preferred to the widely used Stardew Valley Wiki.

Data

I. Collection and Preparation

Our project utilizes comprehensive data extracted from Stardew Valley, primarily sourced from the game’s official Wiki page, which is widely regarded as the most accurate and community verified representation of in game mechanics. This source was chosen due to its consistent updates, trust within the player community, and our own experiences as players who rely on it during the game. However, it also required the data to be compiled manually. While tedious, it gave us a lot of control in our process.

We focused on gathering data for the three core economic systems within the game: crops, fish, and animal products. We applied consistent naming conventions and structured the data using tidy or long-format principles to support flexible analysis.

For crops, we gathered detailed information related to planting, harvesting, and profit margins, including:

  • Crop name
  • Crop type ( fruit, tree, vegetable, forageable, flower, other)
  • Season availability (Spring, Summer, Fall, Winter)
  • Seed price
  • Days to initial harvest
  • Days to regrow (for multi-yield crops)
  • Yield per harvest
  • Maximum number of harvests per season
  • Harvest frequency under different fertilizers: Speed-Gro, Deluxe Speed-Gro, Hyper Speed-Gro
  • Impact of the Agriculturist profession on fertilizer-enhanced growth rates
  • Base sell price by quality: Normal, Silver, Gold, Iridium
  • Tiller profession price multipliers by quality
  • Keg product output (Juice, Wine) and:
  • Base and Artisan profession prices by quality
  • Preserves Jar output (Pickle, Jelly) and:
  • Base and Artisan profession prices by quality
  • Dehydrator product (Dried Fruit, Dried Mushroom) and:
  • Base and Artisan profession prices by quality

We included effects of relevant professions, which are selected by players upon leveling up in specific skills. Professions significantly alter item values and growth rates:

  • Tiller: Crops worth 10% more
  • Artisan: Artisan goods worth 40% more
  • Agriculturist: Crops grow 10% faster

For fish, we collected data relevant to seasonality, pricing, and processing:

  • Fish name
  • Fish type (ocean, lake, pond, river, legendary)
  • Seasonal availability (Spring, Summer, Fall, Winter, or Special)
  • Base quality sell prices: Normal, Silver, Gold, Iridium
  • Smoked product prices, with and without Artisan profession
  • Sell prices under Fisher and Angler professions
  • Fish Roe value (raw and aged), including Artisan profession boosts

The Fisher and Angler professions apply multipliers of 25% and 50% respectively to raw fish values. The Artisan profession adds value to processed fish products, such as smoked or aged goods.

For animal-based goods, we recorded information on raw and processed profits, along with production context:

  • Product name
  • Animal that produces it
  • Base sell prices by quality
  • Rancher profession multipliers (+20% value)
  • Artisan profession multipliers (+40% for artisan goods)
  • Processing time
  • Machine used for processing (Cheese Press, Oil Maker, Loom)
  • Required building type (Coop, Barn, Deluxe Barn)

II. Cleaning and Processing

While compiling our data, we faced several formatting issues. Our original datasets included mixed capitalization and spacing that caused problems when trying to link data with file paths or reference values dynamically. For example, image assets for items had to be referenced by name in the browser, and names like "Sweet Gem Berry" would not match correctly unless written in a file-friendly format like "sweet_gem_berry".

To address this, all item names were converted to lowercase, spaces were removed or replaced with underscores, and column names were standardized using snake_case. Additionally, all numeric values, especially prices and growth times, were manually converted from strings to proper numerical types. This was necessary to enable quantitative operations and comparisons during exploratory data analysis (EDA), especially when using tools like Tableau, which would otherwise treat the values as categorical text.

We made deliberate decisions about which data to include and exclude. While our datasets are rich in numerical detail, we chose to omit broader global multipliers, like general profession-based price boosts, from most visualizations to avoid distorting trends across categories. For example, although professions like Fisher, Angler, and Rancher affect final profit margins, they apply uniformly and do not change item relationships or patterns of seasonality, processing efficiency, or base quality profitability. Instead, we focused on underlying factors that players could experiment with directly: quality tiers, processing choices, season timing, and growth enhancements.

This decision helped us maintain the clarity and usability of the visualizations, allowing users to evaluate core economic trade-offs without needing to toggle multiple modifiers. That said, we still preserved all the profession-based pricing in our datasets to allow for more advanced comparisons if desired, and future iterations of the visualization might include display of these modifiers.

III. Integration

Initially, we planned to work with CSV files directly in the visualization pipelines. However, we encountered technical limitations when integrating CSVs into the website using Javascript. Since CSVs are flat tables, they lack nested structure needed to easily associate relative properties (matching a fish to its season and to its processing value). To solve this, we pivoted to using JSON for all frontend integration which allows us to easily query and manipulate the data within our Javascript functions.

We converted our clean CSVs into JSON arrays using, which allowed us to access data via key-value pairs, making our JavaScript logic far more efficient and readable. This structure was especially important for: dynamically filtering items based on season or category, loading related images based on name, and calculating profit per day or per season using conditional logic. When a user filters by variable (choosing crops available in Spring), our script generates a new array containing only the relevant data, which is then passed into the visualization and used to update other display elements. In the end we developed ten spreadsheets, three .CSV files, three .JSON files, and 9+ dynamically generated arrays.

Reflections

Personally, this project gave me a deep appreciation for the attention that went into making each item in the game truly unique. There are only a handful of obvious money makers, all of which are only accessible late in the game. So a player can often choose any item they have a particular fondness for and still manage their profits efficiently. It was also very enjoyable to see other players express excitement for the dashboards, because it indicates we made something for which there was an actual need.

We later had the opportunity to exhibit this project to a larger audience mostly comprising of people who do not play Stardew Valley. One visitor even asked if we can use our layout and information dashboard display for other purposes such as displaying student productivity levels and statistics and mentioned this could potentially turn into a paid opportunity. This feedback was insightful as it told us that the general layout was effective and intuitive enough for someone with an outside perspective to want to take inspiration from our project and turn it into a visualization of their own following our methods.

There is also much room for improvement. The dashboard was designed initially (and solely) with computers in mind, and fills up the full width of the screen. This is because Stardew Valley was originally released only on PC, and a large percentage of players play this way. However, unless a player has multiple monitors, or doesn't mind switching between windows, our dashboards might be as inconvenient as the Wiki page. A future iteration of this project might be more responsive, or modded directly into the game for ease of access.

Also, we couldn't decide how much of the game's art and art style we wanted to incorporate. Perhaps it would have been better to lean into it more, or do something more creative with the charts.